Skip to content
BENIBIX Learn

Conway's Law

Development🏗️ ArchitectureArchitecture Basics

Also known as Conway Law

A system's parts copy the teams that built it. They join where the teams talk.

Think of it like

It is like three kids building one sandcastle. Each one builds a tower, so it has three towers.

Example

One team builds the website and another builds the app. They rarely talk, so the two end up with different prices for the same item.

Why it matters

You cannot fix a system's shape while the teams around it stay the same. The team chart and the system chart move together.

Definition

Conway's law says a system's design copies the way its makers talk to each other. Melvin Conway made the point in a 1968 paper called How Do Committees Invent? If four teams build a program, it tends to come out in four parts. The parts join where the teams talk, and they stay apart where the teams do not. Fred Brooks later gave the idea its name.
Three teams, three parts. The links between the parts follow the links between the teams.

Common mistake

Treating it as a rule only for software. It holds for any system a group of people designs.

Key takeaways

  1. 1
    Mirror image. Systems copy who talks to whom.
  2. 2
    Team lines. Team lines become system lines.
  3. 3
    Teams first. Change teams to change the system.