Stackbook Logo
economics-evolutionestablished · high operational burden

Team Topologies

Also known as: team-structure, org-design, conways-law, stream-aligned, platform-team

Intent

Design team structures that optimize for flow, autonomy, and cognitive load — applying Team Topologies patterns (stream-aligned, platform, enabling, complicated-subsystem).

Problem

Org structure often accidental. Teams are component-based (frontend/backend), creating dependencies. Need flow-oriented design per Conway's Law.

Forces

  • •Conway's Law: org structure = system architecture
  • •Cognitive Load: team must own comprehensible scope
  • •Flow Efficiency: minimize handoffs, waiting, dependencies
  • •Autonomy: teams deploy, operate, decide independently

Solution

✓ When to Use

  • •Org > 50 engineers
  • •Cross-team dependencies slowing delivery
  • •Platform team becoming bottleneck
  • •Cognitive load complaints

✗ When Not to Use

  • •Small org (<30 engineers)
  • •Single product, simple domain
  • •Team not ready for org design investment

Pros

  • +Optimizes for flow and autonomy
  • +Reduces handoffs and cognitive load
  • +Clear ownership and interfaces
  • +Scales with organization

Cons

  • −Reorg disruption (temporary velocity drop)
  • −Requires leadership buy-in and patience
  • −Platform team investment before ROI
  • −Cultural shift: collaboration → X-as-a-Service

Cost Profile

Infrastructure

Low — org design, communication

Operational

Medium — reorg, team formation, platform build

Cognitive

High — org design, cognitive load, interaction modes

Failure Modes

  • Platform as bottleneck: platform team does tickets for stream teams

  • Enabling as support: enabling team never leaves

  • Component teams persist: frontend/backend split remains

  • Cognitive load ignored: teams burn out

  • Interaction mode confusion: collaboration vs X-as-a-Service

Real-World Examples

Alternatives

  • component-teams
  • feature-teams
  • squad-model
  • chapter-guild
  • holacracy

Related Patterns

  • platform-engineering
  • enabling-team
  • stream-aligned-team
  • cognitive-load
  • conways-law
  • platform-engineering
  • devops-topologies

Competency Domains

economics evolutiondeploymentdistribution communicationreliability opsdeployment