What is Customer Effort Score (CES)?
Customer Effort Score (CES), introduced by Dixon, Toman, and DeLisi in 2010, asks: "How much effort did you have to expend to handle your request?" on a 1-5 or 1-7 scale (lower is better). The HBR research that introduced CES — based on 75,000+ customers — found that reducing effort predicted loyalty better than exceeding expectations. The implication: customer service should focus on making problems easier to resolve, not on creating "wow" moments that cost more than they earn. CES is particularly relevant in support, onboarding, and complaint-resolution contexts. Best practice: ask CES after task-oriented interactions; combine with first-call-resolution metric.
How Customer Effort Score (CES) actually works
The framework breaks down into the following moving parts. Knowing what each piece is — and what it is not — is what separates a B-grade answer from an A-grade answer in a written assignment.
- Ask "How much effort?" on 1-5 or 1-7 scale
- Lower scores are better
- Particularly relevant in service contexts
- Pair with first-call-resolution metric
- Optimize for low effort, not for "delight"
A worked example: Amazon's one-click checkout
Amazon's one-click checkout — patented in 1999 — is the textbook customer-effort reduction. Reducing the checkout flow from 15+ steps to 1 click dramatically reduced abandonment and increased conversion. The patent (now expired) was extraordinarily valuable; Apple licensed it for a reported nine figures. The principle generalizes: every step removed from a task increases the percentage of customers who complete it. Many CRO interventions are essentially CES reductions — fewer form fields, fewer clicks, fewer steps to the value. The HBR-CES research formalized what UX designers had long understood: friction kills.
Don't lose marks for these
- Optimizing for delight when effort reduction would matter more
- Confusing CES with CSAT (different questions)
- Ignoring CES in self-service contexts
How to use this on the exam
Score-maximizing moves
- Cite HBR research
- Distinguish from NPS and CSAT
- Apply to service-recovery contexts
When to use Customer Effort Score (CES) (and when not to)
Use Customer Effort Score (CES) when your assignment asks you to analyze, structure, or recommend — and when you have at least two data points to populate every cell of the framework. Skip it when the question is asking for a numerical answer or a single recommendation, since Customer Effort Score (CES) is a structuring tool, not a calculator.