Prompts for Executive Communication

32 ready-to-use ChatGPT prompts for executive communication. Fill in the bracketed fields, paste into ChatGPT, and go.

Writing · 32 prompts

01

Draft a Board Memo from Raw Notes and Business Inputs

Create a board memo that turns raw notes into a clear decision narrative, supporting evidence, and open questions.

You’ll needraw notesdecision or update topicboard audience contextsupporting dataknown risksdesired outcome
Prompt
You are drafting a board memo for a leadership team.

Use the context below.

Context:
- Raw notes, bullets, or source material: [notes]
- Decision, update, or topic: [topic]
- Board audience or context: [audience]
- Supporting data or evidence: [data]
- Known risks, objections, or tensions: [risks]
- Desired outcome from the board: [outcome]

Instructions:
1. Organize the memo around the decision or strategic point, not around the order of the notes.
2. Clarify the situation, recommendation, evidence, and implications.
3. Surface tradeoffs, open questions, and risks honestly.
4. Avoid startup vagueness, filler, and overclaiming.
5. Make the memo readable for a time-constrained board audience.

Output format:
- Executive summary
- Situation and context
- Recommendation or key point
- Supporting evidence
- Risks and open questions
- Requested decision or response

Missing information policy:
Ask up to 2 concise questions only if the topic or desired outcome is unclear. Otherwise proceed with explicit assumptions.

Quality bar:
- Clear strategic logic.
- Board-appropriate tone.
- Honest treatment of tradeoffs.
02

Turn Meeting Notes into a Clear Follow-Up Memo

Rewrite meeting notes into a follow-up memo that captures decisions, owners, next steps, and unresolved issues.

You’ll needmeeting notesaudiencepurpose of follow-upknown decisionsopen questionstone
Prompt
You are rewriting internal meeting notes into a follow-up memo.

Use the context below.

Context:
- Meeting notes or transcript excerpt: [notes]
- Audience for the memo: [audience]
- Purpose of the follow-up: [purpose]
- Known decisions already made: [decisions]
- Open questions or unresolved issues: [questions]
- Tone guidance: [tone]

Instructions:
1. Extract the real decisions, actions, and implications from the notes.
2. Remove repetition, side tangents, and low-value transcript residue.
3. Make ownership and deadlines explicit where possible.
4. Separate confirmed decisions from unresolved issues.
5. Keep the memo useful for people who did not attend the meeting.

Output format:
- Purpose of the memo
- Key decisions
- Action items by owner
- Open questions or blockers
- Next check-in or follow-up needs

Missing information policy:
Ask first only if the notes or memo audience are unclear.

Quality bar:
- Distinguish decisions from discussion.
- Make follow-up obvious.
- Useful to non-attendees.
03

Write a Weekly Executive Update Without Status-Report Bloat

Write a weekly executive update with progress, risks, decisions, and asks in a concise leadership-ready format.

You’ll needweekly updates or notesaudiencetop goalswinsrisksasks or decisions neededtone
Prompt
You are writing a weekly executive update for a leadership audience.

Use the context below.

Context:
- Weekly updates, notes, or source material: [updates]
- Audience: [audience]
- Top goals or priorities this week: [goals]
- Wins or progress worth noting: [wins]
- Risks, blockers, or misses: [risks]
- Asks, decisions, or support needed: [asks]
- Tone guidance: [tone]

Instructions:
1. Prioritize what leadership needs to know, not everything that happened.
2. Distinguish progress, risk, and required action clearly.
3. Avoid status-report filler and overly optimistic gloss.
4. Make the update scannable while still giving enough context for decisions.
5. End with clear asks, decisions, or watch items if applicable.

Output format:
- Weekly summary
- Progress against priorities
- Risks or blockers
- Decisions, asks, or support needed
- Watch next week

Missing information policy:
Proceed with assumptions unless the audience or top goals are unclear.

Quality bar:
- High signal.
- Clear implications.
- Leadership-ready brevity.
04

Draft a Leadership Decision Memo from Incomplete Inputs

Draft a leadership decision memo with recommendation, tradeoffs, assumptions, and questions from incomplete inputs.

You’ll needdecision topicknown factsoptionsconstraintsstakeholdersdesired outcome
Prompt
You are drafting a leadership decision memo.

Use the context below.

Context:
- Decision topic: [topic]
- Known facts or source inputs: [facts]
- Options under consideration: [options]
- Constraints, risks, or limits: [constraints]
- Stakeholders involved: [stakeholders]
- Desired outcome: [outcome]

Instructions:
1. Organize the memo around the actual decision, not the order of the notes.
2. State the leading recommendation and the assumptions behind it.
3. Compare the options honestly, including tradeoffs and uncertainty.
4. Flag what is still unknown without making the memo evasive.
5. Keep the writing sharp enough for a busy leadership reader.

Output format:
- Executive summary
- Decision to make
- Recommendation
- Tradeoffs and assumptions
- Open questions

Missing information policy:
Proceed with explicit assumptions unless the decision topic or desired outcome is unclear.

Quality bar:
- Clear recommendation.
- Honest uncertainty.
- Leadership-ready structure.
05

Tighten a Board Update Without Hiding the Risk

Tighten a board update while preserving real risk, open questions, and strategic clarity.

You’ll needcurrent board updateboard audience contextmain messagerisks to preservetonerequested outcome
Prompt
You are tightening a board update for clarity and candor.

Use the context below.

Context:
- Current board update draft: [draft]
- Board audience context: [audience]
- Main message or update theme: [message]
- Risks or concerns that must remain visible: [risks]
- Tone guidance: [tone]
- Requested outcome or takeaway: [outcome]

Instructions:
1. Tighten the writing so the main point lands faster.
2. Remove filler, repetition, and vague status language.
3. Preserve the real risk and any unresolved issues.
4. Keep the tone composed and credible, not defensive.
5. Make the final version easier for a board reader to scan.

Output format:
- Main problems with the current draft
- Rewritten board update
- Notes on preserved risks or caveats

Missing information policy:
Ask first only if the draft or board audience context is missing.

Quality bar:
- Faster clarity.
- No risk laundering.
- Board-appropriate tone.
06

Create a Leadership Pre-Read from Notes, Threads, and Fragments

Create a leadership pre-read from notes, threads, and fragments with context, options, and questions.

You’ll needsource notes or threadstopicmeeting or decision contextstakeholdersopen questionsrecommended outcome
Prompt
You are preparing a leadership pre-read from fragmented source material.

Use the context below.

Context:
- Source notes, threads, or fragments: [notes]
- Topic or issue: [topic]
- Meeting or decision context: [context]
- Stakeholders involved: [stakeholders]
- Open questions: [questions]
- Recommended outcome if any: [outcome]

Instructions:
1. Consolidate the fragmented material into a coherent pre-read.
2. Separate background context from the decision or discussion that matters now.
3. Surface the most important questions, risks, and tradeoffs.
4. Keep the document concise enough to be read before the meeting.
5. Make the next conversation easier, not broader.

Output format:
- Topic summary
- Context and current state
- Key questions or tradeoffs
- Recommendation or discussion path
- What readers should come prepared to decide

Missing information policy:
Proceed with assumptions unless the topic or meeting context is unclear.

Quality bar:
- Coherent from fragmented inputs.
- Decision-useful.
- Concise enough to get read.
07

Turn 1:1 Notes into a Coaching Summary

Turn 1:1 notes into a coaching summary that captures themes, support needs, and next actions.

You’ll need1:1 notesperson or rolemain themessupport concernsfollow-up goalstone
Prompt
You are rewriting 1:1 notes into a coaching summary.

Use the context below.

Context:
- 1:1 notes or transcript excerpts: [notes]
- Person or role discussed: [person]
- Main themes or recurring topics: [themes]
- Support concerns or tensions: [concerns]
- Follow-up goals: [goals]
- Tone guidance: [tone]

Instructions:
1. Extract the meaningful patterns from the notes rather than repeating every detail.
2. Clarify what the person needs, what should be followed up, and what may require coaching.
3. Separate factual recap from interpretation or pattern recognition.
4. Keep the summary useful for the next manager or coach interaction.
5. Preserve nuance without turning the output into a transcript.

Output format:
- Coaching summary
- Key themes
- Support or risk areas
- Follow-up actions
- Questions to revisit next time

Missing information policy:
Ask first only if the notes or coaching context are missing.

Quality bar:
- Pattern-based synthesis.
- Useful follow-up.
- Less transcript residue.
08

Write an Executive Approval Request That Is Easy to Decision

Write an executive approval request with context, rationale, tradeoffs, and a clean decision ask.

You’ll needapproval topicbusiness contextproposed actiontradeoffsdeadlinedecision maker
Prompt
You are writing an executive approval request.

Use the context below.

Context:
- Approval topic: [topic]
- Business context: [context]
- Proposed action or request: [action]
- Tradeoffs, costs, or implications: [tradeoffs]
- Deadline or timing pressure: [deadline]
- Decision maker or audience: [decision maker]

Instructions:
1. Make the ask explicit early.
2. Include only the context needed to support the decision.
3. Clarify tradeoffs, implications, and urgency without sounding dramatic.
4. Reduce ambiguity that would cause delay or extra questions.
5. Keep the writing crisp and easy to scan.

Output format:
- Decision ask
- Why this matters now
- Key tradeoffs or implications
- Deadline or timing note
- Recommended decision framing

Missing information policy:
Proceed with assumptions unless the approval topic or decision maker is unclear.

Quality bar:
- Easy to decide from.
- Minimal back-and-forth.
- Honest tradeoff framing.
09

Write a Risk Update Memo Without Status-Report Filler

Write a risk update memo that explains the issue, trajectory, mitigation, and leadership implications clearly.

You’ll needrisk topiccurrent statetrajectorymitigation workunknownsaudience
Prompt
You are writing a risk update memo for a leadership audience.

Use the context below.

Context:
- Risk topic or issue: [risk topic]
- Current state: [current state]
- Trajectory or recent movement: [trajectory]
- Mitigation work underway: [mitigation]
- Unknowns or unresolved questions: [unknowns]
- Audience: [audience]

Instructions:
1. State the risk clearly and early.
2. Explain how the situation is evolving and what matters most right now.
3. Describe mitigation progress without pretending the risk is solved if it is not.
4. Flag what leadership should watch, decide, or support.
5. Avoid generic status-report filler.

Output format:
- Risk summary
- Current trajectory
- Mitigation status
- Unknowns or watch items
- Leadership implications or asks

Missing information policy:
Proceed with assumptions unless the risk topic or current state is unclear.

Quality bar:
- Clear risk statement.
- Honest trajectory.
- Useful leadership implications.
10

Create a Strategy Offsite Summary That Clarifies Real Decisions

Create a strategy offsite summary that captures real decisions, unresolved tensions, and next steps.

You’ll needoffsite notesparticipantsmajor themesdecisions madeunresolved issuesnext-quarter context
Prompt
You are summarizing a strategy offsite for a leadership audience.

Use the context below.

Context:
- Offsite notes or source material: [notes]
- Participants: [participants]
- Major themes discussed: [themes]
- Decisions made: [decisions]
- Unresolved issues or tensions: [issues]
- Next-quarter or forward-looking context: [next quarter]

Instructions:
1. Capture the real strategic movement from the offsite, not just the agenda topics.
2. Separate decisions, open questions, and themes worth carrying forward.
3. Clarify where alignment improved and where ambiguity remains.
4. Make the summary useful for follow-through after the offsite ends.
5. Keep the write-up concise and leadership-ready.

Output format:
- Offsite summary
- Decisions made
- Open tensions or unresolved issues
- Next-step priorities
- What needs follow-through

Missing information policy:
Proceed with assumptions unless the offsite notes or leadership context are unclear.

Quality bar:
- Real decisions visible.
- Clear follow-through.
- Less retreat-summary fluff.
11

Write a Staff-Level Update Memo from Department Inputs

Write a staff-level update memo from department inputs with movement, friction, and leadership implications.

You’ll needdepartment updatesshared company prioritiescurrent risksleadership audienceopen decisionstone
Prompt
You are writing a staff-level update memo from department inputs.

Use the context below.

Context:
- Department updates or source notes: [updates]
- Shared company priorities: [priorities]
- Current risks, misses, or tensions: [risks]
- Leadership audience: [audience]
- Open decisions or support needed: [decisions]
- Tone guidance: [tone]

Instructions:
1. Consolidate the inputs into a memo that leadership can actually use.
2. Focus on what changed, what matters, and what needs support or attention.
3. Avoid stacking disconnected status blurbs.
4. Surface cross-functional implications where they matter.
5. Keep the memo concise and scan-friendly.

Output format:
- Staff update summary
- Progress against priorities
- Risks or tensions
- Cross-functional implications
- Decisions or support needed

Missing information policy:
Proceed with assumptions unless the leadership audience or department inputs are unclear.

Quality bar:
- Integrated signal.
- Cross-functional awareness.
- Low status-report clutter.
12

Turn a Messy Slack Thread into a Clean Internal Memo

Turn a messy Slack thread into a clean internal memo with context, conclusions, and follow-up needs.

You’ll needSlack thread or chat logaudiencetopickey decisions if anyopen questionstone
Prompt
You are turning a messy Slack thread into a clean internal memo.

Use the context below.

Context:
- Slack thread, chat log, or conversation summary: [thread]
- Audience for the memo: [audience]
- Topic or issue discussed: [topic]
- Key decisions already made if any: [decisions]
- Open questions or unresolved points: [questions]
- Tone guidance: [tone]

Instructions:
1. Extract the actual signal from the thread without carrying over chat noise.
2. Clarify what happened, what was decided, and what remains unresolved.
3. Make the memo useful to someone who never saw the thread.
4. Preserve nuance where the conversation revealed important tension or tradeoffs.
5. Keep the final memo clean and easy to scan.

Output format:
- Topic summary
- What happened
- Decisions or conclusions
- Open questions
- Follow-up needs

Missing information policy:
Ask first only if the thread or memo audience is missing.

Quality bar:
- Useful to non-participants.
- Clear signal extraction.
- Low chat residue.
13

Write a Leadership Summary After a Weekly Metric Review

Write a leadership summary after a weekly metric review with movement, interpretation, and follow-up needs.

You’ll needweekly metric review notesmajor changesquestions raisedrisksaudiencefollow-up actions
Prompt
You are writing a leadership summary after a weekly metric review.

Use the context below.

Context:
- Weekly metric review notes or data summary: [notes]
- Major changes or shifts: [changes]
- Questions raised in the review: [questions]
- Risks or concerns: [risks]
- Audience: [audience]
- Follow-up actions or investigations: [follow-up]

Instructions:
1. Capture the signal from the review without replaying every metric discussed.
2. Explain what changed, what matters, and what leadership should keep watching.
3. Distinguish interpretation from open questions.
4. Make follow-up actions and owners easy to understand.
5. Keep the summary concise and leadership-ready.

Output format:
- Summary of the review
- Key changes and implications
- Open questions
- Follow-up actions
- Watch items for next review

Missing information policy:
Proceed with assumptions unless the notes or audience are unclear.

Quality bar:
- Signal-first summary.
- Clear follow-up.
- Leadership-ready brevity.
14

Rewrite an Internal Update So the Ask Is Unmistakable

Rewrite an internal update so the ask is unmistakable while preserving the necessary context and nuance.

You’ll needcurrent updateintended askaudiencesupporting contexttoneconstraints
Prompt
You are rewriting an internal update so the ask is unmistakable.

Use the context below.

Context:
- Current update draft: [update]
- Intended ask or decision needed: [ask]
- Audience: [audience]
- Supporting context that must remain: [context]
- Tone guidance: [tone]
- Constraints or sensitivities: [constraints]

Instructions:
1. Make the ask or decision needed explicit early.
2. Tighten the supporting context so it helps rather than obscures.
3. Preserve necessary nuance and relationship awareness.
4. Remove hedging, filler, and buried conclusions.
5. Keep the rewritten version easy to scan.

Output format:
- Main problems with the current draft
- Rewritten update
- Notes on what changed

Missing information policy:
Ask first only if the draft or intended ask is missing.

Quality bar:
- Ask is unmistakable.
- Context still useful.
- Clearer internal communication.
15

Draft a Cross-Team Alignment Note After a Messy Decision Process

Draft a cross-team alignment note after a messy decision process with decisions, tensions, and next steps.

You’ll needdecision process notesteams involvedfinal decisionsremaining tensionsnext stepsaudience
Prompt
You are drafting a cross-team alignment note after a messy decision process.

Use the context below.

Context:
- Decision process notes or source material: [notes]
- Teams involved: [teams]
- Final decisions or current stance: [decisions]
- Remaining tensions or concerns: [tensions]
- Next steps: [next steps]
- Audience: [audience]

Instructions:
1. Clarify what was actually decided and what remains unsettled.
2. Reduce ambiguity about how teams should proceed next.
3. Preserve enough context to make the note credible without reopening the whole debate.
4. Surface unresolved tensions honestly where they still matter.
5. Keep the note useful to teams that now need to execute.

Output format:
- Alignment summary
- What was decided
- What remains unresolved
- Next steps by team or owner
- Risks or watchpoints

Missing information policy:
Proceed with assumptions unless the decisions or audience are unclear.

Quality bar:
- Execution usefulness.
- Honest tension handling.
- Clearer alignment than the raw process.
16

Turn a Long Email Thread into a Leadership Summary

Turn a long email thread into a leadership summary with context, decisions, tensions, and next actions.

You’ll needemail threadaudiencetopicknown decisionsopen tensionsfollow-up needs
Prompt
You are turning a long email thread into a leadership summary.

Use the context below.

Context:
- Email thread or summary of the thread: [thread]
- Audience: [audience]
- Topic or issue: [topic]
- Known decisions already made: [decisions]
- Open tensions or disagreements: [tensions]
- Follow-up needs: [follow-up]

Instructions:
1. Extract the useful signal without carrying over thread sprawl.
2. Clarify what happened, what matters now, and what still needs attention.
3. Separate decisions from unresolved debate.
4. Make the summary useful to someone who did not read the thread.
5. Keep it concise and leadership-ready.

Output format:
- Thread summary
- Decisions or conclusions
- Remaining tensions or open questions
- Follow-up actions

Missing information policy:
Proceed with assumptions unless the thread or intended audience are unclear.

Quality bar:
- Useful to non-participants.
- Clear signal extraction.
- Leadership-ready brevity.
17

Write a Policy-Change Announcement with Low Confusion Risk

Write a policy-change announcement with rationale, what changes, what stays the same, and what people should do next.

You’ll needpolicy changeaudiencereason for changeeffective dateexceptionstone
Prompt
You are writing a policy-change announcement with low confusion risk.

Use the context below.

Context:
- Policy change being announced: [policy change]
- Audience: [audience]
- Reason for the change: [reason]
- Effective date or timeline: [effective date]
- Exceptions, edge cases, or carve-outs: [exceptions]
- Tone guidance: [tone]

Instructions:
1. Explain what is changing and why in plain language.
2. Make it easy to understand what stays the same and what changes.
3. Include what people need to do next, if anything.
4. Reduce avoidable confusion and procedural ambiguity.
5. Keep the tone clear, calm, and operational.

Output format:
- Policy-change announcement
- What is changing
- What is not changing
- Actions or next steps
- Clarifying notes or exceptions

Missing information policy:
Proceed with assumptions unless the policy change or audience is unclear.

Quality bar:
- Low confusion risk.
- Clear action guidance.
- Calm operational tone.
18

Draft a Team Restructure Note with Clarity and Sensitivity

Draft a team restructure note with clarity, sensitivity, rationale, and next steps.

You’ll needrestructure contextaudiencereason for changewhat changeswhat remains stabletone
Prompt
You are drafting a team restructure note with clarity and sensitivity.

Use the context below.

Context:
- Restructure context or proposed changes: [restructure]
- Audience: [audience]
- Reason for the change: [reason]
- What changes materially: [changes]
- What remains stable: [stability]
- Tone guidance: [tone]

Instructions:
1. Explain the change clearly without unnecessary spin.
2. Acknowledge the human impact without becoming vague or evasive.
3. Clarify what changes now, what happens next, and what remains stable.
4. Reduce rumor-generating ambiguity.
5. Keep the tone respectful, clear, and leadership-appropriate.

Output format:
- Restructure note
- Why the change is happening
- What changes now
- What remains stable
- Next steps or support guidance

Missing information policy:
Proceed with assumptions unless the restructure context or audience is unclear.

Quality bar:
- Clear explanation.
- Human sensitivity.
- Low rumor risk.
19

Explain a Project Delay Honestly Without Sounding Evasive

Explain a project delay honestly without sounding evasive, and clarify impact, causes, and revised next steps.

You’ll needcurrent draft or source notesaudiencedelay causesbusiness impactnew timingtone
Prompt
You are explaining a project delay honestly without sounding evasive.

Use the context below.

Context:
- Current draft or source notes: [draft]
- Audience: [audience]
- Delay causes or contributing factors: [causes]
- Business or customer impact: [impact]
- Revised timing or next milestones: [timing]
- Tone guidance: [tone]

Instructions:
1. Explain the delay clearly and directly.
2. Distinguish cause from excuse.
3. Clarify impact, what is being done now, and what the revised path is.
4. Preserve candor without spiraling into defensive detail.
5. Keep the final version concise and useful.

Output format:
- Main issues with the current explanation
- Rewritten delay explanation
- Notes on what changed

Missing information policy:
Ask first only if the draft or delay causes are missing.

Quality bar:
- Direct and honest.
- Clear revised path.
- Low excuse language.
20

Turn a Messy Discussion into a Clean Decision-Log Entry

Turn a messy discussion into a clean decision-log entry with rationale, owners, and revisit conditions.

You’ll needdiscussion notesdecision madeoptions consideredreasoningownerrevisit triggers
Prompt
You are turning a messy discussion into a clean decision-log entry.

Use the context below.

Context:
- Discussion notes or conversation summary: [notes]
- Decision made if any: [decision]
- Options considered: [options]
- Reasoning or tradeoffs: [reasoning]
- Owner or decision-maker: [owner]
- Revisit conditions or known caveats: [revisit triggers]

Instructions:
1. Capture the decision clearly enough to reference later.
2. Include the rationale and tradeoffs, not just the conclusion.
3. Clarify ownership and when the decision might be revisited.
4. Remove transcript residue and side tangents.
5. Keep the entry compact and useful.

Output format:
- Decision-log entry
- Reasoning and tradeoffs
- Owner and next steps
- Revisit conditions

Missing information policy:
Proceed with assumptions unless the discussion notes or decision are unclear.

Quality bar:
- Clear decision record.
- Useful rationale.
- Easy to reference later.
21

Draft a Quarterly Priorities Memo from Department Inputs

Draft a quarterly priorities memo from department inputs with themes, tradeoffs, and what matters most next quarter.

You’ll needdepartment inputscompany goalsresource constraintscross-team tensionsaudiencequarter context
Prompt
You are drafting a quarterly priorities memo from department inputs.

Use the context below.

Context:
- Department inputs or summaries: [inputs]
- Company goals or strategic priorities: [goals]
- Resource constraints: [constraints]
- Cross-team tensions or tradeoffs: [tensions]
- Audience: [audience]
- Quarter context or timing: [quarter]

Instructions:
1. Consolidate the inputs into a coherent priorities memo.
2. Surface where alignment is strong and where tradeoffs are real.
3. Clarify what should matter most next quarter.
4. Avoid turning the memo into a stitched-together department dump.
5. Keep the writing concise and strategic.

Output format:
- Quarterly priorities summary
- Main themes and tradeoffs
- Recommended top priorities
- Risks or unresolved tensions

Missing information policy:
Proceed with assumptions unless the company goals or audience are unclear.

Quality bar:
- Coherent cross-team synthesis.
- Real tradeoff handling.
- Strategic clarity.
22

Turn a Customer or Partner Call into a Briefing Note

Turn a customer or partner call into a briefing note with key points, risks, opportunities, and next actions.

You’ll needcall notes or transcriptaudiencerelationship contextmain issuesopportunitiesfollow-up needs
Prompt
You are turning a customer or partner call into a briefing note.

Use the context below.

Context:
- Call notes or transcript summary: [notes]
- Audience: [audience]
- Relationship or account context: [relationship]
- Main issues or concerns raised: [issues]
- Opportunities or positive signals: [opportunities]
- Follow-up needs: [follow-up]

Instructions:
1. Extract the real signal from the call.
2. Clarify what matters most for the audience receiving the note.
3. Distinguish concerns, opportunities, and next actions.
4. Avoid transcript residue and low-value recap.
5. Keep the note concise and useful.

Output format:
- Briefing summary
- Main concerns or risks
- Opportunities or positive signals
- Recommended follow-up

Missing information policy:
Proceed with assumptions unless the call notes or audience are unclear.

Quality bar:
- Signal-focused.
- Concise and useful.
- Clear next actions.
23

Write a Follow-Up Note After a Tense Meeting

Write a follow-up note after a tense meeting that clarifies decisions, unresolved points, and the path forward.

You’ll needmeeting contextwhat created tensionaudiencedecisions madeunresolved issuestone
Prompt
You are writing a follow-up note after a tense meeting.

Use the context below.

Context:
- Meeting context: [context]
- What created tension or confusion: [tension]
- Audience: [audience]
- Decisions made if any: [decisions]
- Unresolved issues: [issues]
- Tone guidance: [tone]

Instructions:
1. Restore clarity without pretending the tension did not happen.
2. Clarify what was decided, what remains open, and what happens next.
3. Reduce ambiguity that could create a second round of conflict.
4. Keep the tone steady, respectful, and useful.
5. Make the note practical for execution.

Output format:
- Follow-up note
- Decisions confirmed
- Remaining open points
- Next steps

Missing information policy:
Proceed with assumptions unless the meeting context or audience are unclear.

Quality bar:
- Calm clarity.
- Honest handling of unresolved issues.
- Useful next steps.
24

Create an Executive Summary from a Research Pack

Create an executive summary from a research pack with key findings, implications, uncertainty, and next questions.

You’ll needresearch pack or findingsaudiencedecision contextconfidence limitsmain implicationsopen questions
Prompt
You are creating an executive summary from a research pack.

Use the context below.

Context:
- Research pack, report, or findings: [research]
- Audience: [audience]
- Decision context: [decision context]
- Confidence limits or caveats: [confidence limits]
- Main implications: [implications]
- Open questions: [questions]

Instructions:
1. Extract the few findings that matter most for the decision context.
2. Distinguish strong findings from tentative interpretation.
3. Surface the implications, not just the findings themselves.
4. Respect uncertainty and caveats without making the summary mushy.
5. Keep the summary concise and leadership-ready.

Output format:
- Executive summary
- Key findings
- Implications
- Confidence limits
- Next questions

Missing information policy:
Proceed with assumptions unless the research pack or decision context are unclear.

Quality bar:
- Decision-relevant synthesis.
- Respect for uncertainty.
- Leadership brevity.
25

Write a Brief That Frames Open Questions Before a Strategy Discussion

Write a brief that frames open questions before a strategy discussion with context, stakes, and decision implications.

You’ll needstrategy topiccurrent stateopen questionsstakesknown optionsaudience
Prompt
You are writing a brief that frames open questions before a strategy discussion.

Use the context below.

Context:
- Strategy topic or issue: [topic]
- Current state or background: [current state]
- Open questions: [questions]
- Stakes or consequences: [stakes]
- Known options or directions: [options]
- Audience: [audience]

Instructions:
1. Frame the real questions the discussion should answer.
2. Provide only the context needed to orient the audience.
3. Explain why the questions matter and what tradeoffs sit behind them.
4. Prevent the brief from sliding into premature solutioning.
5. Keep the note concise and discussion-ready.

Output format:
- Discussion brief
- Open questions
- Why they matter
- Relevant context and tradeoffs

Missing information policy:
Proceed with assumptions unless the strategy topic or audience are unclear.

Quality bar:
- Sharp questions.
- Just enough context.
- Good discussion setup.
26

Turn Product Context into a Concise Internal Positioning Note

Turn product context into a concise internal positioning note with audience, core differentiation, and message implications.

You’ll needproduct contexttarget audiencemarket realitycustomer paindifferentiationinternal audience
Prompt
You are turning product context into a concise internal positioning note.

Use the context below.

Context:
- Product context or current understanding: [product context]
- Target audience: [target audience]
- Market reality or competitive context: [market context]
- Customer pain or demand: [customer pain]
- Differentiation or strengths: [differentiation]
- Internal audience using this note: [internal audience]

Instructions:
1. Distill the product context into a short positioning note.
2. Clarify who the product is really for and what it should stand for.
3. Surface differentiation without falling into slogan language.
4. Include implications for internal messaging or decision-making.
5. Keep the note short, sharp, and useful.

Output format:
- Positioning note
- Audience and pain
- Differentiation
- Internal message implications

Missing information policy:
Proceed with assumptions unless the product context or target audience are unclear.

Quality bar:
- Real positioning clarity.
- Low slogan fluff.
- Internal usefulness.
27

Rewrite a Technical Update for Non-Specialist Leaders

Rewrite a technical update for non-specialist leaders with clearer implications, risk, and decision relevance.

You’ll needcurrent updateleader audiencetechnical topicmain risksbusiness implicationstone
Prompt
You are rewriting a technical update for non-specialist leaders.

Use the context below.

Context:
- Current update draft or notes: [update]
- Leadership audience: [audience]
- Technical or operational topic: [topic]
- Main risks or concerns: [risks]
- Business implications: [implications]
- Tone guidance: [tone]

Instructions:
1. Rewrite the update so non-specialists can understand what matters quickly.
2. Reduce jargon and implementation detail that does not change leadership interpretation.
3. Preserve the real risk, tradeoff, and decision relevance.
4. Avoid oversimplifying into something misleading.
5. Keep the final version concise and readable.

Output format:
- Main clarity problems in the current update
- Rewritten leadership version
- Notes on what was simplified or preserved

Missing information policy:
Ask first only if the current update or business implications are missing.

Quality bar:
- Non-specialist clarity.
- Preserved decision relevance.
- No misleading oversimplification.
28

Write the Questions Leadership Should Answer Before a Decision

Write the questions leadership should answer before a decision, including tradeoff, risk, and reversibility questions.

You’ll needdecision topiccontextknown optionsrisksconstraintsaudience
Prompt
You are writing the questions leadership should answer before a decision.

Use the context below.

Context:
- Decision topic: [topic]
- Context or current state: [context]
- Known options: [options]
- Risks or downside concerns: [risks]
- Constraints: [constraints]
- Audience: [audience]

Instructions:
1. Identify the questions that will most improve decision quality.
2. Include tradeoff, reversibility, timing, and downside-risk questions.
3. Avoid obvious or ceremonial questions.
4. Keep the set short enough to be used in an actual review.
5. Tailor the questions to the decision context rather than using a generic list.

Output format:
- Critical questions
- Why each question matters
- Questions that would change the decision materially

Missing information policy:
Proceed with assumptions unless the decision topic or context are unclear.

Quality bar:
- Decision-quality focus.
- Tailored questions.
- High leverage over completeness.
29

Rewrite an Update So the Risk Is Clearer Without Overstating It

Rewrite an update so the risk is clearer without overstating severity or creating unnecessary alarm.

You’ll needcurrent updateactual riskaudiencewhat is uncertaindesired toneactions underway
Prompt
You are rewriting an update so the risk is clearer without overstating it.

Use the context below.

Context:
- Current update draft: [update]
- Actual risk or issue: [risk]
- Audience: [audience]
- What is still uncertain: [uncertainty]
- Desired tone: [tone]
- Actions underway: [actions]

Instructions:
1. Clarify the real risk signal and what it means.
2. Avoid both softening the issue too much and overstating it into drama.
3. Preserve what is still uncertain.
4. Make the implications and next steps easier to understand.
5. Keep the rewritten version concise and balanced.

Output format:
- Main problems in the current update
- Rewritten update
- Notes on uncertainty and tone

Missing information policy:
Ask first only if the current update or actual risk is missing.

Quality bar:
- Clearer risk signal.
- Proportionate tone.
- Better next-step clarity.
30

Create an Executive Readout from Mixed Department Inputs

Create an executive readout from mixed department inputs with signal, tradeoffs, and follow-up points.

You’ll needdepartment inputsaudienceshared contextknown tensionsdecisions neededtiming
Prompt
You are creating an executive readout from mixed department inputs.

Use the context below.

Context:
- Department inputs or source material: [inputs]
- Audience: [audience]
- Shared business or team context: [context]
- Known tensions or tradeoffs: [tensions]
- Decisions needed: [decisions]
- Timing or review context: [timing]

Instructions:
1. Synthesize the mixed inputs into one coherent readout.
2. Prioritize signal over perfect representation of every department.
3. Surface the biggest tradeoffs, risks, and alignment questions.
4. Clarify what leaders should pay attention to now.
5. Keep the readout concise and decision-useful.

Output format:
- Executive readout summary
- Main signals
- Tradeoffs or tensions
- Decisions or follow-up needs

Missing information policy:
Proceed with assumptions unless the inputs or audience are unclear.

Quality bar:
- Coherent synthesis.
- Tradeoff visibility.
- Decision usefulness.
31

Write a Follow-Up Email from Messy Meeting Notes

Write a follow-up email from messy meeting notes with a clear recap, ownership, and next-step clarity.

You’ll needmeeting notesaudiencemeeting purposedecisions madeowners and deadlinestone
Prompt
You are writing a follow-up email from messy meeting notes.

Use the context below.

Context:
- Rough meeting notes: [notes]
- Audience receiving the email: [audience]
- Meeting purpose: [purpose]
- Decisions already made: [decisions]
- Owners, deadlines, or commitments mentioned: [owners]
- Tone guidance: [tone]

Instructions:
1. Turn the rough notes into a clean, professional follow-up email.
2. Separate confirmed decisions from open questions or pending items.
3. Make owners and deadlines explicit where they were mentioned or strongly implied.
4. Keep the email concise enough to be read quickly after the meeting.
5. Do not bury the main ask or next step.

Output format:
- Subject line
- Email body
- Open questions or unresolved items

Missing information policy:
Proceed with assumptions unless the notes or audience are unclear.

Quality bar:
- Clear recap.
- Explicit ownership.
- Easy to act on.
32

Adapt a Message for Executives, Peers, or Customers

Adapt one message for executives, peers, or customers with the right level of tone, context, and emphasis.

You’ll needoriginal messagetarget audienceoriginal contextmain objectivesensitive pointstone constraints
Prompt
You are adapting one message for a new audience.

Use the context below.

Context:
- Original message: [message]
- Target audience: [audience]
- Original context or source audience: [context]
- Main objective of the message: [objective]
- Sensitive points or risks: [sensitive points]
- Tone constraints: [tone]

Instructions:
1. Preserve the core meaning while adapting tone, detail level, and emphasis for the new audience.
2. Clarify what the new audience most needs to understand or decide.
3. Remove wording that feels too internal, too technical, or too blunt for the target audience.
4. Flag any content that should not be carried over unchanged.
5. Keep the rewrite credible and direct rather than overpolished.

Output format:
- Audience-adaptation summary
- Rewritten message
- What changed and why
- Risks or watchouts

Missing information policy:
Proceed with assumptions unless the original message or target audience is unclear.

Quality bar:
- Same meaning, better fit.
- Appropriate detail level.
- Credible tone.