Bet

A bet is a commitment to make a product or marketing change that will ripple through how the business works. It is the highest-stakes kind of decision in Glare, because it moves budgets, people and priorities across more than one team.

For example, after testing and an A/B test, the team commits to putting the points progress bar in front of every new cardholder. They expect it to drive adoption of rewards, it will change how Product and Marketing work, and they will judge it by rewards redemptions. That commitment is the bet.

Why it matters

Big changes often get approved on enthusiasm. Nobody writes down which goal the change is meant to move, which teams will feel it, or how anyone will know if it worked. Months later the change is live, the costs are real, and the team can't say whether it paid off.

A clear bet fixes that before the money is spent. It names the goal, the workflows that will change and the metric that will judge it, so leaders can see what they are committing to and the evidence behind it. It also gives the team a fair way to call the result later.

Make the bet explicit, rank it against the other options with a prioritizing technique such as RICE or ICE, size it to the evidence, name every workflow it touches, and agree on the metric before it ships.

How we write one

Every bet is written as one sentence that names the change, the goal, the workflows affected and the metric:

We bet a change will move a goal, affecting workflows; measured by a metric.

We bet the progress bar will move Drive adoption, affecting Product and Marketing; measured by rewards redemptions.

Writing it this way forces the three things a big commitment needs before it ships: the goal it serves, the teams it changes, and the number that will settle whether it worked.

How it differs from similar ideas

  • A decision is any call made at any stage. A bet is the highest-stakes type, made in Bets, the last block in Focus: a product or marketing decision, sized to the evidence, that affects workflows.

  • An initiative is a body of work that names a variable and compares options across it. A bet is the commitment that comes out of that work.

  • A hunch is an untested belief. A bet should rest on tested evidence, such as signals, findings and UX metrics.

  • A business outcome is the measured change after the bet ships. The bet is the commitment that is expected to produce it.

A good bet

  • Names the change being committed to

  • Names one business goal it should move

  • Names every workflow it affects, from the eight

  • Names the metric that will judge it

  • Is backed by evidence, such as signals and UX metrics

  • Has an owner who can approve it

What happens to it

  1. Proposed. Someone puts forward a change and the evidence behind it.

  2. Approved. The accountable leader signs off on the change, the goal, the workflows and the metric.

  3. Live. The change ships and the affected workflows start working differently.

  4. Measured. User, product and business outcomes are read against the metric and the goal.

  5. Won, lost or reversed. The bet is called against its metric, and watch items or risks it raises loop back to Define.


For Ray

This part tells Ray how to find a bet in an input, such as a decision memo, an investment proposal, a launch plan, a steering committee deck or leadership meeting notes, and how to store it.

How to find one

  1. Mark commitments to a change. Read the input and mark every statement that commits to shipping or launching a product or marketing change.

  2. Find the change. Pull out what will be different. Link it to the concept and the comparison result it comes from.

  3. Find the goal. Match the goal it should move to one of the 20 business goals. If none is stated, leave it blank.

  4. Find the workflows. Identify which of the eight workflows will change: Sales, Marketing, Product, Engineering, Strategy, Operations, Finance, Legal. If none are named, leave it blank.

  5. Find the metric. Look for the measure that will judge the bet. If none is named, leave it blank.

  6. Find the evidence. Look for the signals, findings or UX metrics cited in support. Note if there are none.

  7. Write the sentence. Use the format: We bet [change] will move [goal], affecting [workflows]; measured by [metric].

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

Cues to look for

  • Commitment language: "we're going all in on", "we're committing to", "approved for launch", "green-lit"

  • Investment requests with a budget, a goal and an expected return

  • Launch plans that list teams needing to change, such as Marketing, Sales or Operations

  • A change paired with a success measure: "if redemptions go up, we'll know it worked"

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>Is a smaller call that doesn't affect any workflow</p></td><td colspan="1" rowspan="1"><p>Decision</p></td></tr><tr><td colspan="1" rowspan="1"><p>Starts a body of work without committing to a change</p></td><td colspan="1" rowspan="1"><p>Initiative</p></td></tr><tr><td colspan="1" rowspan="1"><p>Is a belief that hasn't been tested</p></td><td colspan="1" rowspan="1"><p>Hunch</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes how a single function changes</p></td><td colspan="1" rowspan="1"><p>Workflow, linked to the bet</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports a measured change after launch</p></td><td colspan="1" rowspan="1"><p>User, Product or Business Outcome</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 bet</p></td><td colspan="1" rowspan="1"><p>We bet [change] will move [goal], affecting [workflows]; measured by [metric].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Change</p></td><td colspan="1" rowspan="1"><p>What will be different</p></td><td colspan="1" rowspan="1"><p>Short text, with links to Concept and the comparison it won</p></td></tr><tr><td colspan="1" rowspan="1"><p>Business goal</p></td><td colspan="1" rowspan="1"><p>The goal it should move</p></td><td colspan="1" rowspan="1"><p>One of the 20 business goals</p></td></tr><tr><td colspan="1" rowspan="1"><p>Workflows</p></td><td colspan="1" rowspan="1"><p>The functions that will change</p></td><td colspan="1" rowspan="1"><p>One or more of the 8 workflows, with links to Workflow</p></td></tr><tr><td colspan="1" rowspan="1"><p>Metric</p></td><td colspan="1" rowspan="1"><p>The measure that will judge it</p></td><td colspan="1" rowspan="1"><p>Link to UX Metric or KPI</p></td></tr><tr><td colspan="1" rowspan="1"><p>Evidence</p></td><td colspan="1" rowspan="1"><p>What supports it</p></td><td colspan="1" rowspan="1"><p>Links to Signal, Findings, UX Metric</p></td></tr><tr><td colspan="1" rowspan="1"><p>Initiative</p></td><td colspan="1" rowspan="1"><p>The work it came from</p></td><td colspan="1" rowspan="1"><p>Link to Initiative</p></td></tr><tr><td colspan="1" rowspan="1"><p>Owner</p></td><td colspan="1" rowspan="1"><p>The person who approves 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>Proposed, Approved, Live, Measured, Won, Lost, Reversed</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>

Every bet goes to the review digest, whatever its confidence, because bets are high-stakes. Only the owner can move one to Approved.

Scoring confidence

Confidence measures how completely the bet was stated, not how likely it is to win.

<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 change, a goal, named workflows and a metric</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>The change and goal are clear, but the workflows or metric are missing</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Inferred from enthusiasm or loose talk, with no goal, workflows or metric</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.

Judging the evidence

Separately from confidence, Ray scores how well the bet is supported by evidence already in the system. This is what the cloud view shows leaders.

<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>Strong</p></td><td colspan="1" rowspan="1"><p>Linked to tested signals and UX metrics from more than one method or round</p></td></tr><tr><td colspan="1" rowspan="1"><p>Partial</p></td><td colspan="1" rowspan="1"><p>Linked to one round of findings, or to signals with weak or mixed strength</p></td></tr><tr><td colspan="1" rowspan="1"><p>None</p></td><td colspan="1" rowspan="1"><p>No linked signals, findings or UX metrics; resting on hunches or opinion</p></td></tr></tbody></table>

A bet with no evidence is always flagged, even if its statement is complete.

Linking

  • Check for duplicates first. If an existing bet commits to the same change for the same goal, add the new source to it instead of creating another.

  • Link to its evidence: the signals, findings and UX metrics that inform it.

  • Link to its business goal, its initiative and its source input.

  • Link to each affected workflow, creating a Workflow record for each function that changes.

  • Link to the outcomes it produces once user, product and business outcomes are measured, and to any watch items or risks it raises.

When to store and when to ask

  • Store and add to the review digest every time, because bets are high-stakes.

  • Mark it urgent in the digest when it has no evidence, no named workflows, no metric, or when it contradicts an open test.

When to flag

  • A bet has no evidence behind it

  • A bet's workflows weren't named

  • A bet has no metric to judge it

  • A bet went Live without being Approved

  • A bet has been Live past its measurement date with no outcomes recorded

Worked example

Input: a slide from the Q1 steering committee deck.

"Recommendation: roll the points progress bar out to all new cardholders. Goal: drive rewards adoption. Product owns the dashboard change; Marketing adds it to onboarding emails. Success = rewards redemptions. Evidence: task success 42% to 78%; A/B variant B won."

What Ray finds:

  • "Roll the points progress bar out to all new cardholders" is the change.

  • "Drive rewards adoption" maps to Drive adoption (User Experience).

  • "Product owns the dashboard change; Marketing adds it to onboarding emails" names two workflows, each stored as a Workflow record.

  • "Success = rewards redemptions" is the metric, and the task success numbers and A/B result are the evidence.

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 bet the progress bar will move Drive adoption, affecting Product and Marketing; measured by rewards redemptions.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Change</p></td><td colspan="1" rowspan="1"><p>Roll the points progress bar out to all new cardholders</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>Workflows</p></td><td colspan="1" rowspan="1"><p>Product, Marketing</p></td></tr><tr><td colspan="1" rowspan="1"><p>Metric</p></td><td colspan="1" rowspan="1"><p>Rewards redemptions</p></td></tr><tr><td colspan="1" rowspan="1"><p>Evidence</p></td><td colspan="1" rowspan="1"><p>Task success 42% to 78%; A/B test variant B won; Findings from the value test</p></td></tr><tr><td colspan="1" rowspan="1"><p>Initiative</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>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>Q1 steering committee deck, slide 7</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: change, goal, workflows and metric all stated in writing</p></td></tr></tbody></table>

Next step: added to the review digest with evidence rated Strong, and a prompt to the product lead to move it to Approved.

Edge cases

  • Workflows implied, not named. "We'll promote it everywhere" suggests Marketing but doesn't say so. Leave Workflows blank, lower confidence, and flag it for the owner to name them.

  • Bet made on a hunch. A leader commits to a change before any testing. Store it as a Bet with evidence rated None, and flag it.

  • Several changes in one bet. "Ship the progress bar and redesign the card page" is two bets. Split them so each can be judged on its own metric.

  • Bet reversed. Don't delete it. Mark it Reversed, link the decision that reversed it, and keep the outcomes for history.

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
Bet | Glare