Loading content
Conway's Law states that an organization's structure influences the structure of the software it develops. If a company is organized in silos, the software is likely to be structured in silos as well. This has far-reaching implications for efficiency, communication, and ultimately the success of software projects.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Conway's Law describes the tendency for a system's architecture to mirror the communication and organizational structure of the people who design it.
Melvin E. Conway formulated the idea in the 1968 Datamation article "How Do Committees Invent?". He started from a practical design problem: teams must split work, coordinate, and define interfaces through limited communication paths. The article presents a relationship between social communication structure and system design, not a fixed natural law.
Think of the organization as a communication network. Where direct coordination is easy, components can be integrated more tightly; where communication runs through few handoffs, separate modules tend to emerge. Every team boundary quickly becomes a technical interface, and every interface needs upkeep. In that sense, responsibilities and coordination friction often shape the architecture.
How people exchange information influences how work is split into technical parts.
Department and team boundaries often encourage separate system boundaries and clear ownership.
When groups work separately, their outputs must fit together through defined handoffs.
Systems are often divided into parts that match organizational work boundaries.
The system's structure, its parts, and their relationships reflect organizational choices.
The idea is useful for team design, reorganization, platform and domain boundaries, and architecture diagnosis. It helps explain why silos can create difficult handoffs and unclear interfaces. But the relationship is a tendency, not a law of nature: good architecture can intentionally reshape communication paths, and business, security, or compliance constraints set their own limits.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.