Journey Mapping
Customer effort reduction
Customer effort is the work a person must do to get an ordinary need resolved.
Customer effort is the work a person must do to get an ordinary need resolved. It includes repeating details, switching channels, waiting for a transfer, finding an answer, and checking whether a promised action happened. Reducing it begins by observing the complete task, not by trimming a single team's processing time.
The customer's task as the unit of analysis
Customer effort is best understood at the level of the customer's task, not an internal queue. A frequent, bounded journey—such as changing an address or correcting an invoice—shows where effort accumulates: repeated information, hand-offs, waiting for a transfer and exception paths. A standard transaction may look easy while the failed one is exhausting.
Customer accounts, support records and observation each contribute a different view. A survey score alone cannot identify which step to remove, and it may miss customers who abandoned the task before they were asked.
Key Steps to Reduce Customer Effort
- Map the complete customer taskObserve end-to-end journey, not individual team processes
- Identify friction pointsRepeat information, hand-offs, waiting, exception paths
- Prioritise high-consequence frictionFocus on journeys that risk churn or confidence loss
- Assign end-to-end ownershipEnsure accountability across teams for seamless outcomes
Remove work rather than relocate it
Effort reduction is not the same as moving work between teams or pushing it to self-service. The decision question is whether the customer's total work falls, not whether an internal team's handling time improves or a routing problem becomes someone else's.
A form that requires the customer to diagnose an internal category may save routing work for staff while increasing effort outside the company. The same risk applies when no team owns the end-to-end request and the customer becomes the integrator.
The framework should weigh ease against quality and fairness: an interaction can be quick and still produce a wrong answer. A design that works for a frequent user may fail someone who needs accessibility support or has an unusual case.
Effort Reduction vs. Work Relocation in Customer Journeys
- Reducing customer effortDecreases total work for the customer across all touchpoints
- Relocating work internallyMay reduce staff time but increases customer workload (e.g., self-service forms requiring diagnosis)
Choose an effort signal
Customer Effort Score (CES) gives teams a direct measure of how easy people felt it was to get what they needed. One common approach asks the question immediately after an interaction and uses a seven-point scale: seven indicates no friction, while one indicates a gruelling experience.
Treat the score as a signal about perceived ease, not a diagnosis of the cause. The task map and supporting evidence are still needed to locate the step creating the difficulty.
Effort can also inform retention priorities. Customer effort predicts loyalty better than satisfaction: 96% of high-effort customers grow more disloyal, compared with 9% of low-effort customers; 94% of low-effort customers say they intend to buy again.
Prioritise friction with consequences
When several journeys need attention, look for friction that makes customers work repeatedly or risks losing their confidence. A telecom example is a bill a customer cannot decode, followed by an outage that takes three calls to escalate; an app that redirects someone to the phone line is another sign the journey is not connected.
In a telecom context, the cited guide links effort to churn and retention. For another sector, use its own task outcomes and customer evidence rather than assuming those industry claims apply unchanged.
Customer Journey Friction Points in Telecom Industry
- Step 1Unreadable bill — Customer cannot decode charges; leads to confusion and frustration
- Step 2Service outage — Requires three separate calls to escalate; repeated details shared
- Step 3App redirects to phone line — Breaks digital continuity; forces channel switch
Keep ownership visible
Ownership matters because effort reduction cuts across teams. The framework should make clear who is accountable for the end-to-end journey and how the organisation will know whether friction has fallen rather than merely moved.
In this guide
- Identifying steps customers must repeatRepeated work is easy for an organisation to miss because each team sees only its own interaction.
- Removing unnecessary transfers between service teamsA transfer is useful when a specialist is needed.
- Testing whether a redesigned process is easierA redesigned service process should be tested on the complete customer task.
- Measuring effort without reducing service qualityAn effort score asks how easy a customer found an interaction.
