Decision Summary Prompts: 15 Templates for Memos People Actually Read

Decision memo prompts — 1-pager, ADR-format, options table, RACI summary, reversible vs irreversible, escalation, rollback. Make decisions findable and replayable.

Published: May 18, 2026 Author: AI Productivity Guide Team 🌐 查看中文版本

Most decision write-ups fail because they bury the decision under context. A good decision summary leads with the decision, names who decided, lists the options considered, captures dissent, and ends with what changes tomorrow. These 15 templates cover the formats real teams reuse — from one-pager memos to ADRs to vendor selection write-ups.

Who this is for

PMs, chiefs of staff, eng managers, founders, and ops leads who need to make decisions reviewable, searchable, and replayable for new hires six months later.

When not to use these prompts

Don’t use these for trivial choices (font color, meeting time) — overhead exceeds value. Also avoid for decisions that should NOT be documented (HR-sensitive, legal-privileged) without checking with the right function first.

Prompt anatomy / structure formula

A decision summary prompt should always carry six elements:

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 facts, no PII, fit under word count).
Output format: numbered sections, markdown table, slack-friendly bullets, or 1-page memo.
Examples / signal: 1-2 lines of “good” tone, or a previous example 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 captured
Escalation memos to a VP who has 5 minutes
No-decision-yet status updates so stakeholders stop pinging

15 copy-ready prompt templates

Default format — works for 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}

Variables to swap: paste — raw notes, transcript, or whiteboard photo OCR

Optimization: If memo drifts long, add: “Hard limit: 400 words. Cut context first, never cut the decision or action items.”

2. ADR-format decision (engineering)

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. End with a "Reversibility" line: easy / costly / one-way door.

Decision context: {paste}

Variables to swap: paste — the technical decision (e.g., “Postgres vs Mongo for 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

Below is a decision write-up. Append a RACI block that names: Responsible (drives execution), Accountable (final call), Consulted (gave input before decision), Informed (told after). 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 won’t come 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

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. (b) For irreversible — long, 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 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. 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 5 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}

Common mistakes

Burying the decision in paragraph 4 — 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 — audiences 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 2, never paragraph 1.
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 fails. What killed it?”
Keep dissent in the memo, not in a separate doc — separation = erasure over time.
Add a “revisit trigger” — a specific metric or date — so the decision is not permanent by default.
Save decision memos in one searchable place (Notion DB, /docs/decisions/, ADR folder). Untagged decisions disappear.
After 90 days, run a follow-up prompt: “Score this decision against its stated outcome.” Builds calibration.

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 communicated. Be explicit about 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, post-hoc. Slack threads are not searchable archives. Decisions without a memo will be relitigated within 6 months.
Do I need a memo for every decision?: No. Use this filter: would a new hire 6 months from now need to know why? If yes, memo. If not, skip.
How do I get people to actually read it?: Sentence-1 decision. Action items at the bottom with their names. Slack post linking the memo with the one-sentence TL;DR. Anyone scrolling past gets the punchline.
What if the decision changes the next day?: Update the original memo with a “Superseded by” header pointing to the new one. Do not delete. The trail of reversals is valuable.

Tags: #Prompt #Productivity #Decision #Memo