from metrics
to mechanism
A shared measurement framework built from customer needs that unified disparate teams and drove measurable revenue within six months.
This case study has been condensed with all confidential information removed. If you would like to learn more about this design and process, please contact me.
overview
The organization tracked business metrics — revenue, individuals trained, digital subscribers, CSAT — that were valuable for understanding high-level trends but not directly actionable. Over six months, CSAT declined 12.95%. Senior managers couldn't identify what was driving it. That gap produced opinion-driven prioritization debates, release cycles averaging 6-8 sprints, and misaligned product investments.
The organization needed a shared measurement system grounded in customer outcomes with the diagnostic precision to act on it. I led the development of the CXO (Customer Experience Outcomes) Framework, built and adopted across the organization in 12 months.
problem
Each team measured differently, and none of it pointed to what actually needed fixing. Three gaps made the status quo unsustainable.
Unique visions of success
Each product team tracked its own metrics in its own way. Revenue, individuals trained, NPS, CSAT — all useful directionally, but none of them could answer the question that mattered: are customers accomplishing what they came here to do? When NPS dropped and open-text feedback said "hard to find what I need," there was no way to pinpoint whether the issue was navigation, search, or content gaps. The metrics could show that something was off. They couldn't show what.
Non-actionable metrics
Even when teams had data, it didn't map to anything they could fix. Revenue showed financial movement but not why people subscribed or left. Completion counts reflected activity without measuring value delivered. Satisfaction scores captured sentiment without pointing to a specific product flow or feature. The gap between "we see a problem" and "here's what to fix" was where conversations stalled.
I didn't build the solution in a single pass. The framework moved through three phases — discovery, validation, and measurement — each one building the credibility needed to earn adoption at the next stage.
No comparison across products
With every team using different definitions and instruments, there was no way to look across the portfolio and make informed tradeoffs. Leadership couldn't answer basic allocation questions: which products have the largest experience gaps? Where would investment have the most impact? Prioritization was harder than it needed to be because there was no shared frame of reference.
solution
Validated customer outcomes
I conducted 24 leadership interviews, synthesized 86 existing reports, and ran 160 interviews across four learner segments — surfacing 63 candidate outcomes representing customer goals. A validation survey with 2,000+ responses, stratified by learner segment, narrowed those to 51 outcomes organized into four behavior categories. Each outcome was composed of a job statement, success criteria, and metrics tied to specific product tasks.
Diagnostic measurements
The framework's core innovation was precision. Instead of a single satisfaction number, each outcome measured task completion rates, time on task, and product analytics alongside difficulty ratings, confidence scores, ease of use, and usefulness — all connected to specific customer tasks rather than general sentiment. Behavioral and attitudinal data worked together to give teams a clear line from "this score dropped" to "this is the task causing it."
Together the three phases produced something the organization had never had: a common language for customer needs that was prioritized, measurable, and directly connected to product decisions.
Embedded workflows
CXOs were integrated into product proposal templates, monthly business reviews, roadmap planning, and executive reporting. I built a searchable database of 1,000+ customer insights tagged by outcome, segment, and product so teams could find evidence without submitting a research request. A two-month pilot with 12 teams produced 19 feature improvements — 158% over the target of one per team.
results
Six years of operation. Measured at every stage.
51
validated outcomes
86%
org-wide adoption
34.6%
CSAT
increase
The cumulative result was behavioral.
Prioritization conversations that once relied on intuition now started from shared data. Product managers could justify investment with evidence tied to specific customer outcomes rather than aggregate trends. Leadership could look across all products and make allocation decisions based on measured outcome gaps, not competing opinions.
50%
faster release cycles
~$400K+
revenue within 6 months
what i learned
Senior leaders were engaged throughout, but only a few participated as builders rather than reviewers. In practice, those who helped shape the taxonomy used it differently than those who inherited it. The difference wasn't familiarity, it was ownership.
what this unlocked
With a shared measurement system in place, the organization had something it had never had before: a diagnostic vocabulary. Teams could identify which customer outcomes were underperforming, trace those gaps to specific product flows, and measure whether their interventions actually worked.
The quarterly cadence meant measurement wasn't a one-time event but a continuous feedback loop — each cycle refining both the products and the organization's confidence in its own decision-making. That foundation is what made the next chapter possible.