Team Topologies
Team organization by value stream, with reduced dependencies and clear ownership that eliminates coordination waste.
4 types
of teams
Clear structure
3 modes
of interaction
Defined patterns
-70%
dependencies
Between teams
Why this matters
What executives need to know
Team structure is architecture. Conway's Law is not optional.
Systems reflect the communication structures of the organizations that build them. Poorly organized teams produce problematic architectures regardless of individual talent or technical decisions.
Four team types cover virtually every organizational scenario
Stream-aligned, Platform, Enabling, and Complicated Subsystem teams provide a complete vocabulary for designing organizations that deliver value without accumulating coordination debt.
Cognitive load determines effective team size
Teams sized by headcount without regard for cognitive load become overloaded. Overloaded teams slow down, produce lower quality, and experience higher turnover. The cost is measurable.
Each inter-team dependency adds latency and risk
Dependencies between teams are not just coordination overhead. They are structural bottlenecks that compound across every delivery. Team Topologies eliminates them by design.
Proven Results
Measurable business impact
Real metrics from organizations that evolved this capability.
-70%
Dependencies
High coupling→Autonomous teams
2x
Delivery Speed
Frequent blockages→Continuous flow
+45%
Team Satisfaction
Frustration→Clarity of purpose
-60%
Meeting Time
Excessive coordination→Defined interactions
The Challenge
Team structures that do not reflect value flow become organizational debt
When teams are organized around functions rather than value streams, coordination overhead grows faster than headcount. Work spent on alignment does not generate output.
1
Teams blocked by other teams
Dependencies that require cross-team coordination to make progress. Every dependency is a queue.
2
Unclear ownership
When responsibility is ambiguous, accountability disappears. Problems fall through the gaps between teams.
3
Cognitive overload
Teams managing domains too large to fully understand. Quality degrades. Decisions slow down. Turnover rises.
4
Meetings that produce alignment theater
Excessive coordination work that feels productive but generates no delivery output.
Our Approach
What we implement
01
Team API
Explicit definition of what each team offers, how to request it, and what response time to expect. Reduces informal channels and makes dependencies visible.
02
Cognitive Load Assessment
Structured evaluation of cognitive load per team to identify overload before it affects delivery and retention.
03
Interaction Modes
Three defined modes: Collaboration, X-as-a-Service, and Facilitating. Each appropriate for different phases. None permanent by default.
04
Platform Thinking
Platform teams that build self-service capabilities so stream-aligned teams ship faster without depending on a central gatekeeper.
05
Enabling Teams
Temporary teams that help other teams build a specific capability, then move on. Knowledge transfer built into the model.
06
Team-First Boundaries
System boundaries designed around what a team can realistically own, not derived from technical convenience. Architecture follows organization.
Frequently Asked Questions
Common questions about this topic
What is the right team size?
The constraint is cognitive load, not headcount. Can the team fully understand and evolve the domain it owns? Typically five to nine people, but the complexity of the domain sets the real ceiling.
Does every team need end-to-end skills?
Stream-aligned teams should have all the skills required to deliver value without depending on other teams. Platform and complicated subsystem teams can be more specialized by design.
How to move from a functional structure?
Incrementally. Identify one value stream, form a stream-aligned team around it, and demonstrate results before scaling the model. Structural reorganizations that happen all at once rarely work.
What is a platform team?
A team that builds and maintains an internal platform used by other teams in self-service mode. It reduces the cognitive load of stream-aligned teams and removes the need for them to solve infrastructure and tooling problems.
Ready to evolve Team Topologies?
Start with a maturity diagnostic. In 47 days, you'll have clarity about where you are, where to go, and how long it will take.