Concept · part of When the map moves the territory

Compare two pieces of software that do the same job. One was built by an open-source community, loosely connected. The other was built by one company’s tightly knit staff. Researchers who made this comparison, pair after pair, found the community’s software was built from much more separate, swappable parts.

Melvin Conway said in 1968 that systems mirror the communication structure of the organizations that design them. Teams that rarely talk build components that barely depend on each other. Teams that talk constantly build things that are tangled together. A review of 142 studies found strong support in most of them, with open collaborative projects as the main exception.

An org chart is a framework people work inside without seeing it as one, and its shape comes out in the product. This is framework pricing again: talking to the next desk is cheap, and talking across departments is expensive. The useful part of Conway’s law is that it runs in reverse. If you want a system with certain seams, organize the teams along those seams first. The book argues the same way about institutions: what a curating institution can produce depends on how it is built and paid for.

Read the full argument

How it connects


← Looping effects · When the map moves the territory (14 of 17) · Path dependence and lock-in →

Explore all the ideas · Read the book in order · Open the interactive map