An ask is a question the team needs to resolve. It's how work enters Glare, and anyone, from design, product, marketing, engineering or leadership, can raise one.
For example, after the VP of Cards asks for more early spending, the product lead asks: should we redesign the rewards dashboard for new cardholders to drive adoption? That question is the ask. It doesn't assume the answer; it names what needs deciding.
Why it matters
When asks aren't captured, requests arrive as finished solutions. Someone says "build a new dashboard", and the team starts building before anyone checks whether the problem is real or worth solving.
Writing the ask down as a question keeps the team honest. It ties the work to a business goal, makes it clear who it's for, and lets the team route it to the right kind of decision: research, new concepts, improvement or investment.
Capture the question in plain words, check which business goal it serves, and route it to the stage that should answer it.
How we write one
Every ask is written as one question that names the action, who it's for, and the goal:
Should we take an action for an audience to reach a goal?
Should we redesign the rewards dashboard for new cardholders to drive adoption?
Framing it as a question keeps the answer open, and naming the goal makes it easy to check whether the ask still matters when priorities change.
How it differs from similar ideas
-
Business intent is what the business wants. An ask is a specific question that intent makes worth answering.
-
A hunch is a belief about what's true. An ask is a question that still needs an answer.
-
A test question is asked of participants inside a test. An ask is asked of the team and decides what work happens.
-
A decision is the answer. An ask is the question it resolves.
A good ask
-
Is phrased as a question
-
Says who it's for
-
Names the goal it serves
-
Leaves the answer open
-
Connects to one business goal
-
Has someone who raised it and someone who will answer it
What happens to it
-
Raised. Someone voices it, or Ray finds it in a meeting note, email or request.
-
Restated. Ray rewrites it as a situation to explore, so the team sees the problem behind the request.
-
Routed. It's sent to one of the four stage questions: Define, Measure, Focus or Lead.
-
In progress. Work is under way to answer it.
-
Resolved or dropped. A decision answers it, or the team agrees it no longer matters and records why.
For Ray
This part tells Ray how to find asks in an input, such as a meeting transcript, a request ticket, a Slack thread, an email or a planning doc, and how to route and store them.
How to find one
-
Mark open questions and requests. Read the input and mark every question, request or "we should" that calls for a decision.
-
Turn requests into questions. If the request names a solution, such as "build a new dashboard", rewrite it as "Should we..." and note the solution as a possible Concept.
-
Find who and why. Identify the audience it's for and the goal it aims at. If no goal is given, leave it blank.
-
Restate it as a situation. Describe the situation the ask points to, such as "new cardholders rarely open the rewards tab", and check whether that situation is already stored.
-
Route it to a stage. Pick the decision question it needs answered: Are there new situations? (Define), Does the situation require new concepts? (Measure), Can the situation be improved? (Focus), or Is the situation worth improving? (Lead).
-
Map it to a business goal. Match it to one of the 20 business goals and link the business intent behind it, if there is one.
-
Write the sentence. Use the format: Should we [action] for [audience] to [goal]?
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Question language: "should we", "do we need to", "what if we", "is it worth"
-
Requests: "can we build", "we should", "let's look at whether"
-
Tickets, briefs and kickoff notes that open new work
-
Questions from leaders that end a message or a meeting
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>Says what the business wants, with no question</p></td><td colspan="1" rowspan="1"><p>Business Intent</p></td></tr><tr><td colspan="1" rowspan="1"><p>States a belief about why something happens</p></td><td colspan="1" rowspan="1"><p>Hunch</p></td></tr><tr><td colspan="1" rowspan="1"><p>Is a question for participants in a test</p></td><td colspan="1" rowspan="1"><p>Test question</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports a call that was already made</p></td><td colspan="1" rowspan="1"><p>Decision</p></td></tr><tr><td colspan="1" rowspan="1"><p>Is a rhetorical question with no decision behind it</p></td><td colspan="1" rowspan="1"><p>Nothing; skip it</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 ask</p></td><td colspan="1" rowspan="1"><p>Should we [action] for [audience] to [goal]?</p></td></tr><tr><td colspan="1" rowspan="1"><p>Action</p></td><td colspan="1" rowspan="1"><p>What the team is considering doing</p></td><td colspan="1" rowspan="1"><p>Short text</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>Goal</p></td><td colspan="1" rowspan="1"><p>What it aims to achieve</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>Situation</p></td><td colspan="1" rowspan="1"><p>The situation the ask points to</p></td><td colspan="1" rowspan="1"><p>Link to Situation</p></td></tr><tr><td colspan="1" rowspan="1"><p>Routed to</p></td><td colspan="1" rowspan="1"><p>The stage and decision question it needs answered</p></td><td colspan="1" rowspan="1"><p>Define, Measure, Focus, Lead</p></td></tr><tr><td colspan="1" rowspan="1"><p>Raised by</p></td><td colspan="1" rowspan="1"><p>The person or role, and their skill area</p></td><td colspan="1" rowspan="1"><p>Name or role, skill area</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>The input and exact passage</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>Raised, Restated, Routed, In progress, Resolved, Dropped</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How clearly it was asked</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
New asks start as Raised. An ask is only Resolved when a Decision is linked to it.
Scoring confidence
Confidence measures how clearly the ask was stated and how complete it is, not how urgent 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>Asked directly, with a clear action, audience and goal</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Asked directly, but the audience or goal is missing, or it was phrased as a solution</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Implied by a remark or complaint, with no clear question behind 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.
Linking
-
Check for duplicates first. If an existing ask covers the same action for the same audience, add the new source to it instead of creating another.
-
Link to the business intent that shapes it and the business goal it serves.
-
Link to the situation it points to, creating one at low confidence if none exists.
-
Link to the decision that resolves it, once one is made.
-
Note solutions. If the ask was phrased as a solution, link the Concept Ray created from it.
When to store and when to ask
-
Store automatically when confidence is high and the ask matches a business goal.
-
Add to the review digest when confidence is medium or low, when it doesn't match any business goal, or when it duplicates an ask that's already been resolved.
When to flag
-
An ask has no business goal or business intent behind it
-
An ask was raised as a solution and work started before it was restated
-
An ask has been In progress for 60 days with no decision
-
Two open asks point at the same situation with different actions
-
An ask was routed to Focus or Lead with no situation defined
Worked example
Input: a product team meeting transcript, October planning session.
Product lead: "The VP wants early spend up. I keep coming back to the rewards dashboard. New cardholders barely look at it. Should we redesign it for them so they actually start using rewards?"
What Ray finds:
-
"Should we redesign it" is the action, and "for them" refers to new cardholders, the audience.
-
"So they actually start using rewards" is the goal: Drive adoption.
-
"New cardholders barely look at it" points to a situation, which Ray links or creates.
-
"The VP wants early spend up" refers to the stored business intent, so Ray links it.
-
The situation isn't yet confirmed, so Ray routes the ask to Define: Are there new situations?
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>Should we redesign the rewards dashboard for new cardholders to drive adoption?</p></td></tr><tr><td colspan="1" rowspan="1"><p>Action</p></td><td colspan="1" rowspan="1"><p>Redesign the rewards dashboard</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Customers: new cardholders</p></td></tr><tr><td colspan="1" rowspan="1"><p>Goal</p></td><td colspan="1" rowspan="1"><p>Get new cardholders using rewards</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>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>Routed to</p></td><td colspan="1" rowspan="1"><p>Define: Are there new situations?</p></td></tr><tr><td colspan="1" rowspan="1"><p>Raised by</p></td><td colspan="1" rowspan="1"><p>Product lead, Product</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Planning session transcript, October 2026</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Routed</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: asked directly with an action, audience and goal</p></td></tr></tbody></table>
Next step: stored automatically and linked to the VP of Cards' business intent; Define work starts on the rewards tab situation.
Edge cases
-
Ask as a demand. "Build a new rewards dashboard" is a solution. Store the dashboard as a Concept and rewrite the ask as "Should we...".
-
Several asks in one. "Should we redesign the dashboard and change the points rules?" is two asks. Split them and route each one.
-
Already answered. If an ask matches one already resolved, link it to the existing decision and flag it, in case the situation has changed.
-
Wrong stage. If an ask lands in Focus but nobody has confirmed the situation, route it back to Define and note why.