A business outcome is a measured change in how the business performs after a bet ships. It's the change leaders already track: revenue, spend, churn or cost.
For example, before the redesign, new cardholders spent $410 a month on their cards. After the points progress bar shipped, they spent $445. That rise is the business outcome. It's the last outcome in the chain, and it's what connects design and product work to a business goal.
Why it matters
Leaders fund work that moves the business. When design and product teams can only point to happier users or more clicks, their work looks like a cost. When they can show which bets moved spend or cut churn, it looks like an investment.
Business outcomes make that case. They're measured by business KPIs, the numbers already on the leadership dashboard, and they're tied to a specific bet. They also feed Results, where leaders judge whether the whole system delivered on its goals.
For each bet, name the business KPI it should move, record the number before and after, and trace it back through the product and user outcomes that explain it.
How we write one
Every business outcome is written as one sentence that names the business KPI, where it started and where it ended up:
A business KPI moved from a starting value to a new value.
Monthly card spend per new cardholder moved from $410 to $445.
Writing it this way uses the same measure leaders already track, so nobody has to translate it. The group is built into the KPI, such as "per new cardholder".
How it differs from similar ideas
-
A product outcome is a change in how people use the product, such as rewards tab visits. A business outcome is the change in money, customers or cost that usage should produce.
-
A user outcome is a change in how the experience works for people. A business outcome sits two steps later in the chain, closest to the business goal.
-
A result judges the whole system against a business goal and its target, combining everything that moved the KPI. A business outcome belongs to a single bet.
-
Business intent is what the business hopes will change. A business outcome is what actually changed, measured after the work.
-
A business goal is one of the 20 standard goals, such as Grow sales. A business outcome is the measured movement that counts toward it.
A good business outcome
-
Uses a business KPI, such as revenue, spend, churn or cost
-
Has a real before and after value
-
Uses a number leaders already track
-
Covers a stated period
-
Comes from one bet
-
Links back to a product outcome and forward to a business goal
What happens to it
-
Expected. A bet names the business KPI it should move and the goal it serves.
-
Baselined. The starting value is recorded from finance or business reporting before the change ships.
-
Measured. After launch, the same KPI is pulled again for the same group and a comparable period.
-
Rolled up. The outcome feeds the Result for its business goal, alongside outcomes from other bets.
-
Returned. The outcome goes back to Define and Collecting, where it informs new situations and business intent.
For Ray
This part tells Ray how to find business outcomes in an input, such as a finance report, a quarterly business review deck, a board update, a leadership email or a revenue dashboard export, and how to store them.
How to find one
-
Mark before and after business claims. Read the input and mark every statement that compares a business measure before and after a change.
-
Confirm it's a business KPI. Keep it only if the measure is about money, customers or cost, such as revenue, spend, churn, cost per account or support costs. Route usage to Product Outcome and experience measures to User Outcome.
-
Find the two values. Pull out the starting value and the new value, with units and the group they cover.
-
Find the period. Identify the time window for each value, and note seasonality if the source mentions it.
-
Find the bet. Identify the shipped change the input credits. If the change is credited to many factors or none, leave the bet blank and flag it.
-
Find its neighbors. Look for a product outcome that explains the change and the business goal it counts toward.
-
Write the sentence. Use the format: [Business KPI] moved from [x] to [y].
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Money and customer language: "revenue", "spend", "ARPU", "churn", "cost per", "margin", "retention rate"
-
Period comparisons: "quarter over quarter", "vs. last year", "up from", "down to"
-
Attribution language: "driven by", "thanks to", "since we launched"
-
Finance and leadership sources: QBR decks, board updates, finance dashboards
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 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 task success, ease of use or comprehension</p></td><td colspan="1" rowspan="1"><p>User Outcome</p></td></tr><tr><td colspan="1" rowspan="1"><p>Judges total progress on a goal against its target</p></td><td colspan="1" rowspan="1"><p>Result</p></td></tr><tr><td colspan="1" rowspan="1"><p>States a target the business wants to reach</p></td><td colspan="1" rowspan="1"><p>Business Intent</p></td></tr><tr><td colspan="1" rowspan="1"><p>Gives a single business number with no before value</p></td><td colspan="1" rowspan="1"><p>Benchmark</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>[Business KPI] moved from [x] to [y].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business KPI</p></td><td colspan="1" rowspan="1"><p>The business measure that moved</p></td><td colspan="1" rowspan="1"><p>Link to UX Metric tagged Business 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>Group</p></td><td colspan="1" rowspan="1"><p>Whose results were 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>The before and after windows</p></td><td colspan="1" rowspan="1"><p>Dates or periods</p></td></tr><tr><td colspan="1" rowspan="1"><p>Data source</p></td><td colspan="1" rowspan="1"><p>Where the numbers came from</p></td><td colspan="1" rowspan="1"><p>Short text, such as finance reporting</p></td></tr><tr><td colspan="1" rowspan="1"><p>Bet</p></td><td colspan="1" rowspan="1"><p>The shipped change it's credited to</p></td><td colspan="1" rowspan="1"><p>Link to Bet, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Product outcome</p></td><td colspan="1" rowspan="1"><p>The usage change that explains it</p></td><td colspan="1" rowspan="1"><p>Link to Product Outcome, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business goal</p></td><td colspan="1" rowspan="1"><p>The goal it counts toward</p></td><td colspan="1" rowspan="1"><p>One of the 20 business goals</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, after and credit are</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
A business outcome is credited to a bet only when the source makes the link. If the input just reports the number moving, store it with Bet blank and let the team decide.
Scoring confidence
Confidence measures how well the change and its link to the bet are evidenced, not how big the number 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 from finance or business reporting, comparable periods, and the source credits a named bet</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Both values given, but the period, group or credit to the 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 number is a projection, 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, group and period, add the new source to it instead of creating another.
-
Link to the bet it's credited to and the business goal it counts toward.
-
Link back to the product outcome that explains it, such as rewards tab visits rising before spend did.
-
Link forward to the result for its business goal, so it rolls up with outcomes from other bets.
-
Note breaks in the chain. If the business outcome moved with no product outcome behind it, or the product outcome moved and this didn't, flag the break.
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 business goal can be matched.
When to flag
-
A shipped bet has no business outcome measured after one full quarter
-
A business outcome is credited to a bet with no product outcome behind it
-
A business outcome moved, but no result has been updated with it
-
A projection was reported as an outcome
-
A business outcome moved the wrong way
Worked example
Input: a slide from the Q2 2027 quarterly business review deck for Cards.
"New cardholder spend: average monthly card spend in the first 90 days rose from $410 (Q4 baseline) to $445 (Q2), driven by higher rewards engagement after the progress bar launch."
What Ray finds:
-
"Average monthly card spend in the first 90 days" is spend, a business KPI.
-
"$410 (Q4 baseline)" is the before value and "$445 (Q2)" is the after value.
-
"Driven by higher rewards engagement after the progress bar launch" credits the bet and points back to the rewards tab visits product outcome.
-
The rise counts toward Grow sales, so it also feeds the Result for that goal.
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>Monthly card spend per new cardholder moved from $410 to $445.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business KPI</p></td><td colspan="1" rowspan="1"><p>Monthly card spend per new cardholder (Behavioral, Lagging, Business KPI)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Before</p></td><td colspan="1" rowspan="1"><p>$410</p></td></tr><tr><td colspan="1" rowspan="1"><p>After</p></td><td colspan="1" rowspan="1"><p>$445</p></td></tr><tr><td colspan="1" rowspan="1"><p>Group</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>Q4 2026 baseline; Q2 2027</p></td></tr><tr><td colspan="1" rowspan="1"><p>Data source</p></td><td colspan="1" rowspan="1"><p>Finance reporting, Cards QBR</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>Product outcome</p></td><td colspan="1" rowspan="1"><p>Rewards tab visits moved from 12% to 31% of weekly actives</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business goal</p></td><td colspan="1" rowspan="1"><p>Grow sales (Growth)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Cards QBR deck, Q2 2027, new cardholder spend slide</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: finance figures with comparable periods, and the source credits the bet</p></td></tr></tbody></table>
Next step: stored automatically and rolled into the Grow sales result for Q2.
Edge cases
-
Projections. "Spend should reach $460 by Q3" is a forecast. Don't store it as an outcome; note it on the business intent or a watch item instead.
-
Credit claimed by everyone. If marketing, product and pricing all claim the same spend lift, store one outcome, link it to each bet, and flag it for the team to split credit.
-
Costs that rise with success. If redemption costs went up as spend rose, store both as separate business outcomes, and check whether a risk should be raised.
-
Seasonal swings. Compare like periods when the source allows. If it compares Q4 holiday spend to Q1, lower confidence and say why.