CX Measurement
Part of Customer experience prioritisation
Separating a frequent annoyance from a serious rare failure
Separate the frequency of a customer problem from its consequence, choose a sound denominator and decide what each finding needs next.
Judge frequency and consequence separately. A frequent annoyance may create repeated work across many customer tasks. A rare failure may stop someone getting an important result. Neither the largest complaint count nor one striking account settles priority alone.
Define the event you are counting
Start with a specific task and failure. “The confirmation was hard to understand” and “the request was never processed” should not share a category just because both led to a call. Check the underlying outcome before grouping cases where that distinction matters.
Choose a denominator that matches the question. To estimate how often a problem occurs among people who attempt a task, count eligible attempts if suitable records exist. A complaint tally counts complaints received through that route, and may miss people who gave up or did not complain. State the period, channels and groups covered.
For a serious event found in one case, record its verified consequence and who could plausibly encounter the same condition. One report does not establish that the failure is rare; its frequency may be unknown.
Key Metrics for Problem Assessment
- Denominator
- Eligible task attempts (e.g., form submissions)
- Complaint Count
- Number of complaints received through a channel
- Verified Cases
- Confirmed incidents with documented outcomes
- Affected Users
- Estimated number of people who could encounter the issue
Describe what happens in each case
Assess whether the customer can recover, what recovery demands and whether the intended outcome remains incomplete or wrong. Consider people who cannot use the available alternative. Describe the consequence without assuming every customer is affected in the same way.
| Hypothetical finding | What it suggests | What remains to check |
|---|---|---|
| Many customers reread a routine instruction before finishing | Recurring friction that may merit a focused change | Whether it causes errors, delay or abandonment, and whom the records miss |
| One customer cannot obtain a required decision after an exception | A potentially serious failure needing attention to that case | Whether the condition can affect others, its cause and a safe response |
The table does not rank the findings. The first may have a large cumulative effect; the second may need immediate handling while its wider scope is investigated.
Choose the next action for each
For a frequent annoyance with a clear cause, propose a change and check whether the complete task becomes easier without worsening its result. If the cause is uncertain, examine relevant cases or observe the task before rewriting an instruction on guesswork.
For a serious reported failure, address the affected customer through the appropriate service or specialist route. Examine the conditions that produced it and whether others could be exposed. Do not wait for a high complaint count before considering a protective step. Avoid declaring a systemic defect before its cause and scope are established.
Bring both findings to the same comparison record: consequence when the event occurs, available frequency evidence, people potentially affected, uncertainty, next action and owner. This keeps recurring friction visible without allowing its volume to obscure a high-consequence exception.
