Conway's Law — How Do Committees Invent?

In 1968, Melvin Conway published a short paper in Datamation with a deceptively simple thesis: the structure of any system designed by an organization will be a copy of that organization's communication structure. Not a metaphor. A structural inevitability.

The idea never got a proper rebuttal. It just kept showing up — in compiler architectures, weapon systems, and every microservice boundary drawn along team lines. Conway didn't call it a law. Everyone else did.

I put together this infographic to lay out the core argument: the five stages of system design, the homomorphism between org charts and system graphs, and the disintegration problem that follows when you throw people at complexity.

The part that sticks with me is the prescription at the bottom. Conway's answer wasn't better tools or smarter engineers. It was organizational flexibility — the willingness to reorganize around the actual communication needs of the system, not the other way around.

Michael Paris writes about things that keep him up at night.