Home › Leadership › Concepts
Conways Law
Leadership / Concepts · Updated Apr 2026
"Any organisation that designs a system will produce a design whose structure is a copy of the organisation's communication structure." - Melvin Conway, 1967
What It Means
Your software architecture will mirror your org chart. If you have three teams, you'll get a three-part system. If teams don't talk, their systems won't integrate well.
Why It Matters for Engineering Leaders
- You can't fix architecture without fixing team structure.
- When you see integration problems, look at how teams communicate.
- Team boundaries become API boundaries.
The Inverse Conway Manoeuvre
Design your teams to match the architecture you want, not the one you have. The org structure will pull the software in the right direction.
Examples
- Microservices work best when each team owns one service.
- A monolith often reflects a single, tightly-coupled team.
- Cross-cutting concerns (auth, logging) struggle when no team owns them.
Related