Most decision write-ups fail for one reason: they bury the decision under context. By the time the reader reaches the actual call, they have skimmed away. A memo people read leads with the decision, names who decided, lists the options weighed, preserves the dissent, and ends with what changes tomorrow. The 15 prompts below cover the formats real teams reuse — from a one-page memo to an Architecture Decision Record to a vendor write-up — and each one forces the decision into sentence one.
TL;DR
- Lead with the decision in the first sentence. Context is paragraph two, never paragraph one.
- Match the format to the call: 1-pager for most, ADR for engineering, escalation memo (150 words) for execs, rollback memo when you reverse course.
- Classify reversible (two-way door) vs irreversible (one-way door) before you choose length — move fast on reversible, deliberate on irreversible.
- Always name a single human decider and a single owner per action item. “We” hides accountability.
- All 15 prompts paste into ChatGPT (GPT-5.5), Claude (Sonnet 4.6 / Opus 4.7), or Gemini 3.1 Pro. Swap the
[paste]placeholder for your raw notes.
Which AI model to use
Any current model handles these prompts well, since the job is structuring text you already provide, not reasoning from scratch. Two practical notes as of June 2026:
- Long raw notes (a full meeting transcript, a Slack thread export): Claude Sonnet 4.6 and Gemini 3.1 Pro both carry a 1M-token context window, so they swallow long inputs without truncation. ChatGPT Plus holds roughly 320 pages in-app (the full 1M window is $200 Pro only). See ChatGPT vs Claude for long documents.
- Best default: Claude Sonnet 4.6 tends to keep the “lead with the decision” instruction without drifting into marketing voice. If you want a side-by-side on tone and structure, read ChatGPT vs Claude vs Gemini.
You do not need a top-tier reasoning model for a decision memo. Save Opus 4.7 or GPT-5.5 Thinking for the pre-mortem step (below), not the formatting.
Who this is for
PMs, chiefs of staff, eng managers, founders, and ops leads who need decisions to be reviewable, searchable, and replayable for a new hire six months later.
When not to use these prompts
- Trivial choices (font color, meeting time) — the documentation overhead exceeds the value.
- Decisions that should not be written down (HR-sensitive, legal-privileged) without clearing it with the right function first.
- Anything you would be embarrassed to have screenshotted — a memo is a permanent record by design.
The six elements every decision prompt needs
A decision summary prompt should always carry these six:
- Role — who the AI plays (PM, chief of staff, ops lead, finance analyst, manager).
- Context — company / team / project / audience / what already happened.
- Goal — one concrete deliverable: memo, email, talking points, table, prioritized list.
- Constraints — what NOT to do (no marketing voice, no speculation past the facts, no PII, fit under a word count).
- Output format — numbered sections, a markdown table, Slack-friendly bullets, or a 1-page memo.
- Signal — one or two lines of “good” tone, or a previous memo to mirror.
Best for
- Documenting a leadership-call decision before it gets relitigated
- Architecture / vendor / hiring decisions that future-you must defend
- Group decisions where dissent should be on the record
- Escalation memos to a VP who has five minutes
- No-decision-yet status updates so stakeholders stop pinging
15 copy-ready prompt templates
Swap the bracketed [paste] placeholders for your own text before sending.
1. 1-pager decision memo
Default format — works for about 80% of cases.
You are a chief of staff. Below are my raw notes on a decision we just made. Produce a 1-page memo with these sections in order: (1) Decision (one sentence, lede), (2) Context in 3 sentences, (3) Options considered (table: option | pro | con), (4) Why we chose what we chose (3 bullets), (5) Who decided + who was consulted, (6) What changes by when (action items with owners + dates), (7) When we revisit. Plain language. No marketing voice.
Notes:
[paste]Variable to swap: [paste] — raw notes, transcript, or whiteboard-photo OCR.
Optimization: If the memo drifts long, add: “Hard limit: 400 words. Cut context first, never cut the decision or action items.”
2. ADR-format decision (engineering)
Follows the MADR (Markdown Any Decision Records) structure that names the rejected options instead of leaving the loser anonymous.
Write an Architecture Decision Record (ADR) for the decision below. Use the standard sections: Title, Status (Proposed / Accepted / Superseded), Context, Decision, Consequences (positive + negative + neutral), Alternatives considered (with one-line pros and cons each). End with a "Reversibility" line: easy / costly / one-way door.
Decision context: [paste]Variable to swap: [paste] — the technical decision (e.g., “Postgres vs Mongo for the events table”).
3. Options pros-cons table
Use when the decision is not yet made and you need stakeholders to compare.
I am evaluating [N] options for [goal]. Build a comparison table with columns: Option | Cost | Time-to-value | Risk | Reversibility | Strategic fit | Recommendation strength (1-5). Then write 3 sentences below the table: top pick, runner-up, what would change my mind.
Options and notes:
[paste]4. RACI decision summary
RACI assigns exactly one Accountable per call — that single owner is the whole point of the format.
Below is a decision write-up. Append a RACI block that names: Responsible (does the work), Accountable (final call — exactly one name), Consulted (two-way input before the decision), Informed (told after, one-way). Use one name per slot — no "the team". If a slot is empty, write "TBD" and flag it.
[paste]5. Time-boxed decision
When perfect data will never arrive and you decided anyway.
Frame this as a TIME-BOXED decision. Sections: (1) The decision, (2) Why now (the deadline / forcing function), (3) What we knew vs what we did not know, (4) Confidence level (low / medium / high) and why, (5) Re-evaluation trigger (specific signal or date). End with: "If we wait, the cost is X."
Context: [paste]6. Group decision sync writeup
Below is a transcript / notes from a group sync where a decision was reached. Write the sync writeup: (1) Decision in one sentence, (2) Who was in the room (names + roles), (3) Path to the decision (3-5 bullets — how the group converged), (4) Dissenting views captured by speaker, (5) Action items + owners + dates, (6) What was explicitly out of scope.
[paste]7. Reversible vs irreversible framing
Borrowed from the two-way-door / one-way-door framing: reversible calls get made fast at roughly 70% certainty; irreversible calls get the slow, deliberate treatment.
Classify the decision below as reversible (two-way door) or irreversible (one-way door). Then write the memo accordingly: (a) For reversible — short, bias to action, name the rollback path, accept ~70% certainty. (b) For irreversible — longer, name the disconfirming evidence we looked for, name who has veto, name the pre-mortem we ran. Be explicit about which mode you chose and why.
[paste]8. Decision with dissent captured
Use when one or more stakeholders disagreed.
Write a decision memo that explicitly preserves dissent. Sections: (1) Decision, (2) Majority rationale, (3) Dissent block — name(s), their argument in their own voice (steelman it, do not strawman), what evidence would change the decision, (4) Why we proceeded anyway, (5) Commitment to revisit (specific date or metric trigger).
Notes: [paste]9. Decision based on data
Below are the data / analysis underpinning a decision. Write the memo with: (1) Decision, (2) Key data point(s) cited with source + date, (3) What the data does NOT cover (limitations), (4) The judgment call layered on top of the data, (5) Reproducibility — where the analysis lives so anyone can re-run it. Avoid the trap of "the data decided" — name the human who decided.
Data and notes: [paste]10. Decision under uncertainty
This decision is being made with high uncertainty. Write a memo that names the uncertainty explicitly: (1) Decision, (2) Known unknowns — list them, (3) Unknown unknowns — what we cannot even ask yet, (4) Bet size — what we are risking, (5) Kill criteria — specific signals that would reverse the decision, (6) Next info checkpoint (date / event).
Context: [paste]11. Escalation decision memo
For sending UP to a VP / exec who has five minutes.
Write an escalation memo to [VP role] who has 5 minutes. Structure: (1) TL;DR (the ask, in one sentence — escalate / approve / break tie), (2) What I tried (2 bullets), (3) What I need (decision, resources, air cover), (4) Cost of inaction (one sentence). Hard limit: 150 words.
[paste]Variables to swap: [VP role] — e.g., “VP Engineering”, “CFO”; [paste] — situation summary.
12. No-decision-yet status update
No decision has been made yet, but stakeholders are pinging. Write a holding-pattern update: (1) Where we are in the process, (2) What is blocking the call (data, alignment, missing input), (3) Who owns unblocking each item with dates, (4) When the next decision checkpoint is. Tone: confident, not defensive. Do NOT fake a decision.
Context: [paste]13. Decision rollback memo
When you have to reverse a previous call.
We are reversing a previous decision. Write the rollback memo: (1) What we decided previously (link to old memo), (2) What we now know that we did not know then, (3) The new decision, (4) What changes operationally (who unwinds what by when), (5) Acknowledgment of cost / wasted work without blame, (6) What we will do differently next time. No corporate-speak.
[paste]14. Vendor-selection decision
Write a vendor-selection decision memo. Sections: (1) Vendor chosen + contract size + term, (2) Requirements we evaluated against (scored table: vendor | req1 | req2 | ... | total), (3) Why the runner-up lost (specific, not "less aligned"), (4) Risks of the chosen vendor (3 bullets) + our mitigations, (5) Exit ramp — how we get out if it goes wrong, (6) Owner of the relationship.
Notes: [paste]15. Hiring decision summary
For closing out a loop — yes or no.
Write a hiring decision summary for the candidate below. Sections: (1) Decision (hire / no hire / hold), (2) Role + level + compensation band, (3) Strengths (3 evidence-backed bullets — cite the interviewer who saw it), (4) Concerns + how we will mitigate post-hire (or why they are blocking), (5) Dissenting interviewer (if any) — their argument verbatim, (6) Onboarding owner + first-30-day expectation. Treat this as a record future managers will read.
Loop notes: [paste]Pick the right format
| Situation | Use template | Target length |
|---|---|---|
| Standard team call | 1-pager (#1) | ~400 words |
| Technical / architecture call | ADR (#2) | Half a page |
| Decision not made yet | Options table (#3) | Table + 3 lines |
| Unclear who owns it | RACI (#4) | Append to any memo |
| Sending up to an exec | Escalation (#11) | 150 words |
| Reversing a past call | Rollback (#13) | 1 page |
| Choosing a vendor | Vendor (#14) | 1 page |
Common mistakes
- Burying the decision in paragraph four — readers bail before they reach it.
- No owner on action items — “we” will do it means nobody will.
- Hiding dissent — looks tidy now, becomes a credibility tax later.
- Pretending the decision was data-driven when a human judged — own the judgment.
- Skipping the “when we revisit” line — turns decisions into ratchets that can’t be undone.
- Writing one memo for both technical and exec audiences — they need different cuts.
- Treating reversible decisions like irreversible ones — slows the team for no reason.
How to push results further
- Lead with the decision. Always. Context is paragraph two, never paragraph one.
- Name the human who decided, even if the data was strong. “We” hides accountability.
- For irreversible calls, run a pre-mortem prompt first: “Imagine this decision failed badly 12 months from now. List the five most likely causes.” This is the one step worth a top-tier model (Opus 4.7 or GPT-5.5 Thinking).
- Keep dissent in the memo, not in a separate doc — separation becomes erasure over time.
- Add a revisit trigger — a specific metric or date — so the decision is not permanent by default.
- Store every memo in one searchable place (a Notion database, a
/docs/decisions/folder, or an ADR directory). Untagged decisions disappear. - After 90 days, run a follow-up prompt: “Score this decision against its stated outcome.” It builds calibration over time.
FAQ
- How long should a decision memo be?: Default to one page. For ADRs, half a page is fine. For escalation memos, 150 words. If you need more than two pages, you are mixing decision and analysis — split them.
- Should I share the memo before or after the decision?: Before, if you want input. After, if it is already communicated. State which mode in the subject line so readers know whether to push back.
- What if the decision was made informally in Slack?: Write the memo anyway, after the fact. Slack threads are not searchable archives, and a decision without a memo gets relitigated within six months.
- Do I need a memo for every decision?: No. Use this filter: would a new hire six months from now need to know why? If yes, memo. If not, skip.
- How do I get people to actually read it?: Decision in sentence one. Action items at the bottom with names attached. Post the memo in Slack with a one-sentence TL;DR, so anyone scrolling past still gets the punchline.
- What if the decision changes the next day?: Add a “Superseded by” header to the original pointing to the new memo. Do not delete it — the trail of reversals is valuable.
- Which AI model writes the cleanest memo?: For pasting in long raw notes, Claude Sonnet 4.6 or Gemini 3.1 Pro (1M-token context as of June 2026). For a quick 1-pager, any current model is fine. Save Opus 4.7 or GPT-5.5 Thinking for the pre-mortem.
Related
- Meeting notes prompts
- Action item extraction prompts
- Executive summary prompts
- Project planning prompts
- Cross-team Alignment Memo Prompts to Avoid Meetings
- Policy Summary Prompts for One-Page Internal Policies
- Write the A/B Test Summary With AI
- AI Executive Summary for Management Reporting: 12 Slides Into 4 Bullets
- How to Compress Market Research Into a One-Page Brief With AI
- Productivity & Office Prompts hub
Tags: #Prompt #Productivity #Decision #Memo