A result is what the whole system delivered against a business goal by the end of a period. It adds up the business outcomes from every bet and compares the total to the target leaders set.
For example, SecondBank set a target to lift new cardholder spend 10% by Q2. By the end of Q2, spend had risen 8.5%. That's the result: close, but short of the target. It also shows which bets did the work, and it raises the question of whether rising redemption costs are a new risk.
Why it matters
Most teams report on their own work: this feature shipped, that test passed. Leaders are left to piece together whether any of it moved the goals they set. Wins get claimed twice and misses get explained away.
Results answer the question leaders actually ask: did we deliver? They look across every bet, compare the total against a target, and show which bets moved the business and which didn't. They also surface what could go wrong next, so the next round of decisions starts from evidence.
At the end of each period, measure each active goal against its target, name the bets that contributed, and raise any risks the numbers reveal.
How we write one
Every result is written as one sentence that names the goal, the KPI, the value reached, the target and the period:
A goal**:** a KPI reached a value against a target of a target in a period.
Grow sales: first-90-day spend per new cardholder reached an 8.5% lift against a target of 10% in Q2 2027.
Writing it this way puts the target right next to the number, so anyone can tell at a glance whether the goal was met. Leading with the goal keeps the focus on what the business wanted, not on any one project.
How it differs from similar ideas
-
A business outcome is a measured change from one bet. A result adds up the outcomes from every bet that touched a goal and judges the total against a target.
-
A business goal is what the business is aiming for. A result is how it actually did against that goal in a period.
-
Business intent is the aim the business set at the start. A result is the answer at the end.
-
Findings report what one round of testing learned about a concept. A result reports what the business gained once the work shipped.
-
A risk is what could go wrong next. Results raise risks when the numbers point to a problem.
A good result
-
Names one business goal
-
Compares a measured value to a set target
-
Covers a full, stated period
-
Lists the bets that contributed and how much
-
Says plainly whether the goal was met, partly met or missed
-
Raises any risks the numbers reveal
What happens to it
-
Defined. A business goal gets a measure and target for the period.
-
Tracking. Business outcomes from each bet roll up toward it as they're measured.
-
Measured. At the end of the period, the final value is compared to the target.
-
Judged. The result is marked met, partly met or missed, and credit is assigned to the bets that contributed.
-
Returned. Risks it raises go to the loop, and the result goes back to Define and Collecting to shape the next business intent.
For Ray
This part tells Ray how to find results in an input, such as a quarterly business review deck, a board update, a finance close memo, an OKR scorecard or a leadership email, and how to store them.
How to find one
-
Mark statements of progress against a target. Read the input and mark every statement that compares a business number to a goal or target.
-
Match the goal. Link it to the active business goal it measures. If no active goal matches, leave it blank and flag it.
-
Find the value and target. Pull out the value reached and the target. If no target is stated, check the goal's record for one.
-
Find the period and judge the status. Identify the period it covers. If it's complete, mark the result Met, Partly met or Missed by comparing the value to the target; if not, mark it Tracking.
-
Find the contributing bets. Identify which bets the input credits, and link the business outcomes that roll up into it.
-
Look for risks. Note any cost, side effect or trend the input mentions that could hurt the business, and raise each as a Risk.
-
Write the sentence. Use the format: [Goal]: [KPI] reached [value] against a target of [target] in [period].
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Target language: "vs. goal", "against target", "of plan", "hit", "missed", "on track"
-
Period close language: "Q2 close", "year end", "final numbers"
-
Scorecards and OKR grades: red, amber, green; 0.7 of 1.0
-
Attribution across work: "most of the lift came from", "had little effect"
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 from one bet with no target</p></td><td colspan="1" rowspan="1"><p>Business Outcome</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports progress partway through the period</p></td><td colspan="1" rowspan="1"><p>Update the open Result as Tracking</p></td></tr><tr><td colspan="1" rowspan="1"><p>States a target for the future</p></td><td colspan="1" rowspan="1"><p>Business Intent or a target on the Business Goal</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports usage or experience changes</p></td><td colspan="1" rowspan="1"><p>Product Outcome or User Outcome</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes what could go wrong without a measured result</p></td><td colspan="1" rowspan="1"><p>Risk</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 result</p></td><td colspan="1" rowspan="1"><p>[Goal]: [KPI] reached [value] against a target of [target] in [period].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business goal</p></td><td colspan="1" rowspan="1"><p>The goal it's measured against</p></td><td colspan="1" rowspan="1"><p>Link to Business Goal</p></td></tr><tr><td colspan="1" rowspan="1"><p>KPI</p></td><td colspan="1" rowspan="1"><p>The business measure</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>Value reached</p></td><td colspan="1" rowspan="1"><p>The final measured value</p></td><td colspan="1" rowspan="1"><p>Number with unit</p></td></tr><tr><td colspan="1" rowspan="1"><p>Target</p></td><td colspan="1" rowspan="1"><p>The target for the period</p></td><td colspan="1" rowspan="1"><p>Number with unit</p></td></tr><tr><td colspan="1" rowspan="1"><p>Period</p></td><td colspan="1" rowspan="1"><p>The period it covers</p></td><td colspan="1" rowspan="1"><p>Date or period</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>How it compares to the target</p></td><td colspan="1" rowspan="1"><p>Tracking, Met, Partly met, Missed</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business outcomes</p></td><td colspan="1" rowspan="1"><p>The outcomes that roll up into it</p></td><td colspan="1" rowspan="1"><p>Links to Business Outcome</p></td></tr><tr><td colspan="1" rowspan="1"><p>Contributing bets</p></td><td colspan="1" rowspan="1"><p>The bets credited, with their share if given</p></td><td colspan="1" rowspan="1"><p>Links to Bet</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business intent</p></td><td colspan="1" rowspan="1"><p>The aim it answers</p></td><td colspan="1" rowspan="1"><p>Link to Business Intent</p></td></tr><tr><td colspan="1" rowspan="1"><p>Risks raised</p></td><td colspan="1" rowspan="1"><p>Problems the numbers reveal</p></td><td colspan="1" rowspan="1"><p>Links to Risk, or blank</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 row</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 value, target and credit are</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
Use Partly met when the value moved toward the target but fell short. A result stays at Tracking until the period is complete.
Scoring confidence
Confidence measures how solid the numbers and the credit to bets are, not whether the goal was met.
<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>Final figures from finance or business reporting, a stated target, a complete period, and named contributing bets</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Final figures and a target, but credit to bets is unclear or the period is partial</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Estimated or preliminary figures, no stated target, 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 a result already exists for the same goal and period, update it with the new source instead of creating another.
-
Link to the business goal it's measured against, and the business intent it answers.
-
Link to every business outcome that rolls up into it, and to the bets those outcomes came from.
-
Link to the risks it raises, so they enter the loop and return to Define and Collecting.
-
Note conflicts in credit. If the outcomes linked to it add up to more than the total change, flag it so the team can sort out double counting.
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 the goal was missed, or when it raises a risk.
When to flag
-
A period ended with no result for an active goal
-
A result has no contributing bets linked to it
-
Linked outcomes add up to more than the total change
-
A goal was missed two periods in a row
-
A result raised a risk that has no owner
Worked example
Input: a Q2 close memo from Cards finance to the leadership team.
"Q2 close: first-90-day spend per new cardholder up 8.5% ($410 to $445) vs. the 10% goal. Most of the lift tracks to the rewards progress bar; the onboarding email update added little on its own. Note: redemption costs are running 14% over plan."
What Ray finds:
-
"Up 8.5% vs. the 10% goal" is the value reached and the target, for Grow sales.
-
"Q2 close" means the period is complete, so the status is Partly met.
-
"Most of the lift tracks to the rewards progress bar" credits that bet; the onboarding email change gets a small share.
-
"Redemption costs are running 14% over plan" is a warning, so it becomes a separate Risk linked to this result.
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>Grow sales: first-90-day spend per new cardholder reached an 8.5% lift against a target of 10% in Q2 2027.</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>KPI</p></td><td colspan="1" rowspan="1"><p>First-90-day spend per new cardholder (Business KPI)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Value reached</p></td><td colspan="1" rowspan="1"><p>+8.5% ($410 to $445)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Target</p></td><td colspan="1" rowspan="1"><p>+10%</p></td></tr><tr><td colspan="1" rowspan="1"><p>Period</p></td><td colspan="1" rowspan="1"><p>Q2 2027</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Partly met</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business outcomes</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>Contributing bets</p></td><td colspan="1" rowspan="1"><p>We bet the progress bar will drive adoption (most of the lift); onboarding email update (small share)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business intent</p></td><td colspan="1" rowspan="1"><p>We want a 10% lift in spending from new cardholders by Q2</p></td></tr><tr><td colspan="1" rowspan="1"><p>Risks raised</p></td><td colspan="1" rowspan="1"><p>Redemption costs could exceed budget if adoption grows faster than spend</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Cards finance Q2 close memo, July 2027</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: final finance figures, a stated target, a complete period and named bets</p></td></tr></tbody></table>
Flag raised: sent to the review digest because the goal was partly met and the result raises a redemption cost risk.
Edge cases
-
Mid-period updates. "We're at 6% with a month to go" is progress. Store it as Tracking and update the same result when the period closes.
-
Targets that moved. If leadership changed the target during the period, record the final target, note the original, and lower confidence.
-
No bet gets credit. If the goal moved but the input credits market conditions, store the result with no contributing bets and flag it, since the system may not have delivered it.
-
Good result, new risk. A met goal can still raise a risk, such as costs rising faster than revenue. Store both and link them.