Customer Effort Score (CES)

Customer Effort Score measures how much work a customer had to do to accomplish something, typically by asking them to agree or disagree with a statement such as "the company made it easy for me to handle my issue." It emerged from research published in Harvard Business Review by Dixon, Freeman, and Toman, which argued that reducing effort predicts loyalty better than attempting to delight customers, and that most customers simply want their problem solved without difficulty.

The underlying finding is the interesting part. The research reported that high-effort interactions were strongly associated with disloyalty, while exceeding expectations produced far less loyalty benefit than commonly assumed. The practical implication is that investment in removing obstacles, repeated contacts, channel switching, and having to explain a situation more than once, typically returns more than investment in delight initiatives, which are expensive and often go unnoticed.

CES is most useful for transactional and service interactions where the customer's goal is resolution rather than enjoyment: support contacts, returns, account changes, cancellations, claims, and self-service tasks. In these contexts effort is the dominant driver of how the interaction is remembered, and the score attaches to a specific process that can be redesigned. It is much less useful for discretionary or experiential contexts, where effort is not the relevant dimension and low effort is not the goal.

Its practical strength is that a poor score points toward a remedy more directly than satisfaction or loyalty measures do. High effort has identifiable causes: information that was hard to find, a process requiring several steps or channels, a policy requiring justification, a system that lost context between interactions, a form that had to be completed twice. Each is addressable, and the follow-up question asking what made the interaction difficult usually names the cause without further analysis.

The usual measurement cautions apply. Question wording and scale direction have changed across versions of the metric, so historical comparisons within an organization require consistency and cross-organization benchmarks are unreliable. Timing matters, since effort is best assessed immediately after resolution rather than days later. And the metric measures perceived effort, which is influenced by expectation: the same process feels effortful in a context where customers expect instant self-service and reasonable in one where they expect a formal procedure.

The measure also has a useful application in identifying where self-service is failing, which is where most avoidable effort originates. Customers who contact support have, in most cases, already attempted to resolve their issue themselves, and the contact represents a failure of the product to answer a question it could have answered. Categorizing contacts by the question being asked, and locating where in the product that question arises, produces a direct list of content and design gaps. Organizations that route this analysis back into the product rather than treating it as a service capacity problem typically reduce contact volume more effectively than any investment in deflection tools or chatbot automation.

Because effort accumulates across an entire journey rather than within a single interaction, the most valuable application is usually at journey level rather than touchpoint level. Mapping where effort concentrates, using CES alongside behavioral data such as repeat contacts, channel switching, and time to resolution, is standard practice in user research and in service design work. The resulting fixes typically sit in product design, since most avoidable effort is created by the product failing to support self-service rather than by the service team handling contacts badly.