Inverse Conway Maneuver

Stop trying to fix the architecture without changing the org chart. Reorganize your teams around the system you want, and the architecture follows.

Conway’s Law tells you that your org chart will shape your architecture whether you plan for it or not. The Inverse Conway Maneuver flips this from a passive constraint into an active design tool: you deliberately reshape your team structure to mirror the architecture you want.

Traditional Conway’s Law describes the effects of a passive, implicit organizational structure: organization structure constrains system architecture. Your org chart accidentally dictates your software design. The Inverse Conway Maneuver flips the script and makes the law intentional: desired architecture drives your organization structure. You reshape your org to produce the architecture you need.

This is a core insight and strategic move behind Team Topologies. If you want independent, loosely coupled services, you need independent, loosely coupled teams. If you want a reusable and useful platform, you need a team that owns it as a product. Reorganizing the code without reorganizing the teams produces a distributed monolith and, worse, new dependencies that decrease Flow; the org chart reasserts itself.

Resources

• Conway’s Law — the constraint that makes this maneuver necessary
• Team Topologies — the framework that operationalizes this approach
• Organizational Design — workshop where this concept is applied