Casey Muratori on Conway's Law: Bandwidth, Org Charts and AI Agents
By Matt Cullerton, founder of Mavric and Apso
Conway's law says a system's design copies the communication structure of the organization that built it. In a clip from Ryan Peterman's podcast (@ryanlpeterman), Casey Muratori calls it the only unbreakable law in software and recasts it as a bandwidth problem, with "products look like the org chart" as a side effect. The research behind the law is strong. His extension to AI agents is a guess he labels as one.
Who is Casey Muratori?
Muratori is the programmer behind Handmade Hero, Granny 3D at RAD Game Tools, and the collision and world editor work on Jonathan Blow's The Witness. The clip is 75 seconds from a Peterman Pod episode published September 14, 2026. He gave a full lecture on the same topic in March 2022 called "The Only Unbreakable Law."
What did Conway actually write?
Melvin Conway published "How Do Committees Invent?" in Datamation in April 1968, after Harvard Business Review rejected it. The quoted sentence reads: "organizations which design systems (in the broad sense used here) are constrained to produce designs which are copies of the communication structures of these organizations."
On his own site, Conway puts it as "any organization that designs a system will produce a design whose structure is a copy of the organization's communication structure."
The sentence names communication structure. Reporting lines are a rough proxy for it. Two teams under different VPs who talk constantly act as one communication unit. One team on paper, split across two time zones that sync weekly, acts as two.
Why does Muratori call Conway's law a bandwidth problem?
His condition is that communication between workers is slower than each worker's internal ability to compute. Once that holds, splitting a problem buys parallelism. The cost is that design iteration across the split gets slower than iteration inside either half.
This version makes predictions you can check. The boundary should harden in proportion to the communication cost. There should be no penalty when workers can talk as fast as they think, which is why a solo programmer or a single team in one room does not pay it. The clip skips the derivation, but the full lecture and the podcast episode both walk through it.
Does Conway's law apply to AI agents?
Muratori adds "or in the modern parlance, let's say agents" to his definition in the clip. The full transcript on developing.dev is more careful: "I suspect it will also become true for AIs and things like that, where it's like, you will want to partition these problems in ways that respect that line drawing."
I found no study testing Conway's law on multi-agent LLM systems. The mechanism is plausible. Agents passing summaries through a context window have far less bandwidth between them than one agent reasoning inside a single context. Treat it as a prediction worth testing.
Is there evidence for Conway's law?
Yes. Muratori does not cite any in the clip, but two studies stand out.
Nagappan, Murphy and Basili studied Windows Vista at Microsoft Research and the University of Maryland, covering 3,404 binaries and over 50 million lines of code. Organizational structure metrics predicted failure-prone binaries with 86.2% precision and 84.0% recall. Code churn scored 78.6% and 79.9%. Organizational metrics also beat code complexity, coverage, dependencies and pre-release defect counts.
MacCormack, Baldwin and Rusnak tested the mirroring hypothesis by pairing commercial products against open source products that do the same job. In every pair, the product from the loosely coupled organization was significantly more modular. Their paper ran in Research Policy in October 2012.
What is the inverse Conway maneuver?
Thoughtworks calls the practical response the inverse Conway maneuver. You structure teams to match the architecture you want, then let Conway's law produce that architecture. It has sat on the Thoughtworks Technology Radar for years and underpins the Team Topologies book.
Wikipedia's summary notes that people disagree about whether the effect is good or bad, and about which way causality runs. If architecture also shapes how teams communicate, the maneuver pushes on a feedback loop. Expect it to be slow and messy in practice.
Bottom line
Conway's law is about who talks to whom, and Muratori's bandwidth framing explains when it bites: when talking costs more than thinking. The Vista study backs it with numbers. Applying it to AI agents is Muratori's suspicion, and nobody has tested it yet.
Sources
- The Only Unbreakable Law: Muratori's March 2022 lecture.
- Casey Muratori on the Peterman Pod: the full episode with transcript.
- Episode on YouTube: video version of the episode.
- Conway's Law: Melvin Conway's page with the 1968 paper.
- The Influence of Organizational Structure on Software Quality: the Windows Vista study.
- Exploring the Duality Between Product and Organizational Architectures: the mirroring hypothesis test.
- Inverse Conway Maneuver: Thoughtworks Technology Radar entry.
- Conway's law on Wikipedia: overview and criticisms.
- Casey Muratori on Wikipedia: background on his work.
- The Peterman Post: Ryan Peterman's newsletter and podcast.
Published September 17, 2026. Based on a TikTok by @ryanlpeterman. Full video notes (markdown)