team topologies

how it works

• each lesson is one concept, with a concrete application.
• lessons 1–4 build the mental model; lesson 5 applies it to a fictional org as an interactive exercise.
• lesson 6 covers the common ways teams misapply the framework — the fake platform team, the matrix org, the permanent enabling team.
• lesson 7 is about evolving the topology without blowing up delivery.

lessons

1. 01 the four team types stream-aligned, platform, enabling, complicated-subsystem. what each is for, and what happens when you mix them up. 12m
2. 02 interaction modes collaboration, x-as-a-service, facilitating. the three ways teams work together — and the cost of picking wrong. 12m
3. 03 cognitive load as a constraint how much a team can hold in its head. why a team of eight owning ten services is already broken. 10m
4. 04 conway's law, forward and reverse your system's architecture mirrors your org chart. the reverse maneuver: design the org to get the architecture you want. 12m
5. 05 applying it to a real org a fictional company with ten teams. we redesign it. drag-and-drop topology exercise at the end. 16m
6. 06 common failure modes the fake platform team, the matrix org, the enabling team that never leaves. how each one breaks a topology. 14m
7. 07 evolving the topology teams change. how to move a team between types without blowing up delivery — and when not to. 12m