Conway's law

Conway's law is the observation that an organization designs systems whose structure copies its own communication structure. Melvin Conway stated it in a 1968 paper. If two teams rarely talk, the components they own will meet through a narrow, often awkward interface. The software ends up shaped like the org chart, whether anyone planned it or not.

How it works

Every interface between modules needs people to agree on it. Teams find it easy to coordinate inside their group and costly to coordinate across groups. So module boundaries settle where team boundaries are. A common illustration: four groups building a compiler will produce a four-pass compiler. The inverse Conway manoeuvre runs the other way. You shape teams around the architecture you want, and the system drifts toward it.

Why it matters in production

Architecture changes that ignore team structure tend to fail or slowly revert. A planned split into services stalls if one team still owns all of them. Ownership lines also decide who gets paged, so fuzzy team boundaries show up as slow incident response.