Roster construction decides which lineups a coach can actually reach

Options are built, not chosen

A coach selects from the combinations the roster permits, and a roster with several players requiring the same conditions to be effective permits fewer than its quality suggests. Two players who each need the ball in the same area cannot be deployed together without one of them operating outside their strongest role. That constraint is invisible when each is watched separately and becomes obvious only in the combinations a staff repeatedly avoids using.

Because the constraint originates in construction, in-game criticism of the coach frequently targets the wrong decision-maker entirely. The question worth asking is which combinations the roster makes available, and only then whether the staff is choosing well among them.

Spacing is a roster property

The amount of usable space in a possession depends on how many players on the floor must be respected away from the basket at any moment. A lineup containing several players who do not have to be guarded at distance concedes defensive help that the offence then has to overcome. This is why apparently strong individual players sometimes cannot be played together, since their combined effect on spacing outweighs their separate contributions.

Rosters built without attention to this end up with a small number of viable lineups and a long bench that cannot be used effectively. Construction therefore has to consider combinations rather than adding capable individuals and expecting the staff to arrange them.

Defensive coverage has to be complete

Every lineup must be able to cover the range of offensive threats it will face, which requires size, perimeter speed and the ability to defend in space. A combination missing one of these can be attacked systematically, and opponents will find the deficiency within a small number of possessions. Because a roster has limited places, covering every requirement in every lineup is impossible, and staffs accept specific vulnerabilities in specific units.

Which vulnerability is accepted depends on the opponent, which is how the same roster produces very different lineups across a schedule. That pattern of acceptance is one of the clearest expressions of how a staff assesses the risks in front of it.

Availability changes the arithmetic

The set of workable lineups shrinks whenever a player is unavailable, and the shrinkage is rarely proportional to that player's individual contribution. A player whose main value is enabling others may be worth several combinations, and losing them removes more options than a higher-scoring absence would. This is why a squad can absorb one absence comfortably and be destabilised by another that looks less significant on paper.

Depth in this sense is about redundancy of function rather than the number of capable bodies available to a staff. Assessing depth therefore means listing the functions the system requires and checking which of them has no second source.

Reading a rotation as evidence

The combinations a staff uses most, and the ones it avoids under pressure, reveal its own assessment of the roster more reliably than any public statement. A combination that appears only when the game is already decided is being evaluated rather than trusted. One that appears at the end of close contests has been judged the best available answer to the specific problems those situations present.

Tracking these patterns across a schedule builds a picture of the roster's real shape, which often differs from the one implied by reputations. It is also the most reliable way to anticipate what a staff will do when a comparable situation next arrives.