Last time, we tried to turn messy project information into a clean leadership update.
You had 47 minutes.
Stale Jira.
Messy notes.
Slack noise.
Leadership wanted a clean update — fast — and they wanted it to be true.
Here’s what we learned.
The hard part wasn’t writing the update.
The hard part was figuring out what was actually true before writing it.
The notes were incomplete.
Ownership was unclear.
The information existed — but it was scattered across Slack, meeting notes, Jira, and half-finished conversations
The people who got the best results did not start by asking AI to write.
They gathered the information first.
They separated what they knew from what they were assuming.
Then they asked AI to help write the update.
That one change mattered more than finding a clever prompt.
🔴🟡🟢 COPY THIS INTO CHATGPT OR YOUR AI TOOL:
Act as my project verification officer.
From the notes below, create a table with three columns:
- Claim one sentence
- Source the exact line or phrase it came from
- Status - CONFIRMED / UNCLEAR / MISSING
Rules:
- If a claim isn't directly supported by something in the notes, mark it UNCLEAR.
- If there is no clear owner or date, mark it MISSING.
- Don't guess or fill in gaps.
Notes:
[paste your notes here]
