OKRs for Journey Work: Using Experience Scores as the North Star

OKRs fail most often not because teams aim too low, but because teams are aiming at different things. Each team optimizes for their local metric — conversion rate, support ticket volume, feature adoption — without a shared signal that connects their separate efforts to a common outcome.

In journey management, the experience score fills this role. When multiple teams working on different Big Solutions all have OKRs that target improvements in the same experience score, they share a north star that transcends the local metrics of each individual effort.

Why Experience Scores Work as OKR Targets

They are journey-anchored, not function-anchored. A team focused on conversion rate improvement might increase conversion by creating higher-pressure purchase flows — short-term metric gain, long-term experience damage. A team focused on support ticket reduction might discourage customers from seeking help rather than actually solving the problems that drive support contacts. Both local optimizations can worsen the customer experience while improving the KPI they target.

Experience score targets prevent this drift. When the objective is to "lift the Activation experience score from –1.4 to –0.5," the measure of success is whether customers actually experience activation as better — not whether any specific internal metric moved.

They connect teams that would otherwise work in isolation. If the Awareness experience score is currently –1.2, every team working on any aspect of the awareness experience shares that improvement target. The content team working on discovery content, the UX team improving the first-visit interface, and the marketing team adjusting the acquisition messaging can each see how their work contributes to the same goal — and they can identify where their efforts complement rather than duplicate each other.

"When customer experience is managed as a journey — rather than as disconnected projects — journey orchestration, delivery teams, and leadership all align around the same goal: lifting experience where it matters most."

Setting OKRs That Connect to the Journey

The structure for journey-anchored OKRs is straightforward.

Objective (qualitative intent): What customer experience change are we trying to create? "Help customers make confident decisions earlier in the journey" is an objective. It describes the experience we want customers to have, not the feature we want to build.

Key Results (quantified outcomes): What measurable changes will indicate that the objective is being achieved? "Increase Awareness experience score from –1.2 to –0.5" is a key result. "Reduce comparison-related drop-offs by twenty percent" is a supporting key result. Both can be measured. Both connect directly to whether the customer experience is actually improving.

Supporting KPIs: Secondary metrics that add diagnostic depth — first-session product understanding (measured by micro-survey), help article engagement rates, referral code usage — without replacing the experience score as the primary accountability measure.

The Orchestrator's Role in OKR Setting

The journey orchestrator brings shared KPIs to the OKR process. This is a specific and important contribution: ensuring that each Big Solution's OKRs target the experience scores they are designed to lift, rather than only the local metrics that their immediate teams find most natural to optimize.

Teams may arrive at the OKR setting process with their own metric preferences. A UX team might want to track task completion rates. A marketing team might want to track engagement rates. These supporting KPIs are valid and useful. But they should be in addition to the experience score targets, not instead of them.

The orchestrator's value in this moment is perspective: the ability to see how each team's OKRs relate to the others, where they create shared accountability, and where they might inadvertently pull in different directions. When OKRs are set with this perspective in the room, the resulting goal structure is significantly more likely to produce the coordinated improvement the journey map was designed to enable.