User Metrics & Outcome-Driven UX
Building a culture where design decisions are defined, measured, and communicated through user outcomes
​
In 2024, my leadership peers and I led an initiative to upskill every designer in our organization on user-centered measurement. We aligned on Google’s HEART framework as a foundation and extended it with NN/g’s CASTLE framework to reflect the realities of enterprise tools and internal users.
​
This shifted UX from feature delivery → to measurable product impact.
The Problem
Product and engineering had clear success metrics. UX did not.
​
So design value was:
-
difficult to quantify
-
inconsistently communicated
-
often reduced to output
We created clarity by separating focus areas:
​
Product → business outcomes
Engineering → system performance
UX → user outcomes
​
This gave each discipline ownership while aligning everyone to shared product OKRs.
The Model
We standardized how success was defined across the portfolio:
-
Goals → Signals → Metrics
-
2–4 HEART/CASTLE dimensions per product
-
Product OKR alignment
-
Baselines established before feature work began
We partnered with our Lead UX Researcher to create a shared metrics playbook and trained every designer to read behavioral data in Pharos, FullStory, Grafana, and Google Analytics.
​
This moved measurement from a reporting exercise to a design planning tool.
From Product-Level → Feature-Level Success
Once product success was clear, every feature required:
-
a defined user success measure
-
a baseline
-
a post-launch read
Designers could now answer:
Did this improve the user’s experience?
How do we know?
What should we do next?
​
UX became a strategic partner in prioritization, not a downstream function.
Team Enablement
-
trained every designer on HEART and CASTLE and how to apply them to their product space
-
had designers socialize user metrics within their triads to create product-level alignment
-
held monthly UX metrics reviews for peer learning and storytelling practice
-
held quarterly readouts with Product Directors to connect UX outcomes to roadmap decisions
-
supported the entire team in earning Designlab’s Data-Driven Design certification (2024) to establish a shared foundation in outcome-based measurement
Designers learned to:
-
tell outcome-driven stories
-
connect UX work to OKRs
-
influence prioritization using evidence
-
use behavioral data to guide design decisions
Organizational Impact
After this shift:
-
UX success criteria were defined before work began
-
Product leaders expected user metrics in reviews
-
Designers used evidence to influence prioritization
-
Outcome storytelling became a core UX skill across the team
