Your engineering org chart is leaking 30% of your output — Conway's Law, measured.
Conway said system design mirrors org design. The new research from Microsoft and the DORA team puts a number on it: misaligned team topology costs the average 200-engineer org roughly 30% of its potential output. Here's how to measure your leak in one afternoon.
Melvin Conway wrote in 1968 that 'organizations which design systems are constrained to produce designs which are copies of the communication structures of those organizations.' For 50 years that was treated as a metaphor. In the last 24 months, three large-scale studies — Microsoft Research's 2024 paper on team topologies, the DORA 2024 State of DevOps report, and the SPACE framework data — have made it measurable. The honest number for the median 200-engineer org is sobering: roughly 30% of engineering output is lost to communication structures that don't match the systems being built.
The one-afternoon audit
- Pick your 5 most-changed services in the last 90 days (use your VCS commit data).
- For each, list the number of teams that committed to it. Anything >2 is a leak.
- For each, list the number of teams paged when it broke. Anything >1 is a leak.
- Multiply: services with >2 committing teams AND >1 paged team are your top-priority topology fixes.
- Expect 20–40% of your services to be in this category. That's your 30% output leak, visible.
- One team owns code, deploy, and on-call.
- PRs merged in <24h on the team's own services.
- Incident response routes to one Slack channel.
- Roadmap planning is a 90-min meeting, not a quarter-long negotiation.
- Three teams touch the same service every sprint.
- PRs sit for 5+ days waiting for the 'owning' team.
- Incident response requires 4 humans to triage.
- Roadmap planning eats two weeks every quarter.
HR & Operations leader scaling global remote teams across Nepal, the Philippines, Australia, and the US. Tech-leaning writing lives on Medium.