Write a Decision-Ready Research Update
The conversation provided a structured format for transforming scattered research notes into a concise update for decision-makers, emphasizing a clear recommendation, verified facts, uncertainties, options, and a specific next piece of evid
A read-only, creator-approved conversation screened before publication.
Show me how to turn scattered research notes into a short update for a decision-maker. Provide a structure that separates facts, uncertainty, options, recommendation, and the next piece of evidence that would change the conclusion.
Here's a compact structure for that update. Keep the whole thing under one page; a decision-maker wants the bottom line fast. 1. BOTTOM LINE (2-3 sentences) State the recommendation up front. What do you want them to decide, and by when? This is thethe only part most people will read. 2. FACTS (what we know) Only verified items, each with with a source or date. Bullet list. If a fact came from a single weak source, say so here. - Fact A (source, date) - Fact B (source, date) 3. UNCERTAINTY (what we don't know) Ranked by how much it would change the decision. Name the gap, not just "we need more research." - Unknown 1: how it matters - Unknown 2: how it matters 4. OPTIONS (2-3, never more) For each: what it is, rough cost/effort, upside, downside. One line each. If an option is a no-go, kill it here with a reason. 5. RECOMMENDATION Pick one option and give the single strongest reason. Tie it to a goal the decision-maker already cares about, not to your own preference. 6. NEXT EVIDENCE THAT WOULD CHANGE THE CONCLUSION One specific piece of evidence, and the threshold that flips the call. This is the key part: it tells them what to watch for and when to revisit. Example: "If the vendor's pilot data shows <15% churn by Sept 1, switch to Option B. Otherwise proceed with A." Formatting tips: - Use the inverted pyramid: recommendation first, supporting detail after. - Put a date on the update so it's clear how fresh it is. - If anything changed since the last update, flag it with "CHANGED:" so they don't re-read old material. - End with one explicit ask: "Approve A by Friday" or "Tell me which option to pursue." The "next evidence" line is what separates a good update from a status report — it converts your uncertainty into a decision trigger instead of just listing gaps.
RELATED SIGNALS
Project Brief Template for Unstructured Ideas
The conversation produced a template for turning unstructured ideas into concise project briefs, including sections for problem, audience, d
READ TRANSMISSION →
SQLite vs PostgreSQL for Growing Web Apps: Decision Criteria and Switching Signa
The response compares SQLite and PostgreSQL for a single-server web application, providing decision criteria and signals for switching, whic
READ TRANSMISSION →
Capabilities of MU/TH/UR AI System
The conversation outlines the capabilities of the MU/TH/UR AI system, including file and code work, terminal and system operations, research
READ TRANSMISSION →