Writing quick-ask prompts

A Brief can hold dozens of sources but only four quick asks. Those four slots should cover the four moments a recipient is likely to be in when they open the link. The constraint forces you to choose what matters most.

• Orientation — 'Give me the two-minute version.' For the reader with no context who needs to catch up before a meeting.
• Action — 'What happens next, and who owns it?' For the reader who has to do something today and needs clarity on ownership.
• Verification — 'Show me the evidence for the key numbers.' For the skeptic, the auditor, or the person who will be asked to defend the claim.
• Risk — 'What remains open or unresolved?' For the reader who will be blamed if something goes wrong and needs to know where the landmines are.

Every Brief has its own balance. A board update may weight verification more heavily. A deal handoff may weight risk more heavily. A project transition may weight action more heavily. The four jobs stay the same; the emphasis shifts based on what the recipient is trying to do.

Prompts that read like search queries get ignored. Prompts that read like a colleague leaning over your desk get used. 'What's the current price and has it changed?' beats 'Pricing summary.' 'Who has not replied and what are they blocking?' beats 'Stakeholder status.' The difference is specificity and voice.

Use the language of the team, not the language of the template. If the sales team says 'close plan,' use 'close plan.' If engineering says 'blocker,' use 'blocker.' If the finance team says 'accrual,' use 'accrual.' Familiar phrasing lowers friction and makes the prompt feel like it came from someone who understands the work.

Avoid prompts that are too broad to answer well. 'Tell me everything' is not a quick ask; it is a request for a different document. 'What should I know before Friday?' is better because it has a decision and a deadline built in.

After a Brief has been open for a week, look at which quick ask gets used and which typed question keeps repeating. Promote the repeated question into a quick ask and retire the one nobody clicks. This turns the Brief into a learning system.

This is why Brieflin tracks quick-ask usage. The data tells you what your recipients actually care about, which is often different from what you assumed they would care about. A prompt you thought was essential may go unused, while a question you considered obscure may be asked constantly.

The same four jobs show up differently in different contexts. Here are concrete examples for common Brief types.

• Board update: What changed this month? Are we on plan for cash? What is the biggest risk to the plan? What do you need from the board?
• Deal handoff: What is committed in writing? What has slipped? Who has not replied? What would kill this deal this month?
• Project transition: What is the next milestone? What is blocked? Where is the budget vs. plan? What decisions are pending?
• New hire onboarding: What should I do first this week? Who do I meet and why? What do these acronyms mean? What is the team worried about right now?

Use these as starting points, not final answers. The best quick asks are tuned to the specific recipient and the specific decision they need to make. A prompt that works for one board may be irrelevant for another.

• It asks for something the sources do not contain. The recipient gets a weak answer and loses trust.
• It uses jargon the recipient does not know. They will not click it.
• It overlaps with another prompt. Two similar questions split the usage data and confuse the reader.
• It is too polite to be useful. 'Could you possibly summarize?' is weaker than 'Give me the two-minute version.'
• It is written for the author, not the recipient. A prompt that shows off how much the author knows is usually less useful than one that helps the recipient decide.

A failed prompt is not a failure of the reader. It is a mismatch between what was asked and what the reader needed. The fix is almost always to observe the recipient more closely and rewrite the prompt in their language, for their moment, toward their decision.

A quick ask is not a feature; it is a shortcut to a decision. Before writing a prompt, picture the recipient in their actual environment. Are they on a phone in a cab? In a boardroom with five minutes before the meeting? At their desk trying to clear a backlog? The prompt should match the moment.

For mobile readers, prompts should produce short, scannable answers. For auditors, prompts should point to sources. For executives, prompts should surface tradeoffs. For operators, prompts should produce next actions. One Brief can serve all of them if the prompts are chosen with their jobs in mind.

Treat your first four prompts as a hypothesis. After the Brief has been used, replace the weakest one with the most common free-form question. Over time, your Briefs will become more useful because they are shaped by real behavior rather than best guesses.

Make iteration a habit, not a one-time event. Set a calendar reminder to review the quick asks on every Brief that has been active for more than a month. The five minutes you spend tuning prompts will save each recipient far more time than that.

Document the changes you make and why. A prompt that was retired for one Brief may be perfect for another. A shared prompt library, even an informal one, helps the whole team write better quick asks without reinventing the wheel each time.

The most effective teams review prompt performance as a group. A ten-minute monthly review of which quick asks were used, ignored, or repeated surfaces patterns no individual author would see. Those patterns become the team's shared standard for what makes a prompt useful.

Open an example Brief and ask it the questions from this guide, or create your own Brief in a few minutes.