Business intent is what the business is trying to achieve right now, and why. It sets the direction for what the team should be asking about.
For example, leadership says new cardholders aren't spending enough in their first few months, and acquisition is getting more expensive. Their intent is to get more value from each new card. That intent explains why the team is looking at the rewards program at all.
Why it matters
When intent isn't written down, teams fill the gap with guesses. Direction ends up coming from the loudest voice in the room, or from whoever spoke last, and work drifts toward projects nobody actually asked for.
Clear intent does the opposite. It tells the team which questions are worth asking, which decisions matter most, and how success will be judged. It also lets design and product connect their work to something leaders already care about.
Write down what the business wants in plain words, confirm it with the people accountable for it, and check that the team's work traces back to it.
How we write one
Every business intent is written as one sentence that names the result, who it's for, when, and why:
We want a result for a group by a time, because a reason.
We want to lift spending from new cardholders by 10% by Q2, because acquisition costs are rising and each card needs to earn more.
Writing it this way keeps the focus on the result rather than a solution, and the reason makes it easy to tell whether the intent still holds when things change.
How it differs from similar ideas
-
A business goal is one of the 20 standard goals, such as Grow sales or Reduce churn. Business intent is the specific aim behind it for this business, right now.
-
An ask is a question the team needs to answer. Business intent is the reason the question is worth asking.
-
A business outcome is a measured change after the work is done. Business intent is what the business hoped would change.
-
A constraint is a fixed limit, such as a budget or a deadline. Business intent is the direction; constraints are the boundaries.
A good business intent
-
Names a result, not a solution
-
Says who it's for
-
Has a timeframe
-
Gives a reason
-
Connects to one business goal
-
Is owned by someone accountable for it
What happens to it
-
Stated. A leader voices it, or Ray finds it in a strategy deck, plan or meeting note.
-
Agreed. The accountable leader confirms the wording, so the team isn't working from a paraphrase.
-
Active. It shapes which asks get raised and which decisions get priority.
-
Achieved or missed. Results are measured against it when the timeframe ends.
-
Replaced or retired. When priorities shift, a new intent takes its place and the old one is kept for history.
For Ray
This part tells Ray how to find business intent in an input, such as a strategy deck, a planning doc, an OKR sheet, an executive email or a kickoff note, and how to store it.
How to find one
-
Mark statements of direction. Read the input and mark every statement about what the business wants to achieve.
-
Find the result. Pull out the change the business wants. If the statement only names a solution, restate it as the result that solution is meant to deliver.
-
Find the reason. Look for why the result matters now. If no reason is given, leave it blank.
-
Find who and when. Identify the group it's for and the timeframe.
-
Map it to a business goal. Match it to one of the 20 business goals.
-
Note who stated it. Record the person or role, and whether they're accountable for the result.
-
Write the sentence. Use the format: We want [result] for [group] by [time], because [reason].
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Priority language: "this year we need to", "our priority is", "the focus for Q2", "leadership wants"
-
Objectives in OKRs, planning docs and board decks
-
Targets tied to a business measure, such as revenue, spend, churn or cost
-
A problem paired with a direction: "costs are rising, so we need to…"
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 only a solution, such as "launch a rewards banner"</p></td><td colspan="1" rowspan="1"><p>Concept, and restate the result behind it as the intent</p></td></tr><tr><td colspan="1" rowspan="1"><p>Asks a question the team needs to answer</p></td><td colspan="1" rowspan="1"><p>Ask</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports a measured result that already happened</p></td><td colspan="1" rowspan="1"><p>Business Outcome or Result</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sets a fixed limit, such as budget or timeline</p></td><td colspan="1" rowspan="1"><p>Constraint</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes what users need</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 intent</p></td><td colspan="1" rowspan="1"><p>We want [result] for [group] by [time], because [reason].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Result</p></td><td colspan="1" rowspan="1"><p>The change the business wants</p></td><td colspan="1" rowspan="1"><p>Short text, with a target if given</p></td></tr><tr><td colspan="1" rowspan="1"><p>Group</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 achieved</p></td><td colspan="1" rowspan="1"><p>Date or period</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reason</p></td><td colspan="1" rowspan="1"><p>Why it matters now</p></td><td colspan="1" rowspan="1"><p>Short text, 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 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>Stated by</p></td><td colspan="1" rowspan="1"><p>The person or role who voiced it</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 message</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>Stated, Agreed, Active, Achieved, Missed, Replaced, Retired</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How clearly it was stated</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
New intents start as Stated. Only the accountable leader can move one to Agreed.
Scoring confidence
Confidence measures how clearly the intent was stated and by whom, not how important 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 an accountable leader, with a result, a timeframe and a reason</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Stated by a leader, but the target, timeframe or reason is missing</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Inferred from indirect remarks, or stated by someone not accountable for the result</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 intent names the same result for the same group, add the new source to it instead of creating another.
-
Link to its business goal and its source input.
-
Link to the asks it shapes, and to decisions and bets that serve it.
-
Note conflicts. If two intents pull in opposite directions, such as cutting costs and expanding rewards, link them as conflicting.
-
Note replacements. When a new intent supersedes an old one, link the two and mark the old one Replaced.
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 conflicts with another intent, or when it doesn't match any business goal.
When to flag
-
An ask or bet has no business intent behind it
-
Two active intents conflict with each other
-
An active intent has no asks or decisions linked to it after 30 days
-
An intent's timeframe has passed without a result measured against it
-
An intent is being acted on but was never agreed by the accountable leader
Worked example
Input: an email from the VP of Cards to the product team.
"New cardholders are spending well below where we need them in their first 90 days, and acquisition costs keep climbing. By Q2 I want a 10% lift in early spend. Let's look at whether rewards can get us there."
What Ray finds:
-
"A 10% lift in early spend" is the result.
-
"New cardholders, first 90 days" is the group, and "by Q2" is the timeframe.
-
"Acquisition costs keep climbing" is the reason.
-
"Look at whether rewards can get us there" is a question, so it becomes a separate Ask, linked to this intent.
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>We want a 10% lift in spending from new cardholders by Q2, because acquisition costs keep climbing.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Result</p></td><td colspan="1" rowspan="1"><p>10% lift in first-90-day spend</p></td></tr><tr><td colspan="1" rowspan="1"><p>Group</p></td><td colspan="1" rowspan="1"><p>New cardholders, first 90 days</p></td></tr><tr><td colspan="1" rowspan="1"><p>Timeframe</p></td><td colspan="1" rowspan="1"><p>Q2 2027</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reason</p></td><td colspan="1" rowspan="1"><p>Acquisition costs keep climbing</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>Stated by</p></td><td colspan="1" rowspan="1"><p>VP of Cards</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Email to product team, October 2026</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Stated</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: written by the accountable leader with a result, timeframe and reason</p></td></tr></tbody></table>
Next step: stored automatically, with a prompt to the VP to confirm the wording and move it to Agreed.
Edge cases
-
Stated as a solution. "We need a new rewards app" names a solution. Store the app as a Concept and ask what result it's meant to deliver.
-
Several intents in one statement. "Grow spend and cut support costs" is two intents. Split them, and check whether they conflict.
-
One loud voice. An intent voiced by one person in a meeting stays at low confidence until the accountable leader confirms it.
-
Intent changes. Don't edit the old intent. Store the new one, link it as a replacement, and flag any work still tied to the old one.