Conway's law
A system's structure mirrors the communication structure of the organisation that built it. As a diagnostic, chronic friction at the same boundary despite process fixes is often the structure presenting its bill. As a design rule, team boundaries and system boundaries are one decision.
Evidence grade: practice A widely adopted practitioner model with clear provenance.
Use it when
Reading recurring failures at a boundary; designing teams and systems together.
Where it stops working
It is an observation with empirical support, and no law of nature. It says that the structures correlate, and does not say which one to change to fix the other.
Where the standard uses it
- DE-4Managing scope, risk, and dependencies across workstreamsSeeing the whole, naming the risk, negotiating the boundary.
- TJ-1Evaluating architectural decisions and their organisational consequencesTrade-offs, reversibility, and who has to coordinate because of this.
- SV-6Organisational design and leading changeTeam structures, ownership boundaries, reorgs, and transitions.
Sources
- Melvin E. Conway. How Do Committees Invent?. Datamation, April 1968, 1968. In the bibliography
Used alongside it
- One-way and two-way doors practice
- Architecture review forums practice
- Contract at the boundary practice
- Ground truth and status criteria practice
- Leading change practice
- Sizing teams and spans practice
Cite this model
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Conway's law. In Engineering Management Academy Body of Knowledge (Version 3.1, TEC.conway-s-law). https://www.engineeringmanagement.academy/body-of-knowledge/techniques/conway-s-law