# Conway’s Law

The observation that systems tend to reflect the communication structures of the organizations that design them.

- Type: principle
- Domain: Leadership & teams
- Level: Intermediate
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/conways-law/>)

## What it means

Conway’s Law states that organizations designing systems are constrained to produce designs that mirror their communication structures. It is an organizational observation, not a deterministic engineering law: architecture and organization influence each other over time.

## Why it matters

Team boundaries, dependencies, and communication paths can shape product architecture and user experience, so organization design is part of product and technical design.

## When to use it

Use it when examining ownership boundaries, modularity, integration friction, or reorganization consequences. Treat it as a hypothesis to inspect rather than a prediction that excuses poor architecture.

## How it works

1. Map communication paths and decision ownership.
2. Map system boundaries and dependency flows.
3. Compare mismatches and repeated coordination costs.
4. Change team interfaces or architecture deliberately.
5. Observe whether the system and communication improve together.

## A practical example

A company split into separate catalog and checkout departments repeatedly creates duplicated product data; aligning ownership around a shared product flow reduces the integration boundary.

## Where it breaks

Many technical, market, and historical factors shape architecture; reorganizing teams can disrupt delivery and does not automatically improve design.

## Common mistakes

- Treating the law as a universal causal rule.
- Reorganizing without understanding product boundaries.
- Assuming a team chart alone changes communication behavior.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/conways-law/#visualization-conways-law>)

## Sources

1. [How Do Committees Invent?](<http://www.melconway.com/Home/Committees_Paper.html>) — Melvin E. Conway · Original author essay
2. [Conway’s Law](<https://martinfowler.com/bliki/ConwaysLaw.html>) — Martin Fowler · Authoritative software architecture commentary

## Related topics

- [Organizational Silos](<https://wiki.soroush.uk/topic/organizational-silos/>)
- [Team Cognitive Load](<https://wiki.soroush.uk/topic/team-cognitive-load/>)
- [Cross-Functional Team](<https://wiki.soroush.uk/topic/cross-functional-team/>)
