Business Goal

A business goal is one of 20 standard goals that a business works toward, such as Grow sales, Reduce churn or Drive adoption. Leadership sets which goals matter, and every situation the team looks at is weighed against them.

For example, SecondBank's leaders want each new card to earn more in its first few months. That puts Grow sales at the top of the list. When the team asks whether the rewards dashboard is worth redesigning, the answer depends on whether it can move Grow sales.

Why it matters

Every team describes goals in its own words. Marketing says "engagement", product says "activation", finance says "early revenue". Without a shared list, it's hard to see that three teams are chasing the same thing, or that one team is chasing something nobody asked for.

A fixed set of 20 goals gives everyone the same vocabulary. It makes work comparable across teams, shows which goals are crowded and which are ignored, and gives Results something stable to be measured against.

The 20 goals fall into five groups of four. Growth: Prove product fit, Attract new customers, Grow sales, Gain market share. Retention: Keep customers, Reduce churn, Earn loyalty, Increase spend. User Experience: Show value fast, Drive adoption, Improve customer satisfaction, Prove launch success. Efficiency: Work faster, Lower support costs, Scale efficiently, Fund what matters. Operations: Align strategy, Lead with evidence, Strengthen brand trust, Prove design impact.

Have leadership pick the few goals that matter most this period, attach a measure and target to each, and check that every bet traces back to one of them.

How we write one

Every business goal is written as the goal's name followed by its category:

The goal (its category)

Grow sales (Growth)

Using the exact name from the list keeps goals comparable across teams and over time. The details of what the business wants right now live in the business intent that points to the goal.

How it differs from similar ideas

  • Business intent is the specific aim right now, with a group, a timeframe and a reason, such as lifting new cardholder spend 10% by Q2. A business goal is the standard goal that intent serves, such as Grow sales.

  • A result is what the whole system actually delivered against a goal in a period. A business goal is what it's measured against.

  • A business outcome is a measured change from one bet, such as spend per new cardholder rising from $410 to $445. A business goal is where that change counts.

  • A user need is one of 20 things people need from the product. A business goal is one of 20 things the business needs. The mapping chain connects the two through outcomes.

  • A bet is a commitment to a specific change. A business goal is the reason the bet is worth making.

A well-used business goal

  • Uses the exact name from the 20 goals

  • Is set or confirmed by leadership

  • Has a measure and a target for the period

  • Has at least one business intent pointing to it

  • Has bets and outcomes traced back to it

  • Is one of a few priorities, not one of many

What happens to it

  1. Selected. Leadership picks the goals that matter for the period, usually during planning.

  2. Targeted. Each goal gets a measure and a target, often taken from the business intent behind it.

  3. Active. Situations are weighed against it in Lead, and bets, outcomes and workflows are traced to it.

  4. Measured. At the end of the period, a Result records how the system did against its target.

  5. Renewed or set aside. Leadership keeps it for the next period or drops it. Past goals and results are kept for history.


For Ray

This part tells Ray how to find business goals in an input, such as an annual plan, an OKR sheet, a board deck, a leadership email or a strategy offsite summary, and how to match them to the list of 20. Ray never creates a free-form goal.

How to find one

  1. Mark statements of priority. Read the input and mark every statement about what the business is trying to achieve over a period.

  2. Strip it to the aim. Set aside the group, timeframe and reason; those belong in the business intent. Keep only the kind of result being sought.

  3. Match it to the list. Compare the aim to the 20 business goals and pick the closest one, using the category cues below.

  4. Check close matches. If two goals fit, use the KPI and the audience to decide. If it still fits two, store the stronger match and note the other.

  5. Find the measure and target. Pull out the KPI and target leaders attach to it for the period, if given.

  6. Note who set it. Record the leader or group who set or confirmed it, and the planning period.

  7. Write the sentence. Use the format: [Goal] ([category]).

  8. Fill the record, score it, link it and store it using the rules below.

Cues to look for

  • Planning language: "our priorities this year", "objective", "strategic pillar", "north star"

  • OKR objectives and the key results under them

  • Named business measures with targets: revenue, spend, churn, NPS, support cost, time to market

  • Board and leadership decks that rank or group priorities

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 a specific aim with a group, timeframe and reason</p></td><td colspan="1" rowspan="1"><p>Business Intent, linked to the matching goal</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports progress or a final number against a target</p></td><td colspan="1" rowspan="1"><p>Result</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports a measured change from one bet</p></td><td colspan="1" rowspan="1"><p>Business Outcome</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><tr><td colspan="1" rowspan="1"><p>Can't be matched to any of the 20 goals</p></td><td colspan="1" rowspan="1"><p>Leave unmatched and send to the review digest</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 goal and its category</p></td><td colspan="1" rowspan="1"><p>[Goal] ([category]).</p></td></tr><tr><td colspan="1" rowspan="1"><p>Goal</p></td><td colspan="1" rowspan="1"><p>The matched goal</p></td><td colspan="1" rowspan="1"><p>One of the 20 business goals</p></td></tr><tr><td colspan="1" rowspan="1"><p>Category</p></td><td colspan="1" rowspan="1"><p>Its group</p></td><td colspan="1" rowspan="1"><p>Growth, Retention, User Experience, Efficiency, Operations</p></td></tr><tr><td colspan="1" rowspan="1"><p>Wording in source</p></td><td colspan="1" rowspan="1"><p>How the input phrased it</p></td><td colspan="1" rowspan="1"><p>Exact quote</p></td></tr><tr><td colspan="1" rowspan="1"><p>Measure</p></td><td colspan="1" rowspan="1"><p>The KPI leaders track for it</p></td><td colspan="1" rowspan="1"><p>Link to UX Metric tagged Business KPI, or blank</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, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Period</p></td><td colspan="1" rowspan="1"><p>The planning period it's active for</p></td><td colspan="1" rowspan="1"><p>Date or period</p></td></tr><tr><td colspan="1" rowspan="1"><p>Set by</p></td><td colspan="1" rowspan="1"><p>The leader or group who set it</p></td><td colspan="1" rowspan="1"><p>Name or role</p></td></tr><tr><td colspan="1" rowspan="1"><p>Priority</p></td><td colspan="1" rowspan="1"><p>Its rank among active goals, if given</p></td><td colspan="1" rowspan="1"><p>Number, 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>Status</p></td><td colspan="1" rowspan="1"><p>Where it stands</p></td><td colspan="1" rowspan="1"><p>Selected, Active, Measured, Renewed, Set aside</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How clear the match and the mandate are</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>

Each of the 20 goals is stored once per business and period. New sources, intents and targets attach to that one record.

Scoring confidence

Confidence measures how clearly the input matches one goal and how clearly leadership set it, not how important the goal 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>Set in writing by leadership, matches one goal clearly, with a measure and target</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Set by leadership, but the match is close between two goals, or the measure or target 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 raised by someone without the authority to set it</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.

Matching to a category

Use these cues to find the right category first, then the right goal within it.

<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>Category</p></th><th colspan="1" rowspan="1"><p>Typical aims and measures</p></th></tr><tr><td colspan="1" rowspan="1"><p>Growth</p></td><td colspan="1" rowspan="1"><p>New customers, total sales, market share, proof that the product fits a market</p></td></tr><tr><td colspan="1" rowspan="1"><p>Retention</p></td><td colspan="1" rowspan="1"><p>Keeping existing customers, churn, loyalty, spend from customers already on board</p></td></tr><tr><td colspan="1" rowspan="1"><p>User Experience</p></td><td colspan="1" rowspan="1"><p>Time to value, adoption of features, satisfaction scores, launch success</p></td></tr><tr><td colspan="1" rowspan="1"><p>Efficiency</p></td><td colspan="1" rowspan="1"><p>Speed, support costs, cost to scale, where budget goes</p></td></tr><tr><td colspan="1" rowspan="1"><p>Operations</p></td><td colspan="1" rowspan="1"><p>Strategic alignment, evidence-based decisions, brand trust, proof that design pays off</p></td></tr></tbody></table>

Grow sales and Increase spend are the most common close match. Use Grow sales when the aim is revenue from new customers or the business overall; use Increase spend when it's deeper spend from established customers.

Linking

  • Check for duplicates first. If the goal already exists for this business and period, add the new source, intent or target to it instead of creating another.

  • Link to the business intents that point to it, and its source input.

  • Link to bets, business outcomes and workflows traced to it, so the mapping chain from user need to goal is complete.

  • Link to results measured against it at the end of each period.

  • Note conflicts. If two active goals pull against each other, such as Grow sales and Lower support costs, link them as conflicting.

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 statement can't be matched to any of the 20 goals, or when it conflicts with another active goal.

When to flag

  • A bet or business intent has no business goal linked to it

  • An active goal has no measure or target

  • An active goal has no bets traced to it after one quarter

  • More than five goals are active at once

  • A period ended without a result measured against an active goal

Worked example

Input: a row from the FY27 OKR sheet for the Cards business.

"Objective: Grow card revenue from new accounts. KR1: First-90-day spend per new cardholder +10% by end of Q2. Owner: VP of Cards. Priority 1."

What Ray finds:

  • "Grow card revenue from new accounts" is about revenue from new customers, so it matches Grow sales (Growth).

  • "First-90-day spend per new cardholder" is the measure and "+10% by end of Q2" is the target.

  • "Owner: VP of Cards" is who set it, and "Priority 1" is its rank.

  • The same aim already exists as a business intent from the VP's email, so Ray links the two rather than storing it twice.

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 (Growth).</p></td></tr><tr><td colspan="1" rowspan="1"><p>Goal</p></td><td colspan="1" rowspan="1"><p>Grow sales</p></td></tr><tr><td colspan="1" rowspan="1"><p>Category</p></td><td colspan="1" rowspan="1"><p>Growth</p></td></tr><tr><td colspan="1" rowspan="1"><p>Wording in source</p></td><td colspan="1" rowspan="1"><p>"Grow card revenue from new accounts"</p></td></tr><tr><td colspan="1" rowspan="1"><p>Measure</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>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>FY27, through Q2 2027</p></td></tr><tr><td colspan="1" rowspan="1"><p>Set by</p></td><td colspan="1" rowspan="1"><p>VP of Cards</p></td></tr><tr><td colspan="1" rowspan="1"><p>Priority</p></td><td colspan="1" rowspan="1"><p>1</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>FY27 Cards OKR sheet, Objective 1</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Active</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: set in writing by leadership, one clear match, with a measure and target</p></td></tr></tbody></table>

Next step: stored automatically and linked to the business intent to lift new cardholder spend 10% by Q2.

Edge cases

  • Free-form goals. "Become the most loved card" isn't on the list. Match it to the closest goal, such as Earn loyalty, keep the original wording, and lower confidence.

  • Goals stated as projects. "Ship the new rewards app" is a concept. Ask which goal it serves and store that goal instead.

  • One objective, two goals. "Grow revenue and cut support costs" is Grow sales and Lower support costs. Store both and check whether they conflict.

  • Team-level goals. A team may set its own goal, such as Prove design impact. Store it with the team as Set by, and keep it separate from company goals.

Identify where decision quality breaks down

The Glare Design Assessment helps teams spot weak validation, stakeholder friction, alignment gaps, and assumptions that scale without measurable learning—so you have a clearer starting point for improvement.

About 5 minutes · Team-based · Diagnostic snapshot you can act on

Take the Design Assessment