Conway's law

Researchers have tested this many times, in different places, over many years, and they keep finding the same result. This one is safe to trust.

In 1967 a computer scientist named Melvin Conway wrote up an observation and sent it to Harvard Business Review. They rejected it on the grounds that he had not proved his thesis. He sent it instead to Datamation, a computing magazine of the day, which published it in April 1968 under the title How Do Committees Invent. The claim was simple and strange. Any organization that designs a system will produce a design whose structure copies that organization's own communication structure. Not as a metaphor, but literally. Four teams building a compiler will ship a compiler with four parts. A company where two departments barely speak will ship a product where two components barely connect. Fred Brooks cited the paper in The Mythical Man-Month and called it Conway's law, and the name stuck. Forty years after the rejection, researchers at Harvard Business School put it to the test, comparing software built by tightly coupled commercial firms against software of the same kind built by loosely coupled open source communities, and found the correspondence the law predicts.

Your customers are holding a physical copy of your org chart, and they experience it as friction. The reason becomes obvious once it is said aloud: people can only design what they can talk about, and they can only talk across the channels that already exist. Where the channel between two teams is thin, the connection between their two components will be thin, awkward and late. Almost every clunky handoff a customer feels is a thin communication channel made physical. The practical move, which engineering teams now use deliberately and call the reverse Conway maneuver, is to stop fighting the mirroring and use it. Decide what you want the product to look like, then arrange the teams to match, because the mirroring will happen either way and the only real choice is whether it happens on purpose. One honest limit: the research shows the correspondence clearly but does not settle which direction the causation runs, and documented exceptions exist, so treat it as a strong tendency rather than an iron law.

Source: Melvin Conway, How Do Committees Invent?, Datamation, April 1968. Empirical test: MacCormack, Baldwin and Rusnak, Exploring the Duality Between Product and Organizational Architectures, a Test of the Mirroring Hypothesis, Research Policy, 2012. On the limits: Colfer and Baldwin, The Mirroring Hypothesis, Theory, Evidence and Exceptions, 2016.

Draw your own card. It does not take long, and it rewards taking your time.