Four Fundamental Team Types

A model that reduces team organization to four types: stream-aligned (aligned to a flow of work, and the primary type), platform (provides internal services that reduce others' cognitive load), enabling (helps other teams acquire capabilities), and complicated-subsystem (owns a part needing deep specialist expertise).

Why it Matters

Most teams should be stream-aligned; the other three exist to support fast flow for stream-aligned teams. Naming a small set of types stops the proliferation of ad hoc team kinds and makes each team's purpose explicit.

Signals

• Every team can be described as one of the four.
• Support teams (platform, enabling, complicated-subsystem) justify themselves by the load they remove from stream-aligned teams, not by their own output.

Benefits

A shared vocabulary for organizing teams, a sensible default (stream-aligned), and clear reasons to deviate. Keeps the number of distinct team types small.

Risks

Forcing hybrid teams into a single box. Creating platform or enabling teams that add coordination without actually reducing load; the "thinnest viable platform" idea guards against platforms that grow past what is needed.

Tensions

A team may legitimately blend types, and rigid typing fights that reality. A platform team reduces cognitive load but introduces a dependency and a new interaction boundary.

Examples

A product team owning a user-facing journey end to end is stream-aligned. An internal team offering a self-serve deployment platform is a platform team operating as a service.