The Four Fundamental Team Types

Definition

Rather than letting team shapes emerge by accident (or by org-chart convention), Team Topologies proposes a small, closed vocabulary of team purposes: stream-aligned (built around a continuous flow of work to a business domain), enabling (helps other teams close capability gaps), complicated-subsystem (owns a piece of the system that needs specialist expertise), and platform (provides self-service internal services that reduce the cognitive load of stream-aligned teams). Any existing team can be checked against this list and reclassified or restructured accordingly.

In the Book

This source is a condensed one-page "Getting Started" overview rather than full chapter prose, so it presents the four types as a checklist rather than through worked examples. Step 1 instructs the reader to "Identify what kind of teams you currently have" by mapping existing teams to "common industry team types" and flagging which types to avoid or change. Step 2 then names the four target shapes explicitly — Stream-aligned, Enabling, Complicated subsystem, Platform — as the shapes technology teams should be fitted to (with a pointer to shapes.teamtopologies.com for the visual reference). No case study or narrative example of a specific company applying the typology appears in this file.

Why It Matters

A small, exhaustive typology turns "how should we organize this team?" from an open-ended design question into a classification exercise: identify the team's true purpose, match it to one of four shapes, and let the mismatch between current structure and the closest-fitting type reveal where reorganization is needed. The same move — replace an unbounded design space with a small closed taxonomy that forces every unit to declare its purpose — is useful anywhere teams, modules, or roles tend to accumulate ad hoc responsibilities.