Best Prompts for Executive Leadership

Leadership meetings often consume time without producing clear decisions. Updates arrive in different formats, important context is buried in slides, and unresolved questions are mixed with routine reporting. Executives may leave knowing more, but not knowing exactly what they need to decide, what happens next, or what the cost of waiting might be.

A weekly decision memo should reduce that friction. Its job is not to summarize everything that happened. Its job is to identify the few matters that require leadership attention, present the relevant evidence, and make the requested decisions explicit.

Why ordinary prompting fails

A request such as “write an executive update from these notes” gives an AI too much freedom. It may elevate interesting details instead of consequential decisions, make weak evidence sound conclusive, or produce polished recommendations without identifying their assumptions.

A useful prompt must separate facts, interpretations, and recommendations. It should also require an explicit decision owner, deadline, options, trade-offs, and consequences of delay. If the source material does not support a conclusion, the output should say so rather than filling the gap.

The prompt

Copy
ROLE
You are an executive chief of staff preparing a concise weekly decision memo. Your purpose is to help the leadership team make decisions, not to provide a general activity summary.

REQUIRED INPUTS
- Reporting period
- Company or business-unit priorities
- Updates, meeting notes, dashboards, and project reports
- Decisions already made during the period
- Open questions or escalations
- Known constraints, dependencies, and deadlines
- Named owners where available

STEPS
1. Read all source material and identify items that require an executive decision, approval, escalation, or cross-functional alignment.
2. Exclude routine updates unless they materially affect a priority, deadline, risk, customer commitment, or resource allocation.
3. For each decision, state:
   - the decision required
   - the decision owner or forum
   - the deadline
   - why the decision is needed now
   - available options
   - trade-offs for each option
   - the recommended option, if the evidence supports one
   - likely consequences of delaying the decision
4. Separate confirmed facts from interpretations and recommendations.
5. Identify decisions completed since the previous memo and record the resulting action and owner.
6. End with a short list of missing information that would materially improve any decision.

OUTPUT FORMAT
# Weekly Decision Memo: [date range]
## Executive summary
Three to five bullets covering only material changes and decisions.

## Decisions required
For each item:
- Decision:
- Owner or forum:
- Decision deadline:
- Why now:
- Evidence:
- Options and trade-offs:
- Recommendation:
- Consequence of delay:
- Confidence: High, Medium, or Low

## Decisions completed
A table with decision, date, outcome, action owner, and next checkpoint.

## Watch items
Items that do not require a decision yet but may require one soon.

## Information gaps
Questions that must be answered, with a suggested owner for each.

EVIDENCE AND UNCERTAINTY RULES
- Use only the supplied material.
- Do not invent financial effects, dates, owners, customer reactions, or probabilities.
- Cite the source document, note, or metric beside each important claim.
- Label assumptions explicitly.
- If options cannot be compared with the available evidence, say “Insufficient evidence to recommend.”
- Preserve disagreement when sources conflict and identify what would resolve it.

What to provide

Give the prompt the same materials a chief of staff would need: current priorities, leadership notes, performance data, project updates, and a record of previous decisions. Include dates and document names so the memo can cite them. If you already know which matters belong on the leadership agenda, label them, but do not remove the underlying evidence.

Avoid uploading an unfiltered archive if a smaller, current set of materials is available. Old context can cause outdated assumptions to appear current. Mark superseded plans clearly.

How to review the output

First, check whether every item in “Decisions required” is actually a decision. “Improve onboarding” is a goal. “Approve one additional onboarding engineer for the next quarter” is a decision.

Then verify every recommendation against its cited evidence. Look for hidden certainty, especially around costs, timing, and customer impact. Confirm the owner and deadline with the people involved. Finally, ask whether the memo makes delay visible. A decision with no stated timing can quietly become another update.

Where it fails

The prompt cannot repair poor source material. If teams provide opinions without supporting facts, the memo can organize the uncertainty but cannot resolve it. It may also over-compress a decision that involves legal, regulatory, personnel, or technical detail. Those decisions need specialist review and the full supporting documents.

It also fails when leadership has not agreed on priorities. Without that filter, almost any issue can appear important.

Practical takeaway

A strong weekly memo is a decision instrument, not a record of activity. Use the prompt to create a disciplined first draft, then have the responsible leaders validate the evidence, recommendation, owner, and deadline. You can try the prompt in Agentic Workers with your current weekly reports and refine the format around how your leadership team actually decides.

<!-- X derivative: Turn scattered leadership updates into a weekly memo that separates facts, options, trade-offs, and the decisions that cannot wait. -->