Conway’s Law

Conway’s law relates a system’s structure to the communication structure of the organization that designed it. Conway’s own account emphasizes the constraints that missing communication paths place on design choices. The relationship is not necessarily one-to-one: one design group can produce several subsystems.

It comes from a 1968 paper, “How Do Committees Invent?”, published in Datamation in April of that year — submitted to a management journal the year before and rejected. Worth knowing because the law is frequently cited as folklore, and the original is both older and more precisely worded than the paraphrases.

Communication shapes the available choices

The observation does not establish whether a resulting design is good. Conway also draws a practical implication from it: organize design work around communication needs and preserve the flexibility to change that arrangement as the system concept improves. It is not a prescription for a fixed number of teams or services.

Communication structure includes more than reporting lines. Teams in different departments may work closely together, while teams under one manager may depend on slow ticket handoffs. An application of the law therefore begins by examining how decisions and information actually move.

Expensive coordination can encourage teams to create interfaces along organizational divisions, even when a different boundary would suit the domain better. That is a risk to investigate in changes and handoffs, rather than an outcome that a time-zone map can establish by itself.

Two ways to use it

The observation can guide both diagnosis and organizational choices, provided those choices are checked against actual work.

• Investigate mismatches. Use the service list and team responsibilities to identify places where changes cross ownership boundaries. Then examine delays, conflicting decisions, and contract revisions. Joint work can be effective; the evidence should establish where coordination is costly and what contributes to that cost.
• Change communication where it limits the design. Clear decision rights, closer collaboration, or a reorganization may support better boundaries. Their cost and lead time depend on the situation. Discuss the intended design before reorganizing, and retain room to revise both as the team learns.

Both are more useful than the slogan version, and both survive the fact that you usually cannot choose your organization freely.

Three ways it is misused

As a license to copy another company’s topology. Its service boundaries may reflect communication needs, domain divisions, and operating constraints that differ from yours. Adopting the topology can add coordination demands without reproducing the conditions that made it useful.

As an argument for one service per team. One team can own several services or a coherent set of modules inside a modular monolith. Inspect each service’s ownership, maintenance workload, and incident coverage. A large service-to-team ratio raises questions about capacity but does not prove that any service is unowned.

As a reason not to try. Treating the org chart as an unchangeable design specification ignores communication outside reporting lines. Explicit interfaces, agreed decisions, and investment in collaboration can change which designs the organization can sustain.

Conway’s law helps explain organizational influences on design; domain analysis helps evaluate the boundaries themselves. A bounded context identifies where a model has a consistent meaning, and ownership and operating requirements help determine its implementation. Comparing those needs with the organization’s communication paths is part of the analysis in Splitting the System Was the Easy Part.

References

• Melvin E. Conway, How Do Committees Invent?, Datamation, April 1968
• Conway’s account of the paper’s publication