23/08/2026
Why Your Customer Experience Looks Just Like Your Org Chart: Conway’s Law in Service Industries
I am old enough to have forgotten much of what I learned in my earlier career (most of which was focussed on large scale software and system engineering). Therefore it is always nice to be reminded of something “old” and realise it is still incredibly relevant and applicable today.
My latest re-discovery is the phenomenon known as Conway’s Law. While originally coined in the field of software engineering, Conway’s Law is the key to understanding why service industries so often deliver fragmented customer experiences—and why methodologies like Design & Lean Thinking can be used to fix them.
For example, we have all been there; You contact a service provider because you have a problem. First, you must navigate an automated system seemingly designed to deter you and eventually if you persevere you manage to speak to a human in a contact centre. They then transfer you to tech support. Tech support decide the issue is a billing error, so they transfer you to that department and so on, at every step, you must re-verify your identity, explain your problem from scratch, and wait on hold. Sometimes the call is inexplicably cut-off and you have to start all over!
Your customer experience is disjointed because the company’s internal departments are disjointed and specifically require multiple handovers.
What is Conway’s Law?
In 1967, computer scientist Melvin Conway observed that:
"Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations."
In plain English: The product or service you deliver will end up shaped exactly like your company's org chart. If your internal divisions don't talk to each other seamlessly, your customers will feel every single one of those internal seams (they are sometimes even chasms!).
Customer Journey Mapping Exposes the Org Chart
A service is simply a sequence of interactions. In Design Thinking, teams use a tool called Customer Journey Mapping to visualize an end-to-end user experience across every touchpoint.
When you lay out a service journey map, Conway’s Law becomes glaringly obvious. Every time a customer experiences friction—a redundant form, a long wait, a request for information already provided, or a dropped call transfer—you are almost certainly looking at an internal organizational boundary. The journey map acts as a diagnostic mirror: customer pain points highlight the communication gaps between your internal departments.
When teams don't communicate well internally, the burden of bridging those internal gaps is inevitably pushed onto the customer.
Let’s look at two examples of how Conway’s Law manifests across differing service sectors.
Example 1: Healthcare and the Fragmented Patient Journey
As a young student every vacation I worked as a hospital porter in a large London teaching hospital. This gave me first-hand experience of a complex organisation where lives are at stake. Hospitals are notoriously siloed, traditionally structured around deep medical specialties (Cardiology, Radiology, Oncology) and administrative silos (Admissions, Billing, Outpatients). Looking back my role was to move patients between departments and, except for my cheery disposition, I did not add much that was positive to a patient’s experience; it usually began and ended with a long “wait”.
The Conway Effect: Because these departments operate as highly specialized, separate entities with distinct communication chains, the patient experiences a highly fragmented service. A patient might have to give their family medical history to the intake nurse, repeat it to the attending doctor, and repeat it again to the specialist. Later, they receive three separate bills from the hospital, the radiologist, and the lab. The patient's healthcare journey is an exact copy of the hospital's internal departmental boundaries.
Example 2: The B2B SaaS Onboarding Trap
In business-to-business (B2B) services, companies are often cleanly divided into Sales, Implementation/Onboarding, Finance and Customer Support,
The Conway Effect: The Sales team promises the client the world but doesn't document the client's specific technical needs because they don't talk to the Implementation team. The Implementation team sets up a generic template because they don't know what Sales promised. Finance push to go live (often prematurely) so that invoicing can commence. Once “live” the client has an issue and calls Customer Support, who have no record of what the Implementation team did. Everyone involved including the employees and the client experience pain.
To succeed, service design requires the Inverse Conway Manoeuvre: intentionally restructuring internal teams to mirror the ideal customer journey map. Design Thinking advocates for empathy-driven, human-centred design—focusing on user needs rather than internal corporate convenience. However, if your company's structure remains rigid, even the most elegant design thinking sessions will fail during ex*****on because Conway’s Law will drag the service back into internal silos. This is where Lean Thinking comes in. Conway’s Law diagnoses the structural cause of friction in a system, while Lean provides the framework to eliminate it.
Hand-Offs Are the Primary Location of Problems
A core principle of Lean is the relentless elimination of waste such as delays, errors, and over-processing. Conway’s Law reveals the root cause of this waste in service delivery. Whenever a service process crosses an organisational boundary, for example moving a ticket from front of house to second-line support, communication breaks down and context is lost. In Lean terms, every departmental “seam” predicted by Conway’s Law is an active waste-generator.
Value Stream Mapping vs. The Org Chart
Lean relies on Value Stream Mapping to visualise how value actually flows to the customer. Conway’s Law serves as a direct warning: if your communication pathways remain locked in functional silos (e.g., separate intake, processing, and billing departments), your value stream will inevitably stall at those internal borders. To optimize value flow, you cannot just optimize individual departments; you must dismantle the communication barriers between them, so the service moves continuously without stopping at organizational hand-offs.
Creating "Service Cells" to Achieve Flow
To achieve continuous Flow, traditional Lean manufacturing replaced functional departmental batching (putting all stamping machines in one hall and all paint booths in another) with "work cells"—arranging different machines in sequential order around a specific product. In service industries, Lean applies this same logic by grouping multi-disciplinary staff into dedicated customer-value teams. By organising people around the flow of value rather than functional titles, you rewrite the communication structure using Conway's Law to automatically yield a seamless, waste-free customer experience.
Design Thinking gives you the approach to map a seamless customer experience, and Lean Thinking gives you the tools and continuous improvement methodology needed to survive Conway's Law. You cannot fix a broken service experience with a surface-level redesign. To change what customers experience at the end of a journey on the “outside”, you must first align the communication structure on the “Inside.”
© Serious Consulting Pty Ltd 2026
The Author as Hospital Porter in 1984 (just like Douglas Adams!)
