
Introduction
Customer Effort Score (CES) is a customer experience metric that measures how easy or difficult it was for a customer to get something done, such as resolving an issue, completing a purchase, or setting up a feature, typically with a single question like "How easy was it to handle your request today?" on a short scale. It exists because of a finding that reshaped service thinking: reducing effort predicts loyalty better than delighting people. This article covers where CES came from, how it's asked and calculated, what it captures that satisfaction misses, and how to act on a poor score.
What is Customer Effort Score?
Customer Effort Score is a transactional experience metric that asks customers, right after an interaction, how much effort it took to accomplish their goal. The original formulation asked "How much effort did you personally have to put forth to handle your request?" on a 1-to-5 scale; the more common current version reverses the framing into ease ("The company made it easy for me to handle my issue", agree to disagree, on a 1-to-7 scale) so that higher scores mean better outcomes. Like CSAT it is asked about a specific moment; unlike CSAT it measures friction rather than feeling, and the difference turns out to matter.
Where It Came From
CES was introduced by researchers at the Corporate Executive Board (Matthew Dixon, Karen Freeman, and Nicholas Toman) in a 2010 Harvard Business Review article whose title stated the thesis: stop trying to delight your customers. Their large study of service interactions found that exceeding expectations did little for loyalty, while reducing the effort customers had to expend (repeat contacts, channel switching, repeating information, being transferred) had a strong effect on retention and on word of mouth. The metric packaged that finding: measure effort at the moment it's felt, then attack its causes. Its later popularity in product teams follows the same logic applied to onboarding, self-service, and support, where the enemy is friction rather than absent delight.
Asking and Calculating It
1. Ask immediately after the task or interaction.
Effort is remembered vividly for hours and vaguely for weeks; the prompt belongs at the end of the chat, the checkout, or the setup flow.
2. Use the ease framing on a labeled, balanced scale.
"The product made it easy to..." with fully labeled points; the agreement-scale fundamentals apply, including the awareness that agreement framing invites some acquiescence.
3. Report consistently.
Mean score, or share of top responses, fixed for the life of the series, with the n and a breakdown by touchpoint, since a blended effort score across support and product tells nobody what to fix.
4. Attach the why.
"What made it difficult?" as an open question is where the fixable content lives. For product flows, a recorded task study reproduces the effort directly: watching screened participants attempt the same setup on video (a Ballpark task with a follow-up answer) shows the specific friction a score can only hint at.
What It Captures That Satisfaction Misses
A customer can be satisfied with a support agent who was charming and still have spent forty minutes and three contacts on a problem the product caused; CSAT rewards the charm, CES records the forty minutes. Effort is also more actionable: satisfaction has many causes, but effort points at concrete obstacles (steps, waits, repeats, handoffs, unclear paths) that a team can remove. And effort predicts behavior: high-effort experiences drive churn and negative word of mouth more reliably than low satisfaction drives them, which is why CES belongs in the experience metric set alongside NPS (relationship loyalty) and CSAT (moment satisfaction), each answering a different question.
The Limitations
CES is a self-report about one moment, subject to timing, framing, and who chooses to answer (the frustrated and the pleased respond; the indifferent don't). It says nothing about whether the goal was worth pursuing, and it can be gamed by asking only after successful resolutions. As a KPI it needs the usual guardrails: repeat-contact rate and resolution rate alongside it, and the qualitative why to keep it honest.
The Bottom Line
Customer Effort Score measures friction at the moment it's felt, on the evidence that friction drives disloyalty more than delight drives loyalty. Ask it right after the interaction, in the ease framing, on a fixed scale with the n and the reason attached, and treat a poor score as a map of obstacles rather than a mood. The question it asks of every experience is the one customers ask themselves: how hard did you make this?
Further reading
For the origin and the metric:
Articles:
1. Stop Trying to Delight Your Customers - Harvard Business Review
The article that introduced CES and the research behind the effort-loyalty link.
2. What Is CSAT? - Qualtrics
The sibling transactional metric, for understanding how satisfaction and effort measure different things.