Conway’s law
Conway’s law states that any organisation that designs a system will produce a design whose structure mirrors the organisation’s own communication structure. The shape of what you build copies the shape of how your teams talk.
How it works
Interfaces in a product form at the seams between teams, because the people who must negotiate a boundary are the people who don’t share a room or a manager. Change the communication structure and the system’s structure follows.
How to use it
- Predicting architecture: a product built by four siloed teams will tend to have four loosely-joined modules with awkward seams between them.
- The “inverse Conway manoeuvre”: deliberately shape teams to match the architecture you WANT, so the org produces it.
- Diagnosing integration pain: clumsy interfaces between components often trace to poor communication between the teams that own them.
Worked example
If a company splits its app into separate “front-end” and “back-end” departments that rarely talk, the product tends to ossify into a rigid front-end/back-end split with a brittle API in between — the software’s seam sits exactly where the org chart’s seam sits.
Where it fails
It describes a tendency, not an iron law — disciplined design can resist it. Treated fatalistically, it becomes an excuse (“our architecture is bad because our org is bad”) instead of a lever to redesign teams.
Frequently asked
- What is Conway’s law?
- The principle that the structure of a system you design ends up mirroring the communication structure of the organisation that designed it.
- Who is Conway’s law named after?
- Computer programmer Melvin Conway, who stated it in a 1967 paper (“How Do Committees Invent?”).
- What is the inverse Conway manoeuvre?
- Deliberately structuring teams to match the desired software architecture, so the organisation naturally produces that architecture.
Related
Editorial synthesis © ReadGlobe 2026, drawing on the mental-models tradition (Charlie Munger, Farnam Street) and the primary sources for each model. · Last reviewed 2026-06-30.