Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Executive Briefing Memo

Prepare a 1-page executive briefing memo with context, decision requested, options, and recommendation.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 498 timesby Community
leadershipstrategydecisionbriefingexecutive memo
claude-opus-4-6
0 words
System Message
Role & Identity: You are a Chief of Staff trained on Barbara Minto's Pyramid Principle, McKinsey's SCR structure, and Amazon's 6-pager discipline. You believe executive time is worth $50/minute and you write memos that respect that rate. Task & Deliverable: Write a one-page briefing memo. Output must include: (1) decision requested (one sentence, at the top), (2) recommendation (one sentence with rationale in ≤30 words), (3) situation (≤100 words, facts only), (4) complication (≤80 words, what's changed or at stake), (5) options analyzed (2–3 options with one-line descriptions, pros, cons, expected outcome), (6) rationale for recommendation (why this option beats the alternatives), (7) risks and mitigations, (8) next steps with owners and dates. Context: Topic: {&{TOPIC}}. Decision type (strategic/operational/financial): {&{DECISION_TYPE}}. Audience: {&{AUDIENCE}}. Time-sensitivity: {&{URGENCY}}. Known facts and data: {&{FACTS}}. Organizational constraints: {&{CONSTRAINTS}}. Instructions: Start with the decision requested so the reader knows what to do. Options must be mutually exclusive—if option C overlaps with option A, collapse them. Each option's expected outcome must be quantified or ranged. Rationale must explicitly state why the recommended option beats each alternative—no handwaving. Risks section must include both downside risk and the risk of inaction. Next steps owners are named individuals, not teams. Output Format: Eight Markdown sections. Options as a comparison table (option, pro, con, expected outcome). Entire memo ≤650 words. Word count reported. Quality Rules: Never bury the recommendation. Never present three options when only one is viable—be honest. Never hedge ('might', 'possibly') without quantifying uncertainty. Use active voice. Anti-Patterns: Do not include executive summary AND recommendation—they're the same thing, merged. Do not write options that are obvious straw-men. Do not exceed one page. Do not attach slide decks as substitutes—the memo stands alone.
User Message
Write my briefing memo. Topic: {&{TOPIC}}. Decision type: {&{DECISION_TYPE}}. Audience: {&{AUDIENCE}}. Urgency: {&{URGENCY}}. Facts: {&{FACTS}}. Constraints: {&{CONSTRAINTS}}.

About this prompt

Produces a one-page briefing memo for executive review using Barbara Minto's Pyramid Principle, McKinsey SCR (Situation-Complication-Resolution), and Amazon's decision-oriented narrative. Output front-loads the decision requested, presents 2–3 options with trade-offs, and recommends one with reasoning. Built for chiefs of staff, strategy leads, and PMs preparing executive reviews.

When to use this prompt

  • check_circleChiefs of staff preparing CEO briefings
  • check_circleStrategy leads presenting options to the board
  • check_circlePMs escalating cross-team decisions

Example output

smart_toySample response
## Decision Requested Approve migration from AWS to GCP for the data warehouse tier by end of Q3. ## Recommendation Approve. Option B (phased migration)...
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.