Last time, the plan looked ready.
Three unconfirmed assumptions were quietly holding the whole thing together.
The problem wasn’t that assumptions existed.
The problem was that nobody knew which ones mattered.
Here's what we learned.
An obvious guess usually gets questioned.
Nothing sounds obviously wrong.
So nobody stops to check.
Until the assumption becomes the problem.
The useful move was simple:
Name the assumption before deciding what to do about it.
🔴🟡🟢 COPY THIS INTO CHATGPT OR YOUR AI TOOL:
Act as my project risk officer.
Review the plan below and identify the assumptions it depends on.
For each assumption, rate:
- Risk if wrong: High / Medium / Low
- Confirmation status: Confirmed / Unconfirmed
Then flag the assumptions that are High risk + Unconfirmed.
For each flagged assumption, explain:
- What the plan depends on
- What needs to be confirmed
- What could change if the assumption is wrong
Rules:
- Do not invent missing information.
- Do not mark something Confirmed without support in the material provided.
- Prioritize assumptions that could materially affect time, cost, scope, quality, or delivery.
Plan:
[paste your plan here]
