Customer Experience Management Field Manual: A Practitioner's Review

Most CX programmes fail not because the strategy was wrong, but because no one treated CX as an operation. There was a vision deck, perhaps a journey map pinned to a wall, and a quarterly NPS review — but no standard operating procedures, no governance rhythm, no mechanism for turning insight into action. Jeff Sheehan's Customer Experience Management Field Manual (Boston Business Books, 2019) is one of the few practitioner texts that confronts this directly. It does not ask you to believe in customer-centricity. It asks you to run it like a function.

That distinction matters enormously. CX strategy and CX management are different disciplines, and conflating them is where most programmes unravel. Strategy sets direction; management sustains execution. Sheehan's book is almost entirely about the second — and that makes it unusual, and unusually useful.

What Is Customer Experience Management, and Why Does It Need a Field Manual?

Customer experience (CX) management is the disciplined, ongoing practice of designing, measuring, and improving every interaction a customer has with an organisation — governed by clear accountabilities, informed by real data, and connected to business outcomes. It is not a campaign, a survey programme, or a set of service standards. It is a permanent operational function, no different in principle from finance or supply chain.

The field-manual metaphor Sheehan borrows from military doctrine is apt. A field manual does not explain why a mission matters; it explains how to execute it under pressure, with limited time and imperfect information. That is precisely the condition most CX leaders operate in. They know the destination. What they lack is the procedural clarity to get there without losing momentum every time a sponsor changes, a budget is cut, or a new CEO arrives with different priorities.

Sheehan draws on more than 25 years in customer strategy, support operations, and digital transformation — and his former career as a U.S. Army officer and helicopter pilot — to argue that CX programmes need the same kind of doctrine that military units rely on: repeatable processes, defined roles, and a shared operating language that survives personnel turnover.

The Eight Core Functions: A Framework Worth Examining

The book's architecture is built around eight integrated functions. They are worth naming precisely, because the sequence is deliberate — each function creates the conditions for the next.

1. CX Leadership — setting the mandate, securing executive sponsorship, and defining what the CX function is authorised to do.
2. CX Culture — embedding customer-first behaviours into the organisation's operating norms, not just its values statements.
3. CX Audit — establishing a baseline: what the current experience actually is, not what the business believes it to be.
4. Customer Understanding — building a continuous, structured picture of customer needs, behaviours, and expectations through Voice of Customer and other research methods.
5. Journey Mapping Operations — running journey mapping as a repeatable operational process, not a one-off workshop.
6. CX Strategic Plan — translating insight into a prioritised, resourced, time-bound plan with clear business cases.
7. CX Governance — the structures, forums, and accountabilities that keep the programme alive and connected to the rest of the organisation.
8. CX Change Management — managing the human side of CX transformation: resistance, capability gaps, and the long work of shifting behaviour.

What makes this sequence interesting is what it implies about sequencing failures. Organisations routinely skip to function five or six — commissioning a journey mapping exercise or writing a strategic plan — without having done the audit or built the customer understanding that would make those artefacts credible. The result is a journey map that reflects internal assumptions rather than customer reality, and a strategic plan that cannot survive its first contact with the finance committee.

Why Journey Mapping Fails Without Operational Discipline

Journey mapping is the most widely practised and most widely misused tool in CX management. The problem is not the tool; it is the context in which it is used. A journey map produced in a two-day workshop, validated by internal stakeholders, and filed as a PDF is not a management instrument. It is a document.

Sheehan's insistence on "Journey Mapping Operations" — standard operating procedures for how maps are created, updated, owned, and acted upon — addresses this directly. Effective CX journeys require a living process: regular review cycles, clear owners for each stage of the journey, a mechanism for feeding new VoC data into the map, and a direct link between journey pain points and the strategic plan's prioritisation logic.

The behavioral economics dimension here is worth naming. Daniel Kahneman's peak-end rule tells us that customers do not remember every moment of an interaction — they remember the emotional peak (positive or negative) and the ending. A journey map that treats every touchpoint as equally important will systematically misdirect investment. The operational discipline Sheehan advocates creates the conditions for identifying which moments actually shape memory and loyalty — and prioritising those above the noise.

CX Governance: The Function Most Programmes Skip

Of the eight functions, governance is the one most organisations either skip entirely or implement so lightly that it collapses under the first organisational restructure. Sheehan outlines seven specific jobs that CX governance must perform — a level of specificity that is rare in the literature.

"Without governance, a CX programme is a series of projects. With governance, it becomes a function. The difference is whether the work survives the people who started it."

This is the right framing. CX governance is not a committee or a reporting line. It is the mechanism by which CX decisions get made, conflicts between functions get resolved, and accountability for the customer experience is distributed across the organisation rather than concentrated in a single team that lacks the authority to change anything.

The practical implication: governance must be designed before the strategic plan is written, not after. If you cannot answer the question "who decides?" for each major category of CX investment and change, your strategic plan is aspirational fiction.

The Business Case Problem — and How to Solve It

One of the most practically valuable sections of the book addresses how to build a persuasive business case for CX investment. This is where many CX leaders lose the argument — not because the case is weak, but because it is made in the wrong language.

CX leaders tend to present their cases in experience terms: satisfaction scores, effort scores, complaint volumes. Finance committees speak in revenue, cost, and risk. The translation between these two languages is not obvious, and most CX teams do not do it well.

Sheehan's methodology for building the business case integrates three data streams that most organisations hold separately: Voice of Customer data, Employee Experience data, and operational data. The logic is straightforward. A spike in customer complaints at a specific touchpoint, correlated with high agent attrition in the team handling that touchpoint, and mapped against the operational cost of re-work and escalation, produces a business case that a CFO can engage with. Any one of those data streams alone does not.

This is also where employee experience earns its place in the CX argument. The research is consistent: Gallup's 2022 State of the Global Workplace report found that business units in the top quartile for employee engagement show 10% higher customer ratings and 23% higher profitability than those in the bottom quartile. Employee experience is not a parallel programme to CX — it is an upstream driver of it. Sheehan integrates this, which most CX frameworks do not.

CX Maturity: The Roadmap That Keeps Programmes Honest

A maturity model is only useful if it is honest about where an organisation actually sits, rather than where its leaders would like it to sit. The gap between self-assessed and customer-assessed CX performance is one of the most durable findings in the field. Bain & Company's 2005 study Closing the Delivery Gap found that 80% of companies believed they delivered a superior customer experience, while only 8% of their customers agreed. That gap has not closed in the intervening two decades — it has, if anything, widened as customer expectations have risen faster than organisational capability.

Sheehan's maturity roadmap is structured around three dimensions: skills, capacity, and business value. This is more useful than the typical maturity model, which tends to focus on process sophistication alone. A CX programme can have sophisticated processes and still deliver no business value if it lacks the skills to interpret its data or the capacity to act on its findings.

The practical implication for CX leaders: a CX maturity assessment should be the first deliverable of any new programme or significant programme review. It establishes the baseline, identifies the critical gaps, and creates the shared understanding of starting position that makes the strategic plan credible.

Change Management: The Function That Determines Whether Any of This Works

The eighth function — CX change management — is listed last, but it is arguably the most important. Every other function in the framework produces artefacts: audits, maps, plans, governance structures. Change management is what determines whether those artefacts change behaviour.

The behavioral economics perspective is instructive here. Loss aversion — the well-documented tendency, identified by Kahneman and Tversky in their 1979 paper Prospect Theory: An Analysis of Decision Under Risk (published in Econometrica, Vol. 47, No. 2) — means that people resist changes that feel like losses even when the expected value is positive. For frontline staff, a new CX process often feels like additional scrutiny, additional work, or a challenge to their existing competence. Framing the change in terms of what they gain — clearer guidance, fewer escalations, better tools — rather than what the organisation gains is not manipulation; it is good change design.

Effective change management in a CX context also requires distinguishing between the types of change involved. Updating a process is a different challenge from shifting a cultural norm. The former can be managed with training and clear communication; the latter requires sustained leadership behaviour, reinforcement mechanisms, and patience measured in years rather than quarters.

What the Field Manual Gets Right — and Where to Push Further

Sheehan's framework is genuinely useful, and its practical orientation distinguishes it from most CX literature, which tends toward the inspirational rather than the operational. Several things stand out as particularly well-judged:

• The integration of EX and VoC as co-equal inputs to the business case, rather than treating customer data as the only relevant signal.
• The insistence on standard operating procedures for journey mapping — treating it as a recurring operational process rather than a project.
• The governance-first logic — designing accountability structures before writing strategy, not after.
• The maturity roadmap's three-dimensional structure — skills, capacity, and business value — which is more actionable than process-only models.
• The business case methodology — translating CX data into financial language that finance committees can engage with.

Where practitioners may want to push further: the framework was published in 2019, and the landscape has shifted. The rise of AI-driven personalisation, the proliferation of digital and physical channel combinations, and the growing sophistication of real-time VoC analytics create both new capabilities and new governance challenges that the original framework does not address. The eight functions remain sound; the tools and data available to execute them have changed considerably.

There is also a dimension the book treats lightly: the emotional architecture of the experience itself. Knowing which touchpoints to fix is necessary but not sufficient. Understanding why certain moments create disproportionate emotional impact — and designing intentionally for those moments — requires a behavioral lens that sits alongside the operational framework rather than replacing it. Behavioral economics applied to CX design is the natural complement to Sheehan's operational rigour.

How to Use This Framework in Practice

For a CX leader inheriting a programme that has stalled, or building one from scratch, the field manual structure suggests a clear sequence of diagnostic questions:

1. Is there a clear mandate? Does the CX function have defined authority, executive sponsorship, and a stated scope — or is it advisory by default?
2. Do we have a real baseline? Has a CX audit been conducted against actual customer experience data, not internal perception?
3. Is customer understanding continuous? Is there a Voice of Customer strategy that feeds live insight into decision-making, or is it periodic and retrospective?
4. Are journey maps operational? Do they have owners, update cycles, and a direct link to the strategic plan?
5. Is there a governance structure? Can you name who decides, who owns each journey stage, and how cross-functional conflicts are resolved?
6. Is the business case in financial language? Can you translate your CX metrics into revenue impact, cost reduction, and risk mitigation?
7. Is change management designed in? Is there a plan for the human side of every significant CX change — not just the process side?

If the answer to more than two of these questions is "no" or "not really," the programme has structural gaps that no amount of additional measurement or workshop activity will close. The work is to build the function, not to run more surveys.

The Deeper Argument Behind the Framework

The most important claim in Sheehan's book is implicit rather than stated: that customer experience management is a profession, with its own body of knowledge, its own operating procedures, and its own standards of practice. This is not yet universally accepted. In many organisations, CX is still treated as a marketing sub-function, a service improvement initiative, or a metric to be managed rather than an experience to be designed and operated.

The organisations that have moved beyond this — that treat customer experience management as a genuine operational discipline — tend to show it in their results. McKinsey's research on customer satisfaction consistently shows that consistency across the end-to-end journey matters more than excellence at individual touchpoints — a finding that only makes sense if you are managing the journey as a whole, not optimising touchpoints in isolation.

Not to inspire a CX transformation, but to execute one — reliably, repeatably, and with the rigour that any other operational discipline demands.

Final Assessment

Customer Experience Management Field Manual is not a book for the curious. It is a book for the committed — practitioners who have already accepted that CX is a management discipline and now need a structured way to build it properly. Its value lies precisely in what it refuses to do: it does not offer shortcuts, it does not promise quick wins, and it does not dress up aspiration as method.

Its limitations are real. Practitioners working in early-stage markets, in organisations where CX literacy is low, or in sectors with highly fragmented customer journeys will need to supplement the framework with context-specific thinking. The book assumes a degree of organisational readiness that many teams will not yet have.

But those limitations do not diminish its core contribution. The field has needed a practitioner-grade reference — something that sits closer to an engineering manual than a leadership manifesto. This comes closer to that standard than most.

Who Should Read It

• CX directors and managers responsible for building or restructuring a CX function
• Consultants who need a shared vocabulary and diagnostic framework to use with clients
• Senior leaders who want to understand what a properly governed CX programme actually requires of the organisation
• Service designers and journey owners who operate within a larger CX structure and want to understand how their work connects to the whole

Those looking for inspiration, for stories of transformation, or for a vision of what CX could become will find the book frustrating. That is not a flaw. The field has no shortage of vision. What it has historically lacked is the operational discipline to translate that vision into sustained performance — and that is precisely the gap this manual is written to close.