B-TIER inspiration
Conway's Law — your product ships your org chart
100k ft — What is this?
Conway's Law — your product ships your org chart
50k ft — Why care?
Melvin Conway's 1967 observation: systems copy the communication structure of the organization that builds them. Modern teams apply the reverse Conway maneuver, designing the target architecture first and then shaping teams to match.
10k ft — Key takeaways
• Arrange teams to match the architecture you want
• Awkward product seams usually map to teams that barely talk
• link: https://shakibhammad.com/library/conway
5k ft — Tools & techniques
(no tools tagged)
reverse Conway maneuver
1k ft — Deep-dive / try it
Melvin Conway sent this to Harvard Business Review in 1967 and they rejected it for not proving its thesis. Datamation ran it a year later. The claim: any organisation that designs a system produces a design that copies that organisation’s own communication structure. Four teams building a compiler ship a compiler with four parts.
The elaboration the video does not make: engineers now use this deliberately and call it the reverse Conway manoeuvre. Decide the architecture you want first, then arrange the teams to match, because the mirroring happens either way and the only real choice is whether it happens on purpose.
Your customers are holding a physical copy of your org chart, and they experience it as friction. Which handoff in your product is really two teams that barely speak?
What to…
Transcript excerpt
In 1967, a computer scientist called Melvin Conway noticed something strange enough that he wrote it up and sent it to Harvard Business Review. They rejected it on the grounds that he hadn't proved his thesis, so he sent it to a computing magazine instead, and they published it in 68. And the idea became one of the most quietly confirmed observations in how organizations work. Any company that designs a system will produce a design that copies the company's own communication structure, not as a metaphor, but literally. Four teams building a compiler will ship a compiler with four parts. A company where two departments barely speak will ship a product where two components barely connect. The organization chart leaks into the product piece by piece, whether anyone intends it or not. I told the Sony story a while ago, three divisions invading incompatible music players on the same stage, and Conway is the law underneath it. The customer ends up holding a physical copy of your internal politics. The reason is almost obvious, once said out loud. People design what they can talk about, and they can only talk across the channels that exist. If the channel between two teams is thin, the connection between their two components will be also thin and awkward and late. The lens that follows is the sharp part, and modern engineering systems and teams use it deliberately. Design the organization for the product you want, because you're going to ship your organization chart either way. So…