Home › The Garage › Org design
Teams & ways of working

Org design & team topologies

How you draw team boundaries decides how work flows — and the systems you build end up mirroring your org chart whether you meant them to or not. Team design is therefore a design decision, not an HR afterthought.

By LeanBean · Updated November 2026 · 6 min read
What's in this guide
  1. Org design as flow design
  2. Why systems mirror teams
  3. Four team types
  4. Designing for flow
  5. Common questions
Stream-aligned teamowns a flow of value to the customer Platformself-service foundations Enablinghelps others get better Complicatedsubsystem
A value-delivering team, supported by platform, enabling and specialist teams — a common topology.

Org design as flow design

Org design is usually treated as boxes and reporting lines. But the boundaries you draw between teams decide where the hand-offs fall, and therefore how fast work flows. Draw the boundary across the middle of a value stream and you create a permanent queue; draw it around a whole value stream and the team can deliver without waiting. Org design is flow design in disguise.

Why systems mirror teams

There is a well-observed tendency for the systems an organisation builds to mirror its communication structure — four teams tend to produce a four-part system, with the awkward seams falling exactly on the team boundaries. The practical consequence: if you want a particular architecture or a particular flow of work, you often have to organise the teams to match it first. The team structure is not neutral.

Four team types

One useful model describes a small set of team types: stream-aligned teams that own a flow of value to the customer (most teams should be this), platform teams that provide self-service foundations so stream teams go faster, enabling teams that help others build a capability and then step back, and complicated-subsystem teams that own something needing deep specialism. Clear types with clear interactions beat a sprawl of overlapping remits.

Designing for flow

Keep a team’s load inside its heads
A team can only own what it can hold — if its remit is wider than its collective cognitive capacity, quality and speed both fall. Good org design limits each team’s scope to something it can fully understand, gives it a clear type, and designs the interactions between teams deliberately rather than leaving them to chance. The aim is fast flow with the fewest hand-offs, not a tidy-looking chart.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

What is org design?

The deliberate design of team boundaries, responsibilities and interactions. Because those boundaries decide where hand-offs fall and how work flows, org design is effectively the design of flow, not just reporting lines.

Why do systems mirror the organisation that builds them?

There is a well-observed tendency for a system’s structure to reflect the communication structure of the teams that build it, with seams falling on team boundaries. So achieving a desired architecture often means organising teams to match it first.

What are the main team types in team topologies?

Stream-aligned teams that own a flow of value, platform teams providing self-service foundations, enabling teams that help others build capability then step back, and complicated-subsystem teams that own deep specialist areas. Most teams should be stream-aligned.

What is team cognitive load?

The amount a team can collectively understand and own well. If a team’s remit exceeds its cognitive capacity, speed and quality both drop, so good org design keeps each team’s scope within what it can fully hold.

Related guides: Cross-functional teams · Ways of working · High-performing teams