What customer experience covers
Customer experience is the customer's own account of dealing with a business: what they expected, what they got, how it felt, and whether they would do it again. It includes the advertising that set the expectation, the website or shop, the purchase, the delivery or activation, the product in use, the help they needed, the bill, and the moment they decided to stay or go. Nielsen Norman Group's definition of user experience makes the same point about scope: it covers all aspects of the person's interaction with the company, its services and its products, not only the interface.
Two consequences follow. The experience is judged as a whole, so a brilliant product with a hostile returns process is a poor experience. And the experience is owned by nobody unless somebody is made to own it, because each stage sits with a different team. The foundations in this section are the minimum a marketing team needs to take that ownership: a map of the journey, a view of where new customers stall, a strategy for keeping them, and a clear-eyed decision about rewards. The customer experience hub places these foundations alongside service and measurement; the journey stages guide in the digital marketing root defines the stages themselves.
Journey, onboarding, retention, loyalty
The four foundations answer different questions and are measured differently. Treating them as one thing is the most common reason experience work stalls.
| Foundation | The question it answers | What good looks like | Measured by |
|---|---|---|---|
| Journey | What does the customer go through, in what order, and where does it hurt? | A map the whole business recognises, with the painful steps named | Drop-off and effort at each stage |
| Onboarding | How fast does a new customer reach the value they paid for? | Most new customers reach first value before interest fades | Time to first value; early churn |
| Retention | Why do customers stay, and why do they leave? | A diagnosis, levers chosen, and a plan that is reviewed | Retention and churn by cohort; a retention KPIA metric tied directly to an objective. |
| Loyalty | Should staying be rewarded, and how? | A programme that changes behaviour the business wants, or a decision not to run one | Programme economics; frequency and advocacy among members |
The order matters. Journey mapping comes first because every other foundation depends on knowing where customers are; onboarding second because early loss is the cheapest to fix; retention third because it is the strategy; loyalty last because a programme rewards an experience that already works.
The core guides
The core guides cover keeping customers and deciding whether to reward them.
- Customer retention strategy diagnoses why customers leave, sets out the four levers of onboarding, habit, value and service, covers lifecycle messaging and timing, and explains win-back and when to stop trying. It is the guide to read first.
- Designing a loyalty programme compares points, tiers, paid membership and community models, explains what to reward and what not to, works through the economics of liability and breakageThe share of issued loyalty rewards that customers never redeem, because points expire, balances are too small to use or members forget., and lists the signs that a programme is the wrong answer.
The method for drawing the journey, which the core guides assume, lives in the journey mapping guide rather than here; this section uses the map and does not repeat how to make it. The customer journey mapping framework page summarises the structure for quick reference.
Further guides
Further guides turn onboarding and the promise check into step-by-step work, show the machinery behind the journey, take on the effort customers spend and the way they leave, and recover the customers whose payments fail without anyone deciding to leave:
- Onboarding new customers beyond software — a tutorial for the first weeks of a service or physical product: defining first value, removing steps, explaining at the moment and catching stalls.
- Checking marketing promises against the experience — a tutorial for listing the promises marketing makes, finding the step where customers test each one, judging whether it holds and then fixing the step or softening the claim.
- Drawing a service blueprint — a tutorial for drawing the customer's steps, what staff do in view and behind the scenes, the systems and handoffs behind them, and where it fails.
- Designing the cancellation and leaving experience — letting customers cancel and leave well: a route as easy as joining, fair save offers, confirmation, final bills and data, one exit question and an open door.
- Reducing customer effort across the journey — finding and removing the effort customers spend on a business: repeating themselves, switching channels, long forms, proving who they are and chasing updates.
- Recovering failed payments without losing the customer — a tutorial for separating failed payments from cancellations, the recovery window, service messages, support and the end state.
Onboarding and first value
Onboarding is the period between the purchase and the moment the customer gets what they bought. For a software subscription that moment might be the first report run; for a meal kit, the first meal cooked; for a bank account, the first salary paid in; for a retailer, the first order that arrived as promised. Until that moment the customer is still deciding whether the purchase was a mistake, and most avoidable churn happens here, before any habit has formed and before the customer has told anyone they are a customer.
The work of onboarding is to shorten the distance to first value and to remove the reasons to stop. In practice that means three questions. What does the customer have to do before they get value, and can any of it be removed or done for them? What are they likely to misunderstand, and can it be explained at the moment it matters rather than in a welcome email? And what happens when they stall: does anyone notice, and does anything reach out? The last question is where marketing and product meet, because the reach-out is usually a lifecycle message triggered by a behaviour the product recorded. The tutorial on onboarding new customers beyond software takes these questions through for a service or physical product, from defining first value to catching stalls.
A fitness app moves its first value forward
Stridewell, a running app with a seven-day free trial, converts about 22% of trial users to paid. The team maps the first week and finds that users who complete a run with the app in the first three days convert at roughly 48%, while those who do not convert at under 10%. Most of the second group never got past connecting a watch, a step the app presented before the first run. The team makes the watch optional, lets the first run start from the phone alone, and adds one push notification on day two to users who have not yet run. Trial conversion rises to about 31% over the following quarter, and the watch connection, now offered after the first run, is completed by more users than before.
Expectations, promises and the brand
Experience is judged against expectation, and marketing sets the expectation. Advertising that promises effortless setup makes a merely adequate setup feel like a failure; a brand built on care makes a curt support reply feel like a betrayal. The experience does not have to be perfect, but it has to match the promise, and the cheapest fix for a mismatch is sometimes to change the promise. The FunnelModel of the customer journey stages. view hides this because it measures whether the promise converted, not whether it was kept.
The practical discipline is to read the promise and the journey side by side. Take the main claims from the advertising, the website and the sales conversation, and for each one find the step in the journey where the customer will test it. Where the test fails, either fix the step or soften the claim. The promise check tutorial runs this review step by step, from collecting the promises in every channel to giving each fix an owner and a date. This review belongs in the marketing calendar rather than in a one-off project, because campaigns change promises faster than operations changes delivery. The flywheel framing is the reminder of what is at stake: a kept promise produces a customer who stays and refers, which lowers the cost of the next customer and raises their LTVTotal value a customer brings over time.; a broken one produces the opposite, with the same energy spent.
Common foundation problems
| Problem | Usual cause | Guide |
|---|---|---|
| Nobody can describe the journey end to end | No map; each team sees its own stage | Journey mapping |
| New customers churn before they have used the product | First value is too far from purchase; stalls go unnoticed | Customer retention strategy, Onboarding beyond software |
| Retention work is a series of discount campaigns | No diagnosis of why customers leave; no levers chosen | Customer retention strategy |
| A points scheme is launched to fix churn | Programme chosen before the experience was fixed | Designing a loyalty programme |
| Customers feel misled after purchase | Promise and delivery never reviewed together | This hub, and the journey stages guide, Checking marketing promises |
| Rewards go to customers who would have stayed anyway | Rewarding the wrong behaviour | Designing a loyalty programme |
| Cancellations end in complaints and chargebacks | Leaving made harder than joining; offers put in front of the cancel route | Designing the cancellation experience |
| Customers counted as churned never decided to leave | Expired or declined cards never followed up; retries running without a word to the customer | Recovering failed payments |
| Customers have to repeat themselves after a transfer | Information lost at handoffs between teams and systems | Reducing customer effort, Drawing a service blueprint |
Start with the retention strategy guide if the business has never written one; start with the loyalty guide only if the experience already works and the question is whether rewarding it will change behaviour.
