Customer Effort Score (CES), in depth
CES grew from service research finding that customers rarely leave over absent wow-moments but reliably leave over friction — repeated contacts, confusing flows, manual workarounds. Measuring effort right after key tasks (setup, first value, getting help) locates exactly where the product makes users work.
Like all micro-surveys it trades depth for timing; a bad CES score names the task but not the obstacle. The diagnosis needs the user’s own words, which is why effort surveys pair naturally with an open feedback channel on the same screens.
Putting it into practice
Ask CES after effortful milestones, then chase poor scores through qualitative feedback about those flows. Bug reports and “feedback” category submissions with page context — the TellTide inbox’s bread and butter — are usually where the actual obstacle is named.