Heuristic

Minimize the number of teams that must change together

Cross-boundary coordination is a cost of architecture.

About 1 min read

Before you use it

Use when
  • When small product changes require synchronized work across many groups.

Keep this limit in mind

  • Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Map which teams must agree, build, test and release together for a normal change. Redesign boundaries or contracts where one change creates unnecessary multi-team coupling.

An example

A field-label change should not require integration, platform and reporting releases if the contract can preserve semantic identity.

Check your result

Typical changes require fewer simultaneous owners without bypassing controls.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingMinimize the number of teams that must change together

Evidence and sources
Provides context

Simon described complex systems as often hierarchical and near-decomposable, motivating analysis of relatively strong within-subsystem interactions and weaker cross-subsystem interactions.

Near decomposability is a conceptual property, not evidence that any chosen boundary is correct.

The Architecture of Complexity · Near-decomposability discussion

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details