This guide assumes:

• Familiarity with Conway’s Law. Read What Is Conway’s Law? first if “communication structure shapes system structure” sounds new.
• You work on or with a platform team. This means a team that owns shared infrastructure consumed by multiple product teams.
• Visibility into platform PR queues, product-team workflows, and meeting calendars. Without these signals, you cannot measure friction.
• Influence over platform priorities, or a partner who has it. The fixes below require changing what the platform team does, not what product teams ask for.

Measure the friction budget

Platform teams own shared infrastructure that many product teams depend on. Heavy edit volume across multiple teams is normal. Slow shipping and burned-out engineers are not.

This guide assumes:

• Familiarity with Conway’s Law. Read What Is Conway’s Law? first if “communication structure shapes system structure” sounds new.
• Access to git history. You will read commit patterns over the last quarter.
• Visibility into the org chart. You need to know which engineers belong to which teams.
• Influence over team boundaries, or a stakeholder who has it. The fixes below require organizational change, not technical work.

Read the alignment

Conway’s Law works both directions. Observe the code, and you can infer the organization. Use that to understand where the org is healthy and where it is broken.

This guide assumes:

• Familiarity with Conway’s Law. Read What Is Conway’s Law? first if “communication structure shapes system structure” sounds new.
• Concrete evidence from your own org. A diagnosis from How Do I Diagnose Delivery Friction? or a deployment decode from How Do I Decode a Deployment? gives you the artifacts to point at. Without evidence, the pitch sounds like opinion. Start there if you have not yet.
• An audience. Architects, product leaders, your own team, an open-source community, or conference attendees. The pitch shifts with each.

Bring both halves to every conversation

Most conversations about software architecture skip the organizational layer entirely. Engineers debate microservices versus monoliths. Leaders debate team structure in isolation. The two conversations rarely connect. Use Conway’s Law to make the connection explicit.

This guide assumes:

• Familiarity with Conway’s Law. Read What Is Conway’s Law? first if “communication structure shapes system structure” sounds new.
• A local clone of the repository you want to analyze. The diagnosis below is a git query.
• A POSIX shell with awk, sort, uniq, and cut. Standard on macOS and Linux.
• Visibility into the org chart. You need to map author emails to teams.

Rank the congestion candidates

Start by looking at the slowest, most contentious modules. Files with commits from many different authors over the last quarter signal congestion.

This guide assumes:

• Familiarity with Conway’s Law. Read What Is Conway’s Law? first if “communication structure shapes system structure” sounds new.
• Access to the deployed system. You need to see the service list, runbooks, and on-call rotations.
• Visibility into pipelines and release boundaries. You need to know which services ship together and which ship separately.
• A blank document or whiteboard. You will sketch a map as you go.

Walk the deployment

Treat deployed software like a fossil record. Every service boundary, API contract, and deployment pipeline carries the imprint of the people who shipped it. Walk the deployment in this order:

You redraw the org chart. Six months later, the codebase has grown new seams along the new team boundaries. The teams reshaped the software without intent.

That pattern has a name: Conway’s Law. Any system you ship will reflect the communication structure of the people who built it. Modules align with teams. Interfaces form along reporting lines. Coordination friction shows up as code friction.

This matters because technical leaders keep treating organizational problems as technical problems. A microservice split fails when two teams still own a single service. A monorepo grows congested because four teams edit the same file. The architecture is doing exactly what the org chart told it to do.