Strategy documents are easy. Operating models are hard. A CX strategy can be written in a week and admired for years while changing nothing, because the gap between ambition and reality is bridged not by vision but by structure — who owns what, who decides what, and how often the organization stops to look.
An operating model is that structure. It is the least glamorous part of the work and the part that most reliably determines whether anything actually happens.
The three questions an operating model answers
Strip away the diagrams and a CX operating model exists to answer three questions, unambiguously.
- Who is accountable for the experience? Not who cares about it — who is measured on it and answers for it.
- How do decisions get made? When a customer signal and an operational constraint collide, who arbitrates, and on what basis?
- What is the rhythm? How often does the organization formally review experience, prioritize, and commit resources?
Where these questions have crisp answers, CX tends to work. Where they are fuzzy, it tends to stall regardless of how good the strategy reads.
Accountability without authority is theater
A common failure is appointing a CX leader with a mandate but no authority — responsible for outcomes they cannot influence because the levers sit in operations, IT, and the business lines. The role becomes an internal advocate who can persuade but not decide. The fix is not a bigger title; it is wiring the CX function into the decisions that actually shape the experience, through clear accountabilities and a seat where trade-offs get made.
A CX leader with responsibility but no authority is being set up to apologize, not to lead.
RACIs that survive the first hard call
Accountability maps look tidy until the first genuine conflict — when fixing an experience problem costs a business line something. A model that works has decided in advance who is accountable, who is consulted, and who decides when interests collide. The test of a RACI is not how it reads in a deck; it is whether it holds when the first expensive trade-off arrives.
The cadence is the product
If there is one component to get right, it is the review rhythm. A standing forum — monthly or quarterly — where leaders look at experience signals, prioritize, and commit resources is what converts a strategy from a document into a practice. Without it, even a well-designed model goes quiet between crises. The cadence is what keeps the system honest.
Build the minimum that works
Operating models fail more often from over-engineering than from under-design. A heavyweight governance structure with a dozen committees collapses under its own weight. Start with the smallest set of roles, accountabilities, and forums that answers the three questions, and add structure only when the work demands it. The goal is a model people actually use, not one that wins an architecture award.