Improving customer experience decisions: Record decision outcome: change, investigate, monitor or decline.; Assign decision maker with evidence needs and review date.; Check customer results after changes to confirm improvement.
Image: Customer Experience Desk

CX Measurement

Part of Customer experience governance

Creating a decision process for experience improvements

Turn customer experience issues into documented decisions with clear authority, evidence, owners and outcome checks.

Record one outcome for each proposed customer experience improvement: change, investigate, monitor or decline. Name who can make that decision, what evidence they need and when the issue will return for review. An approved change also needs an owner and a check of its customer result.

Start with the problem

At intake, record the customer task, observed difficulty, people or cases represented and outcome sought. “Add a status page” proposes a solution.

“Customers cannot tell whether their address change has taken effect” identifies a problem to investigate. The address-change case is hypothetical.

Keep the limits of the evidence beside the request. A few complaints may warrant investigation without showing how common a problem is.

A delay recorded by a system may not show what the customer understood. Send a possible urgent consequence through the appropriate specialist route while the wider proposal is considered.

Identify the decision maker

Find who controls the likely change: content, operations, policy, technology or several of them. A journey owner can coordinate the proposal, but cost, risk or rule changes may need another authority. Record that authority before the proposal stalls.

Ask five questions at the decision point:

  1. What customer outcome is affected, and what supports that account?
  2. Which explanation remains uncertain or disputed?
  3. What action can the decision maker authorise, and what needs escalation?
  4. What could the action worsen for other customers or staff?
  5. What result and adverse effect will be checked afterwards?

These questions support judgement; they are not a numerical score. A serious failure may need a prompt response even if few people report it. A proposed fix may need investigation if its effects are uncertain.

Record one outcome

Decision / What to record

Change
Agreed action, authority, delivery owner and customer outcome check.
Investigate
Specific uncertainty, evidence to gather, owner and return date.
Monitor
Signal to watch, review trigger and owner.
Decline
Reason, evidence considered and condition for reopening.

Give people who raised the issue an appropriate explanation. An individual case needing a response continues through its service route regardless of the wider improvement decision.

Return to the result

After a change, examine the same customer task and any adverse effects identified before delivery. Distinguish implementation from improvement. If customers still cannot tell whether their address changed, the team may have addressed the wrong part of the service.

Keep the decision history: what was observed, what was assumed, who decided and when the issue will return. Reopen it when new evidence challenges its basis.

More from CX Measurement