Team Types in Depth

Source: content/manual/05-team-topologies/chapters/01-team-types-in-depth.md

Purpose and scope

Detail stream-aligned, enabling, complicated subsystem, and platform team responsibilities.

Outcomes

  • Clear ownership and fewer handoffs.
  • Reduced cognitive load and rework.
  • Faster decisions at the edge.

Signals of trouble

  • Frequent escalations across unclear boundaries.
  • Overloaded stream teams maintaining shared infrastructure.
  • Stalled adoption of new practices.

Remediation steps

  1. Define charters and interfaces; publish in the handbook.
  2. Reassign shared components to platform or subsystem teams.
  3. Create an enablement calendar for new capabilities.

Checklists and assets

References

  • “Team Topologies”; org maps; service catalog ownership.