Last time, we looked at a proposal that had been sitting unanswered for six days.
Instead of sending another “just following up…” message, we looked for the questions and gaps that might be slowing the decision down.
This time, the proposal got approved.
Fast, even.
And that’s where the next problem started.
Two weeks later, it turned out the approval depended on a number nobody had actually checked.
The hard part wasn’t getting a yes.
The hard part was what happened after the yes.
The better move was to separate the decision from the facts behind the decision.
Before treating an approval as final, check what the decision depends on.
🔴🟡🟢 COPY THIS INTO CHATGPT OR YOUR AI TOOL:
Act as my project verification officer.
Review the approved proposal and the source information below.
Identify the 3 most important facts, numbers, assumptions, or dependencies that the
decision depends on.
For each one, show:
- What the decision depends on
- Where the information came from
- What still needs to be verified
Rules:
- Do not assume something is correct because it was approved.
- Do not invent missing information.
- Flag anything that cannot be verified from the source.
- Prioritize the items that could materially change the decision.
Proposal and source information:
[paste your proposal and source information here]
