Conway's Law
Customers feel the handoffs created by the way a company is organised.
The systems a company builds often mirror how its people communicate and split responsibility.
The customer feels every handoff
A customer explains the same problem to onboarding, payments, and support.
Each team has its own tool, data, language, and definition of done. The customer repeats the same details, loses context at each handoff and can't find one person who owns the whole problem.
The customer ends up dealing with the same boundaries that exist between the teams.
Conway's Law says the systems people build tend to mirror how they communicate and split responsibility. Team boundaries become technical boundaries, and weak communication becomes awkward handoffs for customers.
Separate teams can create a fragmented customer journey
Onboarding, payments, and support each optimise their own part of the product. Each team builds a system that works for its own queue, but the customer journey breaks at the handoffs between them.
The architecture diagram may look intentional, but repeated handoffs usually show which teams share context and which ones need a formal request before they can coordinate.
You can see it beyond software
Hospitals. A patient experiences one illness while departments divide it into specialities, records, and handoffs. Clinical expertise requires boundaries; the patient suffers when information can't cross them.
Government. A citizen's housing, health, work, and identity problem can span several agencies. The person has one problem and still has to join a separate queue for each agency involved.
Product and service design. Customers have to learn which department owns each part of their problem and route themselves through the company.
Physical production. In buildings and films, poor coordination between trades, vendors or production units also appears in the finished work.
What to change when the same handoff keeps failing
When a system repeatedly breaks at the same organizational boundary, check whether the interface is unclear, the teams don't share enough context, or one outcome has been split across too many owners.
Sometimes you deliberately shape teams around the system you want to build. That's the inverse Conway manoeuvre. Conway's Law is a tendency, so check whether team boundaries are creating the technical boundaries you actually want.