Conway's Law

Organizations produce system designs that mirror their own communication structures. The corollary, the Inverse (Reverse) Conway Maneuver, is to deliberately shape teams and communication paths so the system evolves toward a target architecture.

Why it Matters

Architecture and organization are coupled whether or not anyone plans it. Ignore the law and the org chart silently dictates the architecture; use it and team design becomes a tool for achieving the structure you actually want.

Signals

• Module boundaries that line up with team boundaries.
• Integration pain appearing exactly where two teams must coordinate.
• An architecture no one explicitly designed but everyone recognizes as "how we're organized."

Benefits

Explains why reorganizations reshape systems and vice versa. Applied deliberately, it lets you obtain a desired architecture by structuring teams to match it.

Risks

Reorganizing to chase an architecture is disruptive and slow. Forcing team structure to satisfy a diagram can ignore delivery and human realities.

Tensions

The architecture you want may not match the teams you have, and changing either to fit the other carries real cost. Pulls against the value of stable, long-lived teams when restructuring is frequent.

Examples

Splitting one team into two tends to split their shared component in two. Wanting loosely coupled services, you create independent teams so the maneuver produces that coupling.