Conway's law
Conway’s law is the observation that a system’s structure tends to reflect the communication structure of the organization that designs it.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
Conway's law is the principle that a system's architecture tends to reflect the communication structure of the organization that designs it.
- How it is used
- Guides modernization by jointly shaping team organization, communication, domain boundaries, and software architecture.
- How deep it goes
- Defines the principle, diagnoses organizational failure modes, and gives alignment guidance without prescribing a complete organizational design.
- Examples
- Uses siloed teams, broken cross-team changes, siloed data, and collaborative EventStorming as concrete illustrations.
- What you can do after
- Diagnose mismatches between organizational communication and architecture, then identify better-aligned teams, domains, and collaboration boundaries.
Grokking Software Architecture
Conway's law is the observation that a system's architecture tends to reflect the communication structure of the organization that designs it.
- How it is used
- Frames microservices as a response to organizational scaling and deployment coordination, rather than as a performance upgrade.
- How deep it goes
- Defines the law and illustrates team-size and release-queue consequences, without giving a method to measure communication structure.
- Examples
- Uses a 5–15-person team, a 500-person distributed organization, and Inventory/Billing release coordination.
- What you can do after
- Evaluate architecture choices by considering team scale and whether teams need independent release schedules.
Read how Grokking Software Architecture explains Conway's law →
Also covered in
- Architecting for AutonomyIn early access (MEAP)
- Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu
- The Design of Web APIs, Second Edition
What to know first
- model architectureModel architecture is the structural arrangement of a computational model’s components, connections, and operations that determines how it processes inputs and produces outputs.
Related concepts
- model architectureconfigures · Model architecture is the structural arrangement of a computational model’s components, connections, and operations that determines how it processes inputs and produces outputs.
- team topologiesuses · Team Topologies is an organizational design framework for structuring teams and their interactions to improve the flow of value in software delivery.
- contractuses · A contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
- modernization initiativeused by · A modernization initiative is a planned effort to update existing software, technology, architecture, or organizational capabilities to meet current needs.
- couplingproduces · Coupling is the degree of interdependence between software components, including their dependencies on one another’s structure, behavior, or availability.
- microserviceimplemented by · A microservice is an independently deployable service that implements a focused business or technical capability within a larger application or distributed system.
Questions about Conway's law
What is Conway's law?
Conway’s law is the observation that a system’s structure tends to reflect the communication structure of the organization that designs it.
Which Manning books explain Conway's law?
Architecture Modernization: Socio-technical alignment of software, strategy, and structure and Grokking Software Architecture.
What should I know before learning Conway's law?
Manning books that teach Conway's law usually introduce model architecture first.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

