Operations & ContentDecision Doc & RFC#decision#1-pager#async

Operations Decision 1-Pager · Decide Without a Meeting

Turn one operations judgment (vendor switch / process change / tool choice) into a 1-page async decision doc that saves a meeting.

Pain addressed · Ops defaults to 'call a meeting for every decision' — but 60% could ship via a well-structured 1-pager async. Without a template you can't write one.

Operations Decision 1-Pager · Decide Without a Meeting

Prompt·Advanced
Also available in 中文 →
You're my decision-doc partner. I'm an operations lead with a judgment that needs sign-off from my manager or cross-functional peers. Help me write an async-decidable 1-pager.

# Decision context
- Decision title (≤ 15 words): {decision_title}
- My preferred option + 1-2 alternatives: {options}
- My rationale + key data: {rationale_with_data}
- Approver + FYI list: {approver_and_fyi}
- Cost of no decision: {no_decision_cost}

# Structure (strict 6 sections · total ≤ 400 words)

## 1. TL;DR (40 words · first line)
"I recommend X · cost of inaction is Y · need yes/no from you by Z." If the approver only reads this line, they must be able to yes/no.

## 2. Background + trigger (60 words)
Why this decision now. 1-2 supporting datapoints only — don't dump everything.

## 3. Options table (90 words)
| Option | Cost | Time-to-impact | Risk | My take |
- Your preferred option first.
- Every option must honestly name its Risk. No "risk manageable" filler.

## 4. My recommendation + rationale (80 words)
"I recommend X because [1-2 core reasons] but I acknowledge [1 trade-off]". Honesty about your option's downside builds trust.

## 5. What the approver needs to do (40 words)
- ✅ Agree → I'll kick off by [date]
- ❌ Disagree → 30-second note on the specific objection
- ⏸ Want to discuss → comment below or 15-min sync

## 6. Cost of no decision (40 words)
"If we don't decide by [date], consequence is [ABC]." Make status quo feel costly.

# Boundaries
- Total ≤ 400 words.
- No "let's discuss soon" filler — specific dates + specific actions.
- The Risk column must be honest.

Output the 1-pager body.
Saves ~40 min per use

Open directly on your favourite AI

One click copies the prompt and opens the platform in a new tab — just paste (⌘/Ctrl + V).

Workflow · 5 steps

  1. 1

    Lock down the decision context first, especially the cost-of-no-decision — that's the section most 1-pagers omit.

  2. 2

    Run the prompt with all 5 placeholders filled. Claude or ChatGPT give the most structured output.

  3. 3

    On the first draft, audit Section 3 Risk column. Replace any 'risk manageable' filler with a specific risk + magnitude.

  4. 4

    The trade-off in Section 4 must be honestly admitted — models default to neutral phrasing, but self-criticism here builds the doc's credibility.

  5. 5

    Send via Slack / email with '24h to react yes/no/discuss; otherwise default yes'. Use emoji reactions to make replying cheap.

Verify before you ship

AI's "almost right" is the #1 pain. Tick these off so reviewers can't find the obvious holes. (Checkbox state stays local — we don't track it.)

Done 0 / 5 checks

Why this prompt works

This prompt isn't a generic “write me a Decision Doc & RFC”. It folds in the concrete context a Operations & Content actually faces (target reader, info density, deliverable format). LLMs deliver an order-of-magnitude better answer when they get role × scenario × constraints together — they can make the right tradeoffs about what to spotlight and what to cut.

When to use

Best moment: you know roughly that you need to do a Decision Doc & RFC, but you're stuck on “how do I even ask the AI?” Muscle memory has no template. Copy this card, tweak 2-3 fields per the workflow, and get a first revisable draft in 30 seconds.

Common pitfalls

  • Send without tweaking placeholders · the draft reads as default-GPT and your reviewer spots it in 3 seconds.
  • Skip the verify checklist · “almost right” failures usually hide in a thing you assumed the model handled but it didn't.
  • Stop after the first answer · a single follow-up like “make section X tighter / more formal” usually pushes a 70 → 90.

Variants & extensions

Want to use this card more aggressively? Three extensions:

  • Swap languages: both EN/ZH prompts ship in the card — use the EN version when shipping to a Western audience.
  • Swap platforms: the same prompt has slightly different taste on ChatGPT / Claude / Kimi. The recommended-platform pill marks the best fit.
  • Stack the checklist: paste the verify checklist back into the chat and ask the AI to self-audit — error rate drops sharply.
PromptDeck Pro Bundle

Want 25 more prompts like this one?

Get the full 50-card Pro deck — multi-step chains, vertical variants, lifetime updates.

  • 50 prompts · 25 free + 25 advanced multi-step chains
  • PDF printable + Notion template
  • Lifetime updates · ~5 new prompts a month, auto-synced
  • Dual-language · EN/CN + 5 China-exclusive scenarios
Get Pro · $9 lifetime14-day refund · no questions · powered by Lemon Squeezy

Related cards