Flag unstated project assumptions before kickoff
Surface hidden assumptions about resources, data access, and vendor dependencies before projects stall mid-flight.
You getExecutive Summary of Risk Exposure, table of Hidden Assumptions and immediate Pre-Kickoff Actions
Prompt
Act as a project risk manager. Analyze the project kickoff brief or scope notes below to identify unstated assumptions, hidden dependencies, and blind spots that could derail delivery.
Rules:
- Identify assumptions that are implied but not explicitly promised or contracted.
- Focus on technical access, data quality, client response times, and third-party dependencies.
- Assign each finding a plain likelihood-and-impact rating (Low, Medium, High).
- Provide one specific validation question to ask stakeholders for every flagged assumption.
Output format:
- Executive Summary of Risk Exposure (2 sentences)
- Table of Hidden Assumptions (columns: Category, Unstated Assumption Detected, Risk Level, Validation Question to Ask)
- Immediate Pre-Kickoff Actions (3 bullet points prioritizing what to confirm before day one)
Here is the project material:Example output
Paste your project charter, client brief, or kickoff slide text after the prompt in ChatGPT, Claude, or Gemini. Follow up by asking the model to draft an email to the client sponsor seeking clarification on the highest-risk items.
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
Draft a one-page project kickoff brief
Turn fragmented launch details into an aligned single-page kickoff document. Ideal for aligning cross-functional teams before delivery starts.
Review a project schedule for bottlenecks
Spot fragile dependencies, compressed testing buffers, and optimistic estimates hidden inside a draft project schedule.
Audit project estimates for hidden optimism bias
Spot hidden assumptions, under-budgeted handoffs, and optimistic delivery timelines within detailed project task breakdowns.
Extract continuous phase-gate lessons from sprint notes
Identify recurring delivery risks and early project friction from sprint summaries before problems get buried at the final closeout.
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 project risk trigger matrix
Define measurable threshold indicators and immediate response owners before risks become active problems. Use it during project kickoff or sprint planning.