Inverse Conway Maneuver
Updated 2026-08-08
INTRODUCTION
English translation pending.
CORE DEFINITION
Named after Melvin Conway's observation that system designs mirror the communication structures of the organizations that build them, the inverse maneuver turns the relationship around: decide the architecture you want, then reorganize teams and interfaces so the organization produces it. The core claim is that structure shapes output more reliably than instruction does. The qualification is that reorganization carries transition costs and only works when architecture and team boundaries change together.
SCAFFOLDING EFFECT
Reduce cognitive load
- Use Target Architecture: Specify the system structure you want before touching the org chart. - Use Boundary Setting: Define team boundaries and interface ownership to match the target structure. - Use Dependency Cutting: Remove cross-team dependencies that would recreate the old architecture.
Anchor fast decisions
Teams produce designs that fit their own communication paths, because coordination across a boundary is expensive and interfaces tend to form where interaction is easiest. Changing who talks to whom therefore changes which interfaces appear and which services stay coupled. Because the architecture follows the communication structure automatically, restructuring the organization is a more reliable way to reach a target design than mandating it directly.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Conway%27s_lawverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS