Write an executive briefing to unblock approvals
Turn stalled decisions into clear executive briefings that present trade-offs, financial impacts, and a default action path to secure quick sign-off.
You getSubject Line, the Decision Needed and cost of Delay
Prompt
Act as a project manager writing a high-impact decision briefing for a busy executive project sponsor. Review the project hurdle details provided below.
Rules:
- Limit the briefing to under 300 words total.
- State the required decision and the exact date needed in the very first sentence.
- Define the direct business impact of inaction (cost per day, missed milestone, team idle cost).
- Provide two realistic paths forward plus a clear recommended default choice.
- State explicitly what will happen automatically if no response is received by the deadline.
Output format:
- Subject Line: Action Required, then a short, urgent descriptor
- The Decision Needed (1 sentence)
- Cost of Delay (2-3 bullet points with hard facts)
- Options Considered (Option A vs Option B with trade-offs)
- Recommended Action & Default Next Step
My project context, bottleneck, and options are below:Example output
Paste your project issue, delayed decision, and notes after the prompt in ChatGPT, Claude, or Gemini. Ask the model to adjust the tone if your sponsor prefers extreme brevity or needs more technical context.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build an executive steering committee deck outline
Turn project updates into a concise executive deck structured around key decisions, milestones, and trade-offs. Use it before leadership reviews.
Diplomatic pushback against scope creep
Draft a polite, professional response that acknowledges an out-of-scope request, explains project tradeoffs, and offers clear paths forward.
Translate technical blockers into business impact updates
Turn technical bug notes and engineering blockers into concise, executive-ready updates focused on cost, schedule, and next actions.
Identify silent stakeholders before locking requirements
Uncover hidden reviewers across security, compliance, legal, and IT before scope freezes. Use this during early discovery to prevent late launch blocks.
Create a stakeholder matrix and communication plan
Map project stakeholders by power and interest to design a targeted communication cadence that prevents noise and missed updates.
Analyze timeline and budget trade-offs for scope requests
Turn vague stakeholder feature requests into clear trade-off scenarios. Use this when clients or leaders request additions without considering cost or delay.
- Create a shared milestone alignment brief across teams
- Draft a formal deliverable sign-off request email
- Present scope trade-off options to demanding clients
- Turn engineering updates into marketing launch timelines
- Build a phase-gate exit checklist for project approvals
- Create a formal scope change request