Technology
Conway's Law and Organizational Communication Structures
Quick fact
In 1968, computer scientist Melvin Conway observed that the structure of a software system often mirrors the communication structure of the organization that built it, leading to the famous phrase: 'organizations which design systems... are constrained to produce designs which are copies of the communication structures of these organizations.'
Why this is interesting
Ever wonder why many companies' software systems seem as tangled as their org charts? It might not be a coincidence.
Read the full explanation
Understanding Conway's Law and Organizational Communication Structures
Imagine you have a team of engineers building a large software application. If the team is split into two groups that rarely talk to each other, their code will likely end up as two separate pieces that don't integrate well. Converserly, if the team communicates freely and works together closely, the code will be more unified. Conway's Law captures this intuitive idea: the way people communicate and collaborate in an organization shapes the boundaries and interfaces of the technology they build. Why? Because each team tends to work on its own part of the system, and the seams between teams—where communication is limited—become the seams between software modules. So, if you want a certain system structure, you need to align your organizational communication accordingly.
A deeper explanation
Why does Conway's Law hold up? The key mechanism is informaton flow. When people communicate easily, they naturally share ideas, coordinate their work, and create consistent interfaces. When communication is stunted (e.g., due to departmental silos or geographical distance), those groups develop their own local conventions and interpretations, leading to divergent code that doesn't quite fit together. Over time, these discrepancies solidify into the architecture's boundaries. Formal structure, such as reporting lines, defines many communication channels, but informal networks matter too. This means that simply redrawing the org chart can change the path of information and, consequently, alter the system's design. That's why the 'Inverse Conway Maneuver' exists: to intentionally restructure teams to encourage communication patterns that will produce a desired architecture, like aligning teams with service boundaries. Conway's Law is not an excuse for poor design, but a foresight tool—it tells you that organizational design and system design are inseparable.