Experience Scoring: The –2 to +2 System That Makes Priorities Visible

One of the most practical contributions journey management makes to organizational decision-making is a simple mechanism for measuring the current state of the customer experience in a way that creates shared accountability and enables progress tracking. The experience scoring system is that mechanism.

It is not a scientifically precise instrument. It is a structured conversation that produces a "fair enough" shared assessment — which is exactly what organizations need to make priority decisions.

How the Scale Works

Each major stage of the journey receives a score based on a five-point scale:

| Score | Meaning | |-------|---------| | –2 | Broken: actively driving churn, generating significant complaints or support contacts | | –1 | Weak: creating friction, below reasonable expectations | | 0 | Neutral: functional but undifferentiated, neither creating nor destroying value | | +1 | Good: meeting expectations reliably, generating positive feedback | | +2 | Excellent: creating genuine delight or competitive advantage |

The score for each stage is determined collaboratively in the alignment workshop. Participants review the evidence — pains and needs from research, customer quotes, support volume data, qualitative observations — and propose a score. When scores diverge, the group discusses until it reaches a shared reading.

The process is more important than the number. A score that is "technically correct" but not agreed upon is worse than a score that is approximate but shared, because teams cannot act from a picture they do not believe in.

"Accuracy matters more than precision, and alignment matters most of all."

Why Scores Create Strategic Clarity

Before experience scoring, priority debates in cross-functional teams tend to be based on advocacy — whoever makes the most compelling case for their area gets the most attention. After scoring, priority debates are anchored to a shared picture of where the experience is most broken.

When the Activation stage is scored –1.4 and the Retention stage is scored +1.6, the organization can see at a glance where improvement is most urgently needed. This visibility does not make the priority decision automatic — there are resource constraints, organizational capabilities, and strategic choices involved — but it makes the conversation significantly more structured and productive.

Experience scores also create the north star for OKRs. Rather than setting key results based on business outputs alone (conversion rates, churn rates, revenue per user), teams can set OKRs that explicitly target experience score improvement: "Lift the Activation experience score from –1.4 to –0.5 within two quarters." This creates direct accountability for improving what customers actually experience, not just the business metrics that trail it.

Common Mistakes in Applying the System

Precision debates. Stakeholders sometimes invest significant meeting time arguing about whether a stage should be –1.2 or –1.4. This is a sign that the group is treating the score as a measurement rather than a shared assessment. The facilitator should redirect: "Is everyone comfortable that this stage is below zero and needs significant improvement? Yes? Then let's move on."

Defaulting to the average. When a group has widely divergent views of a stage's quality, averaging the scores obscures a useful signal: the team does not have a shared understanding of how this stage is performing. That disagreement should be surfaced and explored, not arithmetically eliminated.

Ignoring evidence. Scores should be grounded in the research material on the map — customer voices, pains, gains, and organizational pressures. When participants score based solely on intuition, the scores tend to reflect organizational politics rather than customer experience reality. The facilitator's job is to redirect to the evidence consistently.