Prefer small, empowered, cross-disciplinary teams
GDC-L1-TEAM-000501
Statement
Small teams with autonomy and mixed disciplines tend to move faster and stay more coherent than large, siloed, permission-gated ones. Communication cost grows with team size; empowerment and cross-discipline collaboration keep decisions close to the work and the vision easy to share.
02
Rationale
The number of communication links in a team grows combinatorially with its size, so every added person raises coordination overhead and dilutes shared context — which is why small teams can hold a vision (VISION-0001) in common almost effortlessly while large ones need heavy process to approximate it. Autonomy compounds the benefit: when a small team can decide and act without gatekeeping, decisions stay close to the people doing the work and the feedback loop tightens. Cross-discipline collaboration (designers, artists, engineers working together rather than handing off over walls) surfaces problems and opportunities that siloed pipelines miss. None of this makes big teams wrong — they're necessary for large-scope games — but it explains why small, empowered, mixed teams punch above their weight and why scaling a team has real costs, not just benefits.
03
Applies when
Team structure and org decisions, and the recurring "should we add people?" question (recall that adding people to a late project often slows it — PROD's staffing caution). Especially relevant to indie and small-studio contexts.
04
Does not apply / Exceptions
Large-scope games (big-budget AAA) genuinely require large teams, and at scale you need structure, specialization, and process that a small team can skip — so this is a preference, not a law (hence stylistic). Deep specialization also has real value that pure generalist small teams lack. The principle is "keep teams as small and empowered as the scope allows," not "small is always better regardless of scope."
05
Implementation
Keep teams as small as the scope permits; resist adding people as a reflex (scope down instead, PROD-0001). Grant autonomy — decisions close to the work. Compose teams cross-functionally so disciplines collaborate rather than hand off.
06
Disagreement
Small-and-autonomous (speed, coherence, low overhead, but limited capacity and depth) vs. large-and-specialized (scale, deep expertise, but coordination cost and diluted context). The right structure follows the scope; the failure modes are under-capacity (too small for the ambition) and coordination-collapse (too big without structure). Typed stylistic as a genuine org-design values choice.
07
Notes
Confidence 3: a real preference, genuinely bounded by project scope.
↔
Connected principles
S