Most organisations design the experience. Almost none design the model that makes it deliverable. The gap between customer experience ambition and customer experience reality is not a CX problem. It is a structural one.
There is a question that every organisation with a customer experience strategy should ask itself — and almost none do. Not: what experience do we want to deliver? But: is our operating model structurally capable of delivering it?
The first question gets considerable attention. Journey mapping, service design, voice of customer programmes, NPS frameworks, CX transformation roadmaps. Organisations invest substantially in understanding and defining the experience they intend to deliver. What they invest almost nothing in is the structural question underneath: whether the way the organisation actually operates — how it makes decisions, distributes accountability, governs across functions and manages performance — is capable of producing that experience consistently, at scale, across every market and channel it operates in.
This is not a minor gap. It is the reason most CX investment fails to close the experience gap it was designed to address.
An operating model is the set of structural decisions that determine how an organisation works: how decisions are made and at what level, how accountability is distributed across functions and roles, how performance is governed and consequences assigned, how coordination happens across organisational boundaries, and how the organisation scales its capacity without losing the quality of what it delivers.
Every one of these decisions directly determines customer experience outcomes. Not in the abstract — concretely, in the interactions customers have every day.
When a customer contacts an organisation and gets a different answer from two different channels, that is an accountability and governance problem — not a training problem. When a customer's issue requires escalation because the frontline team doesn't have the authority to resolve it, that is a decision rights problem — not a capability problem. When experience quality is excellent in one market and poor in another, that is a consistency and operating model problem — not a management quality problem in the underperforming market.
The experience the customer receives is the output of structural decisions the organisation made — usually without explicitly considering their effect on customer experience at all.
The experience the customer receives is the output of structural decisions the organisation made — usually without explicitly considering their effect on customer experience at all.
The reason organisations invest heavily in the experience and lightly in the operating model is partly structural and partly cognitive. The experience is visible. It can be designed, mapped, measured and presented to leadership in a form that feels like progress. Journey maps have a clarity that operating model architecture doesn't. NPS scores move in ways that operating model health indicators rarely do, at least in the short term.
The operating model, by contrast, is largely invisible until it fails. It lives in the structures, processes and governance decisions that most organisations consider separately from CX — in operational efficiency programmes, in organisational design exercises, in governance reviews that are not framed as customer experience investments at all. The connection between operating model decisions and experience outcomes is real and direct, but it is rarely made explicit in the room where either type of decision is being made.
The result is organisations that have invested significantly in understanding and designing the customer experience, and almost nothing in designing the structural conditions that would make that experience consistently deliverable. The journey map is excellent. The operating model cannot produce what it describes.
Designing an operating model with customer experience quality as a structural output requires a set of decisions that most organisations have never been explicitly asked to make. Who structurally owns customer experience outcomes — not as a CX function mandate, but as a board-level accountability? How are decisions that affect customer experience made across functional boundaries, and who has the authority and obligation to make them? What are the governance mechanisms that ensure experience quality is monitored, discussed and acted upon at the structural level where it is actually determined?
These are not CX questions. They are operating model questions. They require leadership engagement that goes beyond the CX function, because the structural conditions for great customer experience are not within the CX function's authority to create alone. They require the CEO, the COO and the board to make explicit structural commitments — to accountability architecture, to governance design, to operating model choices — that most organisations have not yet made in the language of customer experience.
Organisations that consistently deliver exceptional customer experiences are not necessarily the ones with the best CX teams or the most sophisticated journey mapping. They are the ones where the structural conditions for delivering great experiences are embedded in how the whole organisation works — in its governance, its accountability architecture, its operating model design. That is an outcome of structural decisions, not attitudinal alignment. And it requires a fundamentally different kind of investment than most CX programmes are designed to make.