An initiative is a body of work the team commits to after testing shows something is worth pursuing. It turns evidence into a focused effort with a clear audience and a deadline.
For example, testing showed that new cardholders couldn't tell what their points were worth, and a progress bar fixed much of that. The team starts an initiative to improve rewards visibility for new cardholders by the end of Q1. That initiative is where the progress bar work now lives.
Why it matters
Without a named initiative, good findings sit in a readout and nothing happens. Or the opposite happens: several people start related work on their own, and effort gets spread thin across overlapping projects.
A clear initiative gives the work a home. It says what situation is being improved, for whom, and by when. It also makes it easy to see which signals started it, which variable it compares across, which methods are being used, and which business goal it serves.
Start an initiative only when signals support it, name one situation and one audience, set a timeframe, and check that it traces back to a business goal.
How we write one
Every initiative is written as one sentence that names the situation, the audience and the timeframe:
Improve a situation for an audience by a timeframe.
Improve rewards visibility for new cardholders by end of Q1.
Writing it this way keeps the initiative about a situation that needs to get better, rather than a single solution, so the team can try more than one method to get there.
How it differs from similar ideas
-
A concept is one proposed solution, such as the progress bar. An initiative is the wider body of work that may test, compare and ship several concepts.
-
A bet is a high-stakes commitment that names a goal, the workflows it affects and the metric that will judge it. An initiative is the work that comes before and around that commitment.
-
A method is a technique used in Comparing, such as an A/B test, and a variable is the one thing that changes between measurements, such as the version. The initiative is the work both serve.
-
Business intent is what the business wants overall. An initiative is one focused effort that contributes to it.
A good initiative
-
Names a situation to improve, not a single solution
-
Says who it's for
-
Has a timeframe
-
Is started by at least one signal from findings
-
Connects to one business goal
-
Has an owner
What happens to it
-
Proposed. Findings send a signal and someone suggests a body of work to act on it.
-
Started. The owner confirms the scope, audience and timeframe, and work begins.
-
In progress. The team names the variable, repeats the same measurement across it in Comparing, and reads the options against benchmarks.
-
Reported. It ends in a bet, and its outputs move through the coded library and design system, tied to a business goal.
-
Closed or stopped. It ends when the timeframe passes or the work is done, or it stops early if signals no longer support it.
For Ray
This part tells Ray how to find an initiative in an input, such as a roadmap, a planning doc, a kickoff deck, a findings readout or a project brief, and how to store it.
How to find one
-
Mark commitments to a body of work. Read the input and mark every statement that starts, names or scopes a piece of ongoing work.
-
Find the situation. Pull out what is being improved. If the statement only names a solution, restate it as the situation that solution is meant to improve.
-
Find the audience and timeframe. Identify who the work is for and when it should be done. If either is missing, leave it blank.
-
Find the signals behind it. Look for the findings or signals that started the work. If none are cited, leave the field blank.
-
Find the variable and methods. Note the one thing that will change between measurements, such as the version or the audience, and any techniques named for comparing it, such as an A/B test. Store each technique as a separate Method.
-
Map it to a business goal. Match it to one of the 20 business goals.
-
Write the sentence. Use the format: Improve [situation] for [audience] by [timeframe].
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Commitment language: "we're kicking off", "next quarter we'll focus on", "the workstream", "this initiative"
-
Roadmap rows and project names with an owner and a date
-
A findings readout that ends with "move to iteration" or "take this forward"
-
A situation paired with a deadline: "get rewards visibility up by end of Q1"
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>Names one proposed solution, such as "add a progress bar"</p></td><td colspan="1" rowspan="1"><p>Concept, linked to the initiative if one exists</p></td></tr><tr><td colspan="1" rowspan="1"><p>Commits to a change with a goal, affected workflows and a metric</p></td><td colspan="1" rowspan="1"><p>Bet</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes how the work will be done, such as "run an A/B test"</p></td><td colspan="1" rowspan="1"><p>Method</p></td></tr><tr><td colspan="1" rowspan="1"><p>Suggests a next action from a single test</p></td><td colspan="1" rowspan="1"><p>Recommendation</p></td></tr><tr><td colspan="1" rowspan="1"><p>States what the business wants overall</p></td><td colspan="1" rowspan="1"><p>Business Intent</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 initiative</p></td><td colspan="1" rowspan="1"><p>Improve [situation] for [audience] by [timeframe].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Situation</p></td><td colspan="1" rowspan="1"><p>What is being improved</p></td><td colspan="1" rowspan="1"><p>Link to Situation</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Who it's for</p></td><td colspan="1" rowspan="1"><p>Link to Audience</p></td></tr><tr><td colspan="1" rowspan="1"><p>Timeframe</p></td><td colspan="1" rowspan="1"><p>When it should be done</p></td><td colspan="1" rowspan="1"><p>Date or period</p></td></tr><tr><td colspan="1" rowspan="1"><p>Started by</p></td><td colspan="1" rowspan="1"><p>The signals that started it</p></td><td colspan="1" rowspan="1"><p>Links to Signal and Findings</p></td></tr><tr><td colspan="1" rowspan="1"><p>Methods</p></td><td colspan="1" rowspan="1"><p>Comparison techniques chosen, and the variable they compare across</p></td><td colspan="1" rowspan="1"><p>Links to Method, with the variable named</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business goal</p></td><td colspan="1" rowspan="1"><p>The goal it serves</p></td><td colspan="1" rowspan="1"><p>One of the 20 business goals</p></td></tr><tr><td colspan="1" rowspan="1"><p>Owner</p></td><td colspan="1" rowspan="1"><p>The person accountable for the work</p></td><td colspan="1" rowspan="1"><p>Name or role</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>Status</p></td><td colspan="1" rowspan="1"><p>Where it stands</p></td><td colspan="1" rowspan="1"><p>Proposed, Started, In progress, Reported, Closed, Stopped</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How clearly it was stated and supported</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
New initiatives start as Proposed. Only the owner can move one to Started.
Scoring confidence
Confidence measures how clearly the initiative was scoped and how well it is tied to evidence, not how promising it sounds.
<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>Stated in writing by the owner, with a situation, audience and timeframe, and linked to at least one signal</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Clearly stated, but the timeframe, owner or supporting signal is missing</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Inferred from loose talk about future work, or named only as a solution</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 initiative improves the same situation for the same audience, add the new source to it instead of creating another.
-
Link to the signals and findings that started it, and to its source input.
-
Link to its variable and methods and to any benchmarks used to compare options.
-
Link to its business goal, and to any bet that grows out of it.
-
Note overlaps. If two initiatives target the same situation or audience, link them as overlapping so the owners can decide whether to merge.
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 has no supporting signal, when it overlaps another initiative, or when it doesn't match any business goal.
When to flag
-
An initiative has no signal or findings behind it
-
An initiative has no variable or method linked to it after 30 days
-
An initiative's timeframe has passed and it is still In progress
-
Two active initiatives target the same situation and audience
-
An initiative doesn't trace to any business goal
Worked example
Input: a product roadmap row added after the value test readout.
"Rewards visibility (new cardholders). Owner: product lead. Due: end of Q1. Why: value test showed the progress bar lifted task success from 42% to 78%. Next: A/B test two progress bar variants."
What Ray finds:
-
"Rewards visibility" is the situation, and "new cardholders" is the audience.
-
"End of Q1" is the timeframe, and the product lead is the owner.
-
"Value test showed the progress bar lifted task success" points to the signal and findings that started it.
-
"A/B test two progress bar variants" is a separate Method, linked to this initiative.
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>Improve rewards visibility for new cardholders by end of Q1.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Situation</p></td><td colspan="1" rowspan="1"><p>New cardholders rarely open the rewards tab, so earned points go unused</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Customers: new cardholders, first 90 days</p></td></tr><tr><td colspan="1" rowspan="1"><p>Timeframe</p></td><td colspan="1" rowspan="1"><p>End of Q1 2027</p></td></tr><tr><td colspan="1" rowspan="1"><p>Started by</p></td><td colspan="1" rowspan="1"><p>Signal: low task success shows point value is unclear; Findings: progress bar raised task success to 78%</p></td></tr><tr><td colspan="1" rowspan="1"><p>Methods</p></td><td colspan="1" rowspan="1"><p>A/B test two progress bar variants</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business goal</p></td><td colspan="1" rowspan="1"><p>Drive adoption (User Experience)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Owner</p></td><td colspan="1" rowspan="1"><p>Product lead</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Product roadmap, October 2026</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Proposed</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: written by the owner with a situation, audience, timeframe and supporting signal</p></td></tr></tbody></table>
Next step: stored automatically, with a prompt to the product lead to confirm scope and move it to Started.
Edge cases
-
Named as a solution. "The progress bar project" names a concept. Store the progress bar as a Concept and restate the initiative as the situation it improves.
-
Already a bet. If the statement names the goal, the workflows affected and the metric, store it as a Bet and link it to the initiative it came from.
-
No evidence yet. Work started from a hunch or a leader's request, without findings, stays at low confidence and is flagged as having no signal.
-
Scope changes. Don't overwrite the old scope. Update the record, keep the earlier version in history, and flag any methods that no longer fit.