# Team Topologies

An adaptive organizational-design approach that uses four team types and three interaction modes to improve flow and manage cognitive load.

- Type: framework
- Domain: Leadership & teams
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/team-topologies/>)

## What it means

Team Topologies is an approach to designing technology organizations around fast flow of value. It describes four fundamental team types—stream-aligned, platform, enabling, and complicated-subsystem—and three interaction modes: collaboration, X-as-a-Service, and facilitation. Team boundaries and interactions are expected to evolve as needs change.

## Why it matters

An org chart rarely explains how work actually crosses teams. Unclear ownership, permanent handoffs, and unmanaged cognitive load can make delivery slow even when each team appears busy. Team Topologies provides a shared language for examining those conditions and deliberately shaping communication, responsibility, and platform support.

## When to use it

Use the framework when dependencies, handoffs, overloaded teams, or unclear service ownership are blocking flow. It is useful during scaling, platform adoption, modernization, or organizational review, but should begin with value streams and real constraints rather than forcing current teams into fashionable labels.

## How it works

1. Map important value streams, current team responsibilities, dependencies, handoffs, and sources of cognitive load.
2. Align long-lived stream-aligned teams to meaningful flows of change and clarify end-to-end ownership.
3. Introduce platform, enabling, or complicated-subsystem capabilities only where they reduce load or provide scarce expertise.
4. Make each inter-team relationship explicit as temporary collaboration, a service interaction, or facilitation.
5. Observe flow and team health, then evolve boundaries and interaction modes through small, evidence-based changes.

## A practical example

A retailer's checkout team depends on separate infrastructure and security queues for every release. Leaders form a stream-aligned checkout team, expose repeatable deployment and policy checks through a platform service, and ask an enabling team to coach the migration for eight weeks. The facilitation ends once the checkout team can operate independently.

## Where it breaks

The framework is a thinking model, not a complete organization chart or a guarantee of performance. Renaming teams without changing ownership, funding, architecture, or incentives adds ceremony. Real organizations may need temporary hybrids, and platform or enabling teams can become gatekeepers if they ignore internal users and preserve dependencies.

## Common mistakes

- Copying the four team labels without mapping value flow or cognitive load.
- Treating interaction modes as permanent relationships rather than choices that can change.
- Calling a shared infrastructure queue a platform without offering a usable internal product.
- Running a disruptive reorganization before testing smaller boundary changes.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/team-topologies/#visualization-team-topologies>)

## Sources

1. [Key Concepts and Practices](<https://teamtopologies.com/key-concepts>) — Team Topologies · Framework author guidance
2. [Team Topologies Book](<https://teamtopologies.com/book>) — Team Topologies · Framework author book overview
3. [CNCF Platforms White Paper](<https://tag-app-delivery.cncf.io/whitepapers/platforms/>) — Cloud Native Computing Foundation · Industry foundation white paper

## Related topics

- [Platform Engineering](<https://wiki.soroush.uk/topic/platform-engineering/>)
- [Developer Experience](<https://wiki.soroush.uk/topic/developer-experience/>)
- [Engineering Management](<https://wiki.soroush.uk/topic/engineering-management/>)
