science & techWikipedia1967

Software ends up shaped like the organisation that built it, a pattern known as Conway's law

the gist

Conway's law says that any software reflects the communication structure of the organisation that produced it. The computer scientist and programmer Melvin Conway introduced the idea in 1967. Teams that rarely talk tend to build components with hard boundaries between them, while closely connected teams tend to build tightly integrated systems. Because the parts must fit together, the design ends up mirroring the social lines of the company. The law is applied mostly in software architecture, but Conway meant it to apply to most technical fields.

how it works

Components of a product must be compatible, so the people who build them have to coordinate. Where communication is hard, such as across departments or companies, the interfaces between components tend to be harder too. The technical design therefore picks up the social boundaries of the organisation.

so what

Conway's law explains why large products often have awkward interfaces that match old departmental divisions. Engineering managers use it to plan team structures on purpose, since changing the org chart can change the architecture.

fun fact

Melvin Conway is not the same person as John Horton Conway, the mathematician who invented the Game of Life.

more on this

From Wikipedia, the free encyclopedia · text CC BY-SA 4.0

Illustrative photo · Unuplusunu, Public domain, via Wikimedia Commons