| PromptSharp Leadership | SAMPLE ISSUEPRO EDITION |
Copy-paste AI prompts for strategic decisions, board comms, org design, and the operating cadence. Wednesday, July 8, 2026 · For CEOs & Founders · C-suite Executives · Chiefs of Staff & VPs | SAMPLE ISSUE — a representative edition of PromptSharp Leadership prepared for launch. This is what every issue looks like. Your full brief — all five sections’ prompts, ready to paste into your own LLM. Plus the searchable archive of every prompt we’ve shipped. One ready-to-run prompt a day for the exact work executives do — decision stress-tests, board pre-reads, org design reviews, cadence audits, and competitive scans. Paste into your own LLM. No news, no fluff. | The Disagreeing Advisor Strategic Decisions For: CEOs and executives about to commit real money or direction Decision stress-test: pre-mortem, base rates, and pre-committed tripwires A big call is hardening into consensus. Stress-test it with the advisor who is paid to disagree — before the money moves. You are a skeptical board advisor whose job is to disagree with me productively. I will describe a strategic decision, my rationale, and my data. Produce:
A) STEEL-MAN TABLE — my 3 strongest stated reasons, each with the strongest honest counter-argument and the evidence that would settle the disagreement.
B) PRE-MORTEM — it is 18 months later and this decision failed: the top 5 causes ranked by likelihood times damage, each with its earliest observable warning indicator.
C) BASE RATES — the reference class this decision belongs to and what typically happens in it, explicitly labeled "from general knowledge — verify current figures before relying on this".
D) VERDICT — proceed / proceed-with-tripwires / pause, with 3 tripwires (metric + threshold + the pre-committed action when hit).
Inputs: [THE DECISION + DEADLINE] · [MY RATIONALE + KEY DATA] · [ALTERNATIVES I CONSIDERED] · [WHAT WOULD MAKE ME WRONG]
Rules: Do not invent market data or figures — keep my facts separate from your general knowledge and flag every external claim for verification against current sources. Do not soften the counter-arguments to be agreeable. I will not paste material non-public information or personnel records, and you must not ask for them. Why it works: Consensus is where companies lose money — human advisors are too polite, too invested, or too far away to object. Pre-committed tripwires convert a bet into a managed position, and the label-your-training-data rule stops the model's stale base rates from masquerading as current market fact. | | Own the Narrative Board & Investor Comms For: CEOs, CFOs, and chiefs of staff preparing board materials Board memo: the pre-read that kills surprises Board meeting in two weeks. Draft the pre-read that surfaces the hard topic on your terms — before a director does it on theirs. You are a chief of staff drafting a board pre-read memo. I will paste the quarter's numbers and the situation. Produce:
A) MEMO SKELETON — a headline paragraph (state of the business in 5 sentences, no adjective without a number behind it), a KPI table vs plan with variance explanations that state causes rather than describe gaps, a hard-topic section (what happened, impact, what we are doing, what we need), and the asks of the board.
B) QUESTION ANTICIPATION — the 10 hardest questions a director could ask, each with a crisp 3-sentence answer, flagging which answers need pre-verified data.
C) TONE CHECK — flag every instance of hedging, spin, or unexplained jargon in my draft sections.
Inputs: [PASTE KPI DATA VS PLAN] · [THE HARD TOPIC + FACTS] · [LAST MEETING'S OPEN ITEMS] · [MY DRAFT SECTIONS, IF ANY]
Rules: Do not invent numbers or variance explanations — every explanation must come from my inputs or be marked "CFO to confirm". Verify all figures against the finance system before circulation. Never include material non-public information handling guidance or individual compensation data. Why it works: Boards punish surprise harder than they punish bad news. Leading with the hard topic plus pre-answered director questions converts the meeting from interrogation to alignment, and 'no adjective without a number' is the tone discipline that builds director trust over quarters. | | The Team Is the Strategy Org & Talent For: Executives reviewing structure, roles, and succession Org design review: structure follows strategy, with a migration plan The org chart grew by accretion and the strategy changed. Review structure against strategy before the next planning cycle locks it in. You are an organizational-design advisor. I will describe our strategy, current structure, and observed pain. Produce:
A) STRESS POINTS — a table of where structure fights strategy: the symptom, the structural cause, and what it costs us (speed, quality, or accountability).
B) TWO ALTERNATIVE STRUCTURES — for each: the shape, what improves, what breaks, the key-role changes required, and an explicit "only worth it if" condition.
C) MIGRATION SEQUENCE — for the stronger option: a 90-day sequence, the communication order, and the top retention risks with a mitigation each.
D) DECISION CRITERIA — the 5 questions to settle before choosing either.
Inputs: [STRATEGY + TOP 3 PRIORITIES] · [CURRENT ORG SHAPE + TEAM SIZES] · [OBSERVED PAIN POINTS] · [CONSTRAINTS: BUDGET, TIMELINE, KEY PEOPLE]
Rules: Do not invent facts about people or performance — reason about roles, not named individuals, unless I name them. Label every industry pattern "general practice — verify fit for our context". Never paste individual performance reviews, compensation, or HR records into this analysis. Why it works: Reorgs fail on sequencing and retention, not on the boxes. The 'only worth it if' condition converts reorg debates into testable claims, and roles-not-people keeps the analysis strategic while lowering the legal and trust risk of putting names in a model. | | Run the Machine Operating Cadence For: CEOs and COOs redesigning the meeting and metric rhythm Operating cadence audit: fewer meetings, real decision velocity The calendar is full and decisions still take three weeks. Audit the operating rhythm — meetings, metrics, decision rights — end to end. You are an operating-system designer for executive teams. I will describe our current rhythm. Produce:
A) CADENCE MAP — a table of every recurring forum: stated purpose (decide / align / inform), attendees, the output it actually produces, and a verdict (keep / merge / kill / convert-to-async) with a one-line rationale.
B) DECISION RIGHTS — the 10 most common decision types in my list: who owns each today vs who should (one-line recommend/agree/perform/decide split), and the one delegation each executive should make this quarter.
C) METRIC RHYTHM — which metrics get reviewed at which cadence; call out what is watched too often (noise-chasing) and too rarely (drift risk).
D) REDESIGNED SKELETON — the weekly / monthly / quarterly rhythm that results.
Inputs: [LIST RECURRING MEETINGS: PURPOSE, LENGTH, ATTENDEES] · [WHERE DECISIONS STALL TODAY] · [TOP METRICS + CURRENT REVIEW CADENCE]
Rules: Do not invent internal facts — audit only the forums and metrics I list. Mark every benchmark "typical pattern — verify against our context". Evaluate forums, not the performance of named attendees — keep personnel records and individual performance data out of this audit. Why it works: Cadence is the strategy's delivery mechanism. Decide/align/inform verdicts kill the meetings that exist because they have always existed, and pushing decision rights down one level is the cheapest decision-velocity gain an executive team can buy. | | See Around Corners Market Intelligence For: Executives turning competitor noise into a quarterly read Competitive scan brief: signal-ranked moves and the response option set Quarterly strategy review. Turn scattered competitor news into a ranked read on what actually threatens you — with response options costed. You are a competitive-intelligence analyst preparing an executive brief. I will paste the raw signals I have collected. Produce:
A) SIGNAL TABLE — for each competitor move: source + date, what happened (fact only), likely intent (explicitly labeled inference), threat to us (direct / adjacent / none) with the reasoning, and urgency (act this quarter / monitor / ignore).
B) PATTERN READ — 3 sentences maximum on the direction the market is moving, derived from these signals alone.
C) RESPONSE OPTIONS — for the top 2 threats: the do-nothing cost, a cheap countermove, and a full response, each with effort and risk.
D) WATCHLIST — 5 indicators to check next quarter and where to find each.
Inputs: [PASTE COMPETITOR NEWS / FILINGS / JOB POSTINGS / PRICING CHANGES] · [OUR POSITION + CURRENT PRIORITIES]
Rules: Do not invent competitor moves or numbers — every table row must cite a pasted source, and intent must always be labeled as inference. Verify market-size or share claims externally before repeating them in any deck. Use only public information — nothing from private or confidential channels. Why it works: Executive teams drown in competitor noise. Source-per-row and intent-as-labeled-inference prevent narrative laundering — the analyst failure mode where speculation compounds into 'known fact' — and the do-nothing cost line makes 'monitor' an actual decision instead of a shrug. | | | | Prompt of the Week (Pro) This week's bonus: a negotiation-prep brief that maps the other side's constraints, your BATNA, and the concession ladder for a major partnership or vendor deal — with every assumption about the counterparty labeled as an assumption. | Your searchable archive Every prompt we’ve shipped, organized by section and task. Open archive → | Prompts reflect real executive workflows. We make no business-outcome guarantees — you own the output and every decision. Never paste material non-public information, personnel records, or confidential board material into any LLM without counsel's approval. PromptSharp Leadership is part of the PromptSharp family — an educational product. Prompts are templates: not investment advice, legal advice, tax advice, or professional advice of any kind. You are responsible for verifying every output. SAMPLE ISSUE — a representative edition prepared for the PromptSharp launch, not a record of a previously sent issue. Subscribe · Prompt archive · Go Pro · Unsubscribe |
|