CONCEPT
Conway's Law
Organizations designing systems produce designs that copy their communication structures — the 1968 observation that became software engineering's most durable principle.
Melvin Conway's 1968 observation states that any organization designing a system will produce a design whose structure mirrors the organization's communication patterns. Originally rejected by Harvard Business Review for lacking empirical proof, the insight appeared in Datamations and was later elevated to "law" status by Fred Brooks in The Mythical Man-Month. A four-team organization produces a four-component system; hierarchical companies build hierarchical architectures. This isn't coincidence but structural necessity: teams that cannot communicate directly cannot design tightly integrated interfaces. The law has survived mainframes, the internet, mobile computing, and agile methodologies because it describes something fundamental about human coordination rather than something about technology.
In The You On AI Field Guide
The law's durability across six decades of radical technological change reveals that it addresses a constraint more fundamental than any particular computing paradigm. When Conway submitted his paper in 1967, computers filled entire rooms and were programmed in FORTRAN and COBOL. Today's smartphones carry more computing power than existed globally in 1967, yet the law holds with the same precision.