Conway’s Law
The observation that systems tend to reflect the communication structures of the organizations that design them.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/conways-law/
01What it means
Conway’s Law states that organizations designing systems are constrained to produce designs that mirror their communication structures. It is an organizational observation, not a deterministic engineering law: architecture and organization influence each other over time.[1][2]
- Communication structure
- Who shares context, decisions, and coordination pathsTeam boundaries and ownership shape available design choices
- System structure
- Components, interfaces, dependencies, and change pathsArchitecture can reinforce or challenge organizational boundaries
This is an organizational observation, not deterministic fate; teams can deliberately change interfaces, ownership, or architecture and observe the joint effect.
02Why it matters
Team boundaries, dependencies, and communication paths can shape product architecture and user experience, so organization design is part of product and technical design.
03When to use it
Use it when examining ownership boundaries, modularity, integration friction, or reorganization consequences. Treat it as a hypothesis to inspect rather than a prediction that excuses poor architecture.
04How it works
- Map communication paths and decision ownership.
- Map system boundaries and dependency flows.
- Compare mismatches and repeated coordination costs.
- Change team interfaces or architecture deliberately.
- Observe whether the system and communication improve together.
05A practical example
A company split into separate catalog and checkout departments repeatedly creates duplicated product data; aligning ownership around a shared product flow reduces the integration boundary.
06Where it breaks
Many technical, market, and historical factors shape architecture; reorganizing teams can disrupt delivery and does not automatically improve design.
Common mistakes
- Treating the law as a universal causal rule.
- Reorganizing without understanding product boundaries.
- Assuming a team chart alone changes communication behavior.
07Sources
- How Do Committees Invent?Melvin E. Conway · Original author essayHow Do Committees Invent?
- Conway’s LawMartin Fowler · Authoritative software architecture commentaryConway’s Law