What Was Never Written Down
Customer journeys and business processes describe the same mechanism observed from opposite sides, but most organisations treat them as separate concerns owned by different functions. The disconnection means no one owns the transitions where work actually fails.
A retail bank decides to map its mortgage origination process. Three departments are involved: the digital team that owns the online application, the credit risk team that owns the decisioning, and the operations team that handles document verification and disbursement.
A workshop is convened, and within twenty minutes it becomes clear that the three departments are describing different processes. The digital team presents the customer journey, a funnel of form, documents, provisional offer, acceptance, and funds, optimised against analytics that show where users drop off. The credit risk team presents a decisioning flow governed by SLAs, audit requirements, and a regulatory obligation to explain every decision. The operations team presents a fulfilment process of checklists and exception queues, with a backlog of applications “stuck” for reasons no system tracks.
Each team's description is internally coherent, and none of them connect. The digital team does not know what happens between “provisional offer” and “funds received,” and the operations team does not know why applications arrive with missing documents, because the upstream systems do not enforce completeness.
At the end, the facilitator produces a diagram that connects the three views. Everyone agrees it is useful, and it is saved to a shared drive. It exists independently of any underlying system, has no formal versioning, and is not updated when the digital team redesigns the application form six months later.
When the redesigned form collects data in a format the scoring model cannot ingest, a manual workaround introduces a two-day delay and customer complaints increase. The delay is attributed to “operations.”
The diagram is never consulted again. One of the most persistent sources of confusion in software-dependent corporates is the belief that business processes and customer journeys are different concerns, owned by different functions and reconciled only when a problem makes the disconnection visible.
A customer journey is an outside-in view of how value is experienced, the sequence of interactions through which a person achieves something meaningful: apply for a mortgage, file a claim, renew a policy, return a product. It emphasises intent, friction, and outcome.
A business process is an inside-out view of how that same value is produced, the activities, decisions, and state transitions required to fulfil that intent: receive an application, check completeness, assess creditworthiness, generate an offer, verify documents, disburse funds. It emphasises responsibility, constraints, execution, and failure modes.
...
Continue reading in the interactive reader
Read this chapterSee also: Full contents · Preview chapters · Illusions in the Boardroom