Last time, the project looked fine.
Until we looked closer.
A task had slipped.
A dependency wasn’t moving.
A response was taking longer than expected.
The warning signs weren’t dramatic.
They were small.
So we turned them into a short list:
Ignore.
Watch.
Act Now.
But there was still a problem.
One of the warnings was:
“I’m worried about the timeline.”
Everyone heard it.
Nobody owned it.
A week later, the timeline was the problem.
HERE’S WHAT WE LEARNED.
Those statements may be true.
But what is someone supposed to do with them?
Which part is at risk?
Since when?
What needs to happen?
Who needs to act?
Without those details, the warning stays a feeling.
And feelings don’t have owners.
The useful move was turning the warning into something concrete.
Instead of:
“I’m worried about the timeline.”
We could say:
“The design review has been waiting since Monday. If Product doesn’t confirm the direction by Thursday, Friday’s build is at risk. Sarah needs to confirm the direction.”
Now there is something to act on.
🔴🟡🟢 COPY THIS INTO CHATGPT OR YOUR AI TOOL:
Act as my follow-up coordinator.
Review the warnings below and turn each one into a clear action.
For each warning, identify:
- What's at risk
- Since when
- Who needs to act
- What they need to do
- By when
Rules:
- Do not invent an owner or deadline.
- If an owner is unclear, mark [OWNER NEEDED].
- If a deadline is unclear, mark [DATE NEEDED].
- Keep each warning to one or two sentences.
- Separate evidence from interpretation.
Warnings:
[paste your warnings here]
