Claude Prompt Library

Claude Prompts for Leadership Decisions That Hold Up

16 copy-paste prompts

20 copy-paste Claude prompts for leadership work: strategic thinking, hard decisions, executive communication, leading through change, developing other leaders. Claude as a thinking partner — not a yes-man.

In short: This page contains 16 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

Louis Corneloup
By Louis Corneloup · Founder, Techpresso
Last updated ·Hand-curated & tested by the AI Academy team

Strategic Thinking

4 prompts

Strategy Stress Test

1/16

✨ What it does

Claude stress-tests [Paste strategy I'm considering] with best and worst cases plus likelihood, shaky assumptions, missing feedback, motivated reasoning versus evidence, and second-order effects you skipped. Paste the strategy, then sit with the worst-case line before you commit.

[Paste strategy I'm considering]. Stress test it ruthlessly. Output: best case if right (and likelihood), worst case if wrong (and likelihood), what I'm assuming I shouldn't, what feedback I haven't sought, where I'm motivated-reasoning vs evidence-based, second-order effects I'm missing. Push back hard.

💡

Pro tip: Default Claude = diplomatic. Add "push back hard" + "ruthless critique" — different output. Without explicit license, you get balanced feedback that helps less.

Pre-Mortem on Big Decision

2/16

✨ What it does

Claude runs a pre-mortem on [decision], assuming it failed badly in 18 months, with causes, contributing factors, ignored warning signs, and which of those signs you can already see. Name the decision, then act on the warning that is already visible.

I'm considering [decision]. Run pre-mortem: assume 18 months from now this failed badly. What happened? Cause + contributing factors + warning signs ignored. Then: which warning signs are visible RIGHT NOW that I'm discounting? Honest read.

💡

Pro tip: Pre-mortem surfaces risks optimism hides. "What would failure look like?" + "what signs would predict it?" + "are those signs visible now?" = catches blind spots before commit.

Strategic Tradeoff Articulation

3/16

✨ What it does

Claude lays out the tradeoff between [option A] and [option B]: what you gain, what you give up, what each assumes, which matches your real values, and which is the easier choice you will regret. Fill both options, then pick one; treating both as right is not a strategy.

Help me articulate the tradeoff between [option A] and [option B]. Each option: what we gain, what we sacrifice, what assumes. Then: which option matches our actual values + constraints, which is "easier choice that we'll regret"? Force the choice; both being right = strategy without teeth.

💡

Pro tip: Strategy is choice. "We'll do both" usually = doing neither well. Forced binary surfaces real preference. Then deliberately choose, knowing the cost.

Vision Statement Calibration

4/16

✨ What it does

Claude critiques [Paste current vision/mission] for vagueness, over-specificity, inspiration without stretch, stretch without belief, and what would have to change for people to actually act differently. Paste your statement, then rewrite the line that would not change anyone's behavior.

[Paste current vision/mission]. Critique: too vague (could fit any company)? Too specific (boxes us in)? Inspirational without aspirational? Aspirational without believable? What changes would make stakeholders actually act differently?

💡

Pro tip: Vision statements pass the "swap with competitor" test if they're too generic. "Best-in-class X for Y" = meaningless. Specific enough to be us, big enough to inspire — narrow band.

XML tags are just the start. Learn the full Claude workflow.

A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.

Start 7-Day Free Trial

Decision-Making

4 prompts

Reversible vs Irreversible Decision Frame

5/16

✨ What it does

Claude classifies decision [describe] as reversible or a one-way door, then tells you to decide fast if you can undo it, or slow down and gather more if you cannot. Describe the call, then match your pace to that classification instead of inverting it.

I'm facing decision: [describe]. Help me classify: reversible (low cost to undo) or irreversible (one-way door). Then: if reversible, decide fast + iterate. If irreversible, gather more info + slow down. Most people invert this. Frame correctly = better decision speed.

💡

Pro tip: Bezos two-doors. Reversible decisions deserve speed; irreversible deserve deliberation. Most people deliberate over reversible (perfectionism) + rush irreversible (urgency illusion). Inversion costs time + capital.

Decision Right Identification

6/16

✨ What it does

Claude maps decision rights for [decision]: who decides (one person), who is consulted, who is informed, and who is affected but not asked, forcing a single decider. Name your decision, then write the one name who owns the call.

For [decision], help me identify decision rights: who decides (single point), who's consulted (input expected), who's informed (kept in loop), who's impacted but not consulted (manage feelings). Force a single decider. Decision-by-committee = decision-by-nobody.

💡

Pro tip: "Let's decide together" = nobody decides. RACI for decisions: one Accountable. Consulted gives input; impacted gets informed. Single decider = decision actually happens.

Cost-of-Delay Analysis

7/16

✨ What it does

Claude quantifies the cost of delaying [describe]: opportunity cost per week, optionality lost, team frustration, and competitor advantage, then compares that to deciding too soon. Describe your delay, then decide this week if waiting is already costing more.

I'm delaying decision: [describe]. Help me quantify cost of delay: opportunity cost per week, optionality lost, team frustration accumulating, competitor advantage given. Compare to cost of premature decision. Often delay's cost > rush's cost; people miscalculate.

💡

Pro tip: Delay feels safe (no one blamed for non-action). Rush feels risky. But cost-of-delay accumulates invisibly. Naming it = reset perception. Often delay's cost dwarfs rush risk.

Hard Conversation Decision

8/16

✨ What it does

Claude walks you through whether to have the hard conversation [describe]: cost of silence, short-term pain of saying it, the fear underneath, and your obligation in the role, then a have-it or not call. Describe the conversation, then put it on the calendar if the compounding cost wins.

I have a difficult conversation pending: [describe]. Walk me through deciding whether to have it: cost of not having it (compounds), cost of having it (short-term pain), my actual fear (rejection? conflict? being wrong?), my obligation given my role. Decision: have it or not?

💡

Pro tip: Avoiding conversations = leadership tax. Compounds quietly until explosion. Naming the fear = often realizing it's exaggerated. Leader's job sometimes IS the conversation; not having it = dereliction.

Executive Communication

4 prompts

All-Hands Update

9/16

✨ What it does

Claude writes a company all-hands update on [topic] that is confident and honest: where you are with data, what changed, what is next, and what each team must do, without hedging. Fill the topic, then read it aloud once before you send it.

Write all-hands update on [topic]. Audience: full company. Tone: confident, honest, contextual. Cover: where we are (data), what changed (specific), what's next (clear), what we need from each team (asks). Avoid corporate hedging. Trust drops fast when execs hedge in front of full company.

💡

Pro tip: Hedge-words ("we're working to potentially explore") destroy trust. Direct ("we decided X. Here's why. Here's what we need.") = leadership read. Hedging = "they're scared/uncertain."

Hard News Delivery

10/16

✨ What it does

Claude drafts the hard-news message for [describe] plus a delivery plan: written copy, audience variants, in-person versus written, who hears first, follow-up commitments, and how you handle your own emotion. Describe the news, then tell the first audience before the rest hear it elsewhere.

I need to deliver hard news: [describe]. Help me draft message + plan delivery. Output: written message, audience-by-audience adaptation, in-person vs written tradeoff, sequence (who hears first), follow-up commitments, my own emotion management. Honesty + dignity, not corporate-speak.

💡

Pro tip: Hard news read by sequence. Affected people first, then management, then broad. Reverse = leak + chaos. Sequence + delivery = the part that hurts vs heals.

Board Update

11/16

✨ What it does

Claude writes a board update for [period] with a one-page summary, 3 wins, 3 challenges and your response, key metrics, asks of the board, and what is ahead, including what is not working. Fill the period, then leave the hard news in; do not sand it down.

Board update for [period]. Output: 1-page summary, 3 wins, 3 challenges + how we're responding, key metrics, asks of the board, what's ahead. Honest about what isn't working — boards smell BS + lose confidence faster than from honest hard news.

💡

Pro tip: Board updates over-positive = trust erosion. Boards prefer "honest about hard things + clear plan" > "everything's great" repeated. Honest hard updates build credibility for hard asks later.

Memo on Strategic Pivot

12/16

✨ What it does

Claude writes an internal memo on [strategic change] covering what changes, why now with data, what stays the same, how each function is affected, and what tomorrow's town hall will cover. Name your change, then send the memo before the town hall so people can digest it.

Internal memo announcing [strategic change]. Audience: full company. Output: what we're changing (specific), why now (data + context), what stays the same (calming), how this affects each function (preview), questions tomorrow's town hall will cover. Send write-up before town hall — give people time to digest.

💡

Pro tip: Surprise pivots in town hall = panic. Memo first + town hall to discuss = thoughtful. Asynchronous read time = better questions in synchronous meeting.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Developing Leaders

4 prompts

Leader 1:1 Coaching Prep

13/16

✨ What it does

Claude preps your 1:1 coaching of [direct report leader] given [describe]: what is likely under the surface, what they need versus what they asked, questions to draw thinking out, where to push or support, and how they leave owning it. Fill both blanks, then ask the questions instead of handing them the plan.

I'm coaching [direct report leader]. Their situation: [describe]. Help me prep: what's probably going on under-the-surface, what they need from me (vs what they're asking for — often different), questions to draw out their thinking, where to push, where to support, how to leave them owning it.

💡

Pro tip: Coaching ≠ advising. Asking right questions > giving right answers. Leaders grow from finding own answers; advised-to leaders stay dependent. Coach = ask; consultant = answer.

Promoting High-Potential

14/16

✨ What it does

Claude builds a development plan for [High potential employee] with strengths, specific gaps, stretch assignments, visibility they need, feedback cadence, and when to promote versus keep stretching. Name your person, then design one stretch assignment before the next role opens.

[High potential employee]. Help me build their development plan. Output: strengths to leverage, gaps to close (specific), stretch assignments to design, exposure they need (visibility, networks), feedback cadence, when to promote vs when to keep stretching. Goal: ready when next role opens.

💡

Pro tip: Promotion = often just-in-time. Better: ready-and-waiting. Stretch assignments + exposure built deliberately = no scramble when role opens. Sequencing matters.

Underperforming Leader Support

15/16

✨ What it does

Claude diagnoses an underperforming leader from symptoms [describe] as capacity, fit, skill gap, or values, with a different intervention for each. Describe your symptoms, then pick one cause and the matching intervention; do not mix them.

My direct-report leader is underperforming. Symptoms: [describe]. Help me diagnose: are they overwhelmed (capacity), in wrong role (fit), missing skill (gap), or wrong values (deeper)? Different intervention per cause. Be honest about which it likely is.

💡

Pro tip: Generic "performance plan" misses root cause. Capacity gap = redistribute load. Skill gap = training + mentor. Role fit = harder conversation. Values mismatch = part ways. Diagnose first.

Succession Planning

16/16

✨ What it does

Claude plans succession for [my role / key role] with who could step in tomorrow, in 12 months, and in 3 years, the gap if nobody can, and whether an external hire is realistic. Pick your role, then start developing the 12-month person this quarter.

Succession planning for [my role / key role]. Output: who could step in tomorrow (gaps + risks), who could step in 12 months (with development), who could step in 3 years (with stretch), gap if neither happens, external candidate possibility. Honest assessment.

💡

Pro tip: Succession plans without honest gap analysis = false security. Acknowledging "no internal candidate today" = trigger to develop OR plan external search. Self-deception = surprise vacancy = disaster.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

For thinking-partner work (stress-testing strategy, working through decisions, drafting communications): yes. For relationship + presence work (coaching live, in-person decisions, team trust): no. Use Claude for the thinking; you do the leading.
Claude tends to push back more (with explicit prompting) + handle nuance better. ChatGPT tends to be more agreeable. For thinking partnership where you want challenge, Claude often serves better. Both useful; different defaults.
Less than ChatGPT, but yes by default. Add "challenge me," "push back where I'm wrong," "be honest, not encouraging" — different output. Without that license, leaders get sycophantic confirmation.
Don't paste confidential business decisions, employee specifics, financial details into consumer Claude. Use Anthropic via Bedrock with controls if needed, or de-identify before pasting. Org policy may restrict regardless.
Different roles. Coach = relationship, accountability, pattern-spotting across years. Claude = on-demand thinking, faster iteration, no scheduling. Best leaders use both. Coach for depth + accountability; Claude for daily thinking.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.