Conway’s Law
Conway’s Law shows that your product’s seams are usually a map of your org chart’s seams.
What Is It?
Conway’s Law holds that organizations which design systems are constrained to produce designs that copy the communication structure of the organization itself. Programmer Melvin Conway’s original 1968 phrasing was: “organizations which design systems… are constrained to produce designs which are copies of the communication structures of these organizations.”
Conway first submitted the paper, “How Do Committees Invent?”, to the Harvard Business Review in 1967. It was rejected on the grounds that he hadn’t proven his thesis, and was published instead in the trade magazine Datamation in 1968. Fred Brooks later cited it in The Mythical Man-Month and gave it the name “Conway’s Law.”
Why Does It Matter?
The pattern shows up anywhere multiple teams produce a single output. If Marketing and Product don’t talk to each other, the messaging and the feature set drift apart, and customers can tell. If four regional teams each build their own version of a process, the resulting system has four seams in it, whether or not anyone intended four versions to exist.
The seams aren’t a coincidence, and they usually aren’t a failure of any individual team’s competence. They are the org chart, expressed in the output. Fixing the output without touching the communication structure that produced it tends to produce the same seams again.
What Changes Once You See It?
You stop treating a fragmented product, process, or document as a design defect to be patched.
You start asking whether the fragmentation is actually a direct copy of how the teams responsible for it communicate, or fail to.
You start looking at the org chart and the reporting lines before you look for who to blame in the output.
Common Misunderstandings
- It is not limited to software architecture, even though it’s most often cited there. Conway’s original paper was about organizational design in general.
- It doesn’t mean reorganizing always fixes the problem. Changing the structure changes what gets copied into the output, but a badly designed new structure just produces a different set of seams.
- It is not a claim about intent. Nobody has to design the fragmentation on purpose for the law to hold. It emerges from the communication structure whether or not anyone notices.
- It doesn’t only apply at the top level. The same pattern shows up inside a single team, between sub-groups that don’t coordinate closely.
Diagnostic Question
If our output is fragmented, does the shape of that fragmentation match the shape of how the teams responsible for it actually talk to each other?
Explore Further
Field Notes
None yet.
Origin
Melvin Conway published the idea in “How Do Committees Invent?” in Datamation magazine in April 1968. Fred Brooks named it “Conway’s Law” a few years later in The Mythical Man-Month.