Customer Experience as a Business Strategy
Measure the Experience Before You Need to Defend It
Measurement should be designed alongside a product so teams can learn and improve from launch rather than argue from incomplete signals.
· Jason Wong · 2 min read
- Customer Experience
- Practical framework
Teams often defer measurement until a product is close to launch. By then, the questions have already narrowed: what can we instrument quickly, which dashboard is available, and what proxy will leadership accept? That is too late. Measurement is a design decision. It should be shaped when teams define the customer problem, the service flow, and the operating model—not after the interface is complete.
Build a scorecard that helps teams decide
Start with the customer outcome. What should become easier, clearer, faster, or more reliable? Then identify the behavioural signals that show whether the journey is working. Add the operational drivers teams can influence, and the guardrails that prevent a local improvement from moving effort elsewhere. A useful scorecard does not need to be large. It needs to be connected to decisions. If a measure changes, the team should know what it will investigate, who can act, and where the trade-off will be resolved. This is why dashboards alone are not enough. Reporting creates visibility; a review routine creates accountability. The strongest teams decide in advance how they will learn from the first weeks of use, not after a result needs defending.
Connect sentiment to operational drivers
A headline satisfaction measure can tell leaders that a problem exists without showing what to change. McKinsey’s analysis of a European utility found that four operational drivers explained 75 percent of satisfaction in the customer sign-up journey. Its research also described a transportation company where three journeys accounted for more than 65 percent of overall customer satisfaction. (McKinsey, 2017) The implication is practical: measurement should connect three levels.
- Journey outcome: Did the customer accomplish what mattered?
- Experience driver: Which parts of the journey shaped their perception?
- Operational driver: Which process, handoff, delay, or error can the team change? This structure converts measurement from a scoreboard into a diagnostic system. It also limits metric sprawl: if a metric cannot be connected to a journey outcome or a decision, it may be reporting noise. Measurement design is complete only when teams know what they will do with the signal.