Treating customer experience as an organisational function is one of the most consequential category errors in modern business. Experience is not produced by a team. It is produced by the cumulative effect of every structural decision the organisation has made about how it operates.
The creation of a CX function — a dedicated team, a Chief Customer Officer, a budget line, a set of metrics — is one of the most common responses to declining customer experience quality. It is also, in many cases, one of the most expensive ways to avoid addressing the actual problem.
This is not an argument against CX functions or CX leadership. Both are valuable. The problem is what the decision to create them often signals about how the organisation understands customer experience — as something that can be owned by a function, managed by a team, and improved through the right combination of capability, tools and measurement frameworks. This understanding is structurally incorrect, and it produces a particular kind of failure: significant investment in CX that never closes the gap between the experience the organisation intends and the one it delivers.
Customer experience is produced across every function in a consumer-facing organisation. The decision the finance team makes about payment terms affects the experience. The decision the technology team makes about system architecture affects the experience. The decision the logistics team makes about delivery windows affects the experience. The decision the HR team makes about frontline hiring standards affects the experience.
None of these decisions are made by the CX function. Most of them are not made with customer experience quality as a primary consideration at all. They are made with operational efficiency, cost management, technical feasibility and commercial performance as the primary considerations — which are legitimate priorities, but which, when pursued without structural mechanisms to account for their effect on customer experience, consistently produce experience outcomes that no amount of CX investment downstream can fully correct.
The customer experience is the output of the organisation's entire operating model. It is the cumulative effect of thousands of structural decisions — about how the organisation is designed, how it governs itself, how it distributes accountability, how it makes decisions across functions, and what it considers when making those decisions. A CX function can influence some of these. It cannot own them, govern them or change them without the structural authority and cross-functional mandate that most CX functions are never given.
A CX function can influence the structural conditions that produce customer experience. It cannot own them, govern them or change them without authority it is almost never given.
The most damaging consequence of treating CX as a function is the accountability mismatch it creates. The CX function is accountable for experience outcomes it does not structurally control. It is responsible for NPS, CSAT and customer effort scores that are determined by decisions made in functions it does not govern. It is expected to close an experience gap that has structural causes it was not given the authority to address.
This mismatch is not just frustrating for CX leaders — though it is that. It is structurally self-defeating. An organisation that holds its CX function accountable for experience outcomes without giving it the structural authority to address the operating model conditions that produce those outcomes has not created accountability. It has created a sophisticated mechanism for avoiding it. The CX function becomes the organisational proxy for a structural problem that only leadership has the authority and responsibility to solve.
The organisations that understand this do something different. They treat customer experience accountability as a cross-functional structural commitment — not a functional mandate. They design governance mechanisms that engage with experience outcomes at the level where experience is actually determined: in operating model decisions, in cross-functional accountability structures, in the leadership decisions that shape how the whole organisation works. The CX function in these organisations is genuinely powerful — not because it has been given a broader mandate, but because the structural conditions for delivering great experiences have been embedded in the way the whole organisation operates.
Reframing customer experience as a structural outcome rather than a functional responsibility changes what leadership needs to do. It does not remove the need for CX capability, CX measurement or CX leadership. It changes what those things are for and what they can realistically achieve.
CX capability becomes the diagnostic and design capability that helps the organisation understand what its structural conditions are producing and what changing them requires — not the operational function that manages customer interactions downstream of structural decisions it had no part in making.
CX measurement becomes the mechanism that makes the structural consequences of operating model decisions visible to the leadership level where those decisions are made — not the reporting function that documents experience quality without any structural mechanism to connect that documentation to the decisions that produced it.
CX leadership becomes the organisational role with the structural authority and cross-functional mandate to engage with the decisions that determine experience quality — not the executive who presents NPS trends to a leadership team that controls the structural conditions but does not see them as CX decisions.
This reframe requires leadership commitment at a level that most CX transformation programmes do not demand. It requires the CEO and the board to make explicit structural decisions about how customer experience outcomes are governed, who is accountable for them at the structural level, and what the operating model implications are. That is harder than creating a CX function. It is also the only intervention that actually works.