A user outcome is a measured change in what people experience after a bet ships. It shows whether the product actually got easier, clearer or more useful for the people it was built for.
For example, before the redesign, only 42% of new cardholders could say what their points were worth. After the points progress bar shipped, 78% could. That jump is the user outcome. It's the first link in the chain that connects a user need to the business.
Why it matters
Teams often ship a change and move straight to business numbers. When spend goes up, nobody knows whether the design helped. When spend stays flat, nobody knows whether the design failed or something else got in the way.
User outcomes close that gap. They show that the experience changed for real people, measured by a design KPI such as task success, ease of use or comprehension. They're the earliest proof a bet is working, and they usually move weeks before product or business numbers do.
Name the user need a bet is meant to serve, pick the design KPI that shows it's met, record the number before and after, and check that the change happened for the audience you meant to help.
How we write one
Every user outcome is written as one sentence that names the design KPI, where it started, where it ended up, and who it changed for:
A design KPI moved from a starting value to a new value for an audience.
Task success moved from 42% to 78% for new cardholders.
Writing it this way forces a real before and after, and naming the audience makes it clear whose experience changed. A change for everyone in general usually means a change for no one in particular.
How it differs from similar ideas
-
A product outcome is a change in how the product performs, such as adoption or feature usage. A user outcome is a change in how the experience feels and works for people. User outcomes usually come first and help explain product outcomes.
-
A business outcome is a change in revenue, spend, churn or cost. A user outcome sits two steps earlier in the chain, closest to the user need.
-
A UX metric is a single measurement, such as task success of 42%. A user outcome is the change in a design KPI from before a bet to after it.
-
Findings report what happened in a round of testing on a concept. A user outcome is measured after a bet ships, with the real audience.
-
A user need is what people need, such as seeing what their points are worth. A user outcome is the evidence that the need is now better met.
A good user outcome
-
Uses a design KPI, such as task success, ease of use or comprehension
-
Has a real before and after value
-
Names the audience it changed for
-
Covers a stated period
-
Comes from one bet
-
Maps back to one user need
What happens to it
-
Expected. A bet names the user need it serves and the design KPI that should move.
-
Baselined. The starting value is recorded before the change ships, often from a benchmark or earlier findings.
-
Measured. After launch, the KPI is measured again with the same audience and method.
-
Mapped. The outcome is linked forward to the product outcome it helps explain, and back to the user need it serves.
-
Returned. The outcome goes back to Define and Collecting, where it shapes the next round of needs and assumptions.
For Ray
This part tells Ray how to find user outcomes in an input, such as a post-launch usability readout, a UX benchmark report, a research repository entry, a quarterly design review deck or a dashboard export, and how to store them.
How to find one
-
Mark before and after claims. Read the input and mark every statement that compares a design measure before and after a change.
-
Confirm it's a design KPI. Keep it only if the measure describes the experience, such as task success, SEQ, SUS, comprehension or time on task. Route adoption, usage and retention to Product Outcome, and money or churn to Business Outcome.
-
Find the two values. Pull out the starting value and the new value. If only one value is given, look for a linked benchmark; otherwise leave the missing value blank.
-
Find the audience and period. Identify who was measured and when, including sample size and method if given.
-
Find the bet. Identify the shipped change that produced it. If no bet is named, leave it blank and flag it.
-
Map it to a user need. Match it to one of the 20 user needs that the KPI shows is better met.
-
Write the sentence. Use the format: [Design KPI] moved from [x] to [y] for [audience].
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Before and after language: "went from", "improved from", "up from", "compared to baseline"
-
Design KPI names: task success, completion rate, SEQ, SUS, comprehension, time on task, error rate
-
Post-launch research: "in the follow-up study", "after the redesign shipped", "in the live product"
-
Readouts that tie a result to a shipped change: "since the progress bar launched..."
What doesn't count
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>If the statement...</p></th><th colspan="1" rowspan="1"><p>Store it as</p></th></tr><tr><td colspan="1" rowspan="1"><p>Reports a design measure from a concept test before anything shipped</p></td><td colspan="1" rowspan="1"><p>UX Metric in Findings</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports a change in adoption, usage or retention in the product</p></td><td colspan="1" rowspan="1"><p>Product Outcome</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports a change in revenue, spend, churn or cost</p></td><td colspan="1" rowspan="1"><p>Business Outcome</p></td></tr><tr><td colspan="1" rowspan="1"><p>Gives a single design measure with no before value</p></td><td colspan="1" rowspan="1"><p>UX Metric, or Benchmark if it's a baseline</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes what people need without a measured change</p></td><td colspan="1" rowspan="1"><p>User Need</p></td></tr></tbody></table>
The record
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What to fill in</p></th><th colspan="1" rowspan="1"><p>Values</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>The one-sentence outcome</p></td><td colspan="1" rowspan="1"><p>[Design KPI] moved from [x] to [y] for [audience].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Design KPI</p></td><td colspan="1" rowspan="1"><p>The experience measure that moved</p></td><td colspan="1" rowspan="1"><p>Link to UX Metric tagged Design KPI</p></td></tr><tr><td colspan="1" rowspan="1"><p>Before</p></td><td colspan="1" rowspan="1"><p>The starting value</p></td><td colspan="1" rowspan="1"><p>Number with unit, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>After</p></td><td colspan="1" rowspan="1"><p>The new value</p></td><td colspan="1" rowspan="1"><p>Number with unit</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Who was measured</p></td><td colspan="1" rowspan="1"><p>Link to Audience</p></td></tr><tr><td colspan="1" rowspan="1"><p>Period</p></td><td colspan="1" rowspan="1"><p>When before and after were measured</p></td><td colspan="1" rowspan="1"><p>Dates or periods</p></td></tr><tr><td colspan="1" rowspan="1"><p>Method</p></td><td colspan="1" rowspan="1"><p>How it was measured, with sample size</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>Bet</p></td><td colspan="1" rowspan="1"><p>The shipped change that produced it</p></td><td colspan="1" rowspan="1"><p>Link to Bet, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>User need</p></td><td colspan="1" rowspan="1"><p>The need it shows is better met</p></td><td colspan="1" rowspan="1"><p>One of the 20 user needs</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>The input and exact passage, slide or chart</p></td><td colspan="1" rowspan="1"><p>Link to Input</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How solid the before and after are</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
Before and After must use the same KPI, audience and method. If they don't, store both values but lower confidence and say why.
Scoring confidence
Confidence measures how well the change is evidenced, not how big it is.
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Level</p></th><th colspan="1" rowspan="1"><p>When to use it</p></th></tr><tr><td colspan="1" rowspan="1"><p>High</p></td><td colspan="1" rowspan="1"><p>Both values measured the same way with the intended audience, with a named bet and period</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Both values given, but the method, sample size, period or bet is unclear</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>One value is estimated, the audience differs between before and after, or the claim is secondhand</p></td></tr></tbody></table>
If any part of the record can't be filled from the source, leave it blank and lower confidence by one level.
Linking
-
Check for duplicates first. If an existing outcome covers the same KPI, audience and period, add the new source to it instead of creating another.
-
Link to the bet that produced it and the user need it maps from.
-
Link forward to the product outcome it helps explain, such as rewards tab visits rising alongside task success.
-
Link to the benchmark or findings that supplied the before value, and to the UX metric that holds the KPI.
-
Note contradictions. If the outcome moved the opposite way from what the bet expected, link it as contradicting the bet.
When to store and when to ask
-
Store automatically when confidence is high.
-
Add to the review digest when confidence is medium or low, when it contradicts its bet, or when no bet or user need can be found.
When to flag
-
A shipped bet has no user outcome measured after 60 days
-
A user outcome has no bet linked to it
-
A user outcome improved, but its linked product outcome didn't move
-
Before and after were measured with different audiences or methods
-
A user outcome moved the wrong way
Worked example
Input: a post-launch usability readout from the research team, March 2027.
"We reran the point-value task with 40 new cardholders four weeks after the progress bar went live. 78% could say what 5,000 points buys, up from 42% in the January baseline. Same task, same unmoderated setup."
What Ray finds:
-
"Could say what 5,000 points buys" is task success, a design KPI.
-
"Up from 42%" is the before value and "78%" is the after value.
-
"40 new cardholders" is the audience, and "four weeks after the progress bar went live" ties it to the bet.
-
"Same task, same unmoderated setup" confirms the two values are comparable, which supports high confidence.
Stored record:
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>Task success moved from 42% to 78% for new cardholders.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Design KPI</p></td><td colspan="1" rowspan="1"><p>Task success on the point-value task (Behavioral, Leading, Design KPI)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Before</p></td><td colspan="1" rowspan="1"><p>42%</p></td></tr><tr><td colspan="1" rowspan="1"><p>After</p></td><td colspan="1" rowspan="1"><p>78%</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Customers: new cardholders in their first 90 days</p></td></tr><tr><td colspan="1" rowspan="1"><p>Period</p></td><td colspan="1" rowspan="1"><p>January 2027 baseline; March 2027 follow-up</p></td></tr><tr><td colspan="1" rowspan="1"><p>Method</p></td><td colspan="1" rowspan="1"><p>Unmoderated task test, 40 participants</p></td></tr><tr><td colspan="1" rowspan="1"><p>Bet</p></td><td colspan="1" rowspan="1"><p>We bet the progress bar will drive adoption</p></td></tr><tr><td colspan="1" rowspan="1"><p>User need</p></td><td colspan="1" rowspan="1"><p>Valuable (Impact)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Post-launch usability readout, March 2027</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: same task and method before and after, with the intended audience and a named bet</p></td></tr></tbody></table>
Next step: stored automatically and linked forward to the rewards tab visits product outcome.
Edge cases
-
Test results reported as outcomes. "Task success hit 78% in the concept test" is a UX metric in Findings. It becomes a user outcome only once the change ships and is measured again.
-
Several KPIs in one readout. If task success and SEQ both moved, store one user outcome per KPI and link them to the same bet.
-
No baseline. Store the after value with Before blank, lower confidence, and look for a benchmark that can supply the starting point.
-
Mixed causes. If two bets shipped at once, link the outcome to both and flag it so the team can say which one gets credit.