Conway's Law
The structure of a system often reflects the communication structure of the organization that creates it.
The Mechanism: Conway's law is an observation that organizations tend to produce systems whose designs mirror their communication structures. Teams separated by responsibility may build components that reflect those boundaries.
The Philosophical Pivot: Technical architecture is not only a product of engineering choices; it can encode assumptions about who talks to whom. A system may preserve organizational silos long after the original reason for them has faded.
The Horizon: The idea has influenced software architecture and team design, but it is a heuristic rather than a deterministic rule. Technology, standards, and deliberate cross-team collaboration can alter the relationship.
Reorganizing teams does not automatically improve a product, and a clean architecture cannot repair every social conflict. Both structures need to support the work people actually do.
A design review may reveal communication problems that an organizational chart hides.
Changing a system may require changing the conversations through which its parts are imagined and built.
The shape of a product can preserve the shape of the conversations that created it.
Which boundary in this system exists because the organization still struggles to communicate across it?