What this covers
The pain: Friday afternoons disappear into a status update that takes 90 minutes to write and 8 seconds to read. This workflow compresses the writing to about 15 minutes by letting AI handle the boring 80% — bucketing, drafting the TL;DR, surfacing under-discussed items — while you keep the parts a human has to write: the judgment call and the ask. Output is a one-screen update that your skip-level forwards instead of skims.
Who this is for
PMs, eng managers, ops leads, and founders sending weekly or biweekly project status updates. Especially useful if you ship across more than one workstream and have an executive reader who only opens the first paragraph. It also works for individual contributors writing manager-readable updates, with the bucket labels shrunk to “did / blocked / next”.
When to reach for it
When updates start feeling like a tax: you copy last week’s doc, change three numbers, paste in a Linear screenshot, and ship. Or when readers stop replying — a sign they have stopped opening it. Also any time the team grew past ~6 people and informal Slack updates no longer scale. Skip it if the project is in crisis mode; in crisis, you write the update by hand and you write it daily.
Before you start
- Pick the single audience: skip-level manager, cross-functional partner, or exec. Each wants a different lead sentence.
- Gather the raw inputs in one place: commit messages, Linear or Jira tickets closed this week, Slack threads worth surfacing, customer or support notes.
- Decide the format up front — Notion doc, Slack post, or email. Length cap is one screen on the reader’s device.
- Have last week’s update open so you can name what changed (the “delta” is what readers actually want).
- Keep raw data out of the AI prompt if you are in a regulated org; replace customer names with role tags.
Step by step
- Dump raw inputs into AI: this week’s merged PRs, closed tickets, Slack thread summaries, customer escalations. Plain bullets are fine.
- Ask AI to bucket into five lanes: shipped, blocked, on-track, at risk, next-week. Tell it to deduplicate and to drop trivial items.
- Ask AI to draft a one-paragraph TL;DR — 4 sentences, plain language, no buzzwords. Reject anything containing “leverage”, “synergy”, or “momentum”.
- Ask AI to surface one risk that is under-discussed in the raw data and one win that is under-celebrated. This is where AI earns its keep.
- Manually edit and add the “one human sentence”: your opinion, your call, your ask. Format it as
Ask: I need X by Y from Z. This is the only sentence the skip-level actually reads. - Format check: TL;DR on top, bucketed bullets in the middle, ask line at the bottom. Cut anything past one screen.
- Send before 4pm Friday. Save the inputs and the working prompt as next week’s template.
First-run exercise
Run this on a low-stakes week first so you can see where AI helps versus hurts before it matters. Take last week’s already-shipped update and a fresh batch of raw inputs. Run the full prompt chain end-to-end without editing, then diff the AI output against what you actually wrote last week. Mark each section: usable as-is, needs light edit, or wrong. Most teams find AI nails the bucketing and TL;DR but invents momentum that does not exist — that becomes the section you always edit. For the second run, change only one variable: usually the bucket labels or the audience tag.
Quality check
- TL;DR test: read only the first paragraph. Does a reader who knows nothing understand what shipped, what is at risk, and what you need?
- Number audit: every metric, date, and percentage in the draft must appear in the raw inputs. AI will round, smooth, and occasionally fabricate.
- Risk honesty test: would you say this sentence out loud in front of the at-risk team? If not, rewrite it.
- Length test: one screen on a phone. If it does not fit, cut the on-track section first — readers assume on-track if you do not mention it.
- Voice check: read it aloud. If it sounds like a press release, the human sentence is missing.
How to reuse this workflow
- Save the bucket-labels prompt, the TL;DR prompt, and the risk-surfacing prompt as three separate saved messages. Each is a one-line tweak per project.
- Keep a
status-update/folder with a dated copy of inputs and outputs. After 4 weeks, the deltas across weeks become your quarterly review. - Build a fixed checklist: inputs gathered, AI draft generated, numbers fact-checked, human sentence added, format trimmed, sent before 4pm.
- Every 4 to 6 weeks rerun the AI prompt without your edits and compare. If AI output is converging with yours, your prompt is mature; if diverging, the model or your project changed.
- Share the prompt with one peer. Their edits will surface biases in your phrasing that you cannot see.
Recommended workflow
Raw inputs → AI bucketing → AI TL;DR → AI surfaces under-discussed risk and win → human sentence with the ask → trim to one screen → ship by 4pm Friday → archive inputs and prompts for next week.
Common mistakes
- Sending AI’s draft verbatim — the cadence and word choice tip readers off within two sentences.
- Burying the ask in the middle of a bucket. Skip-level scrolls to the last line; put the ask there.
- Omitting risks because they are uncomfortable. A status update with no risks reads as either lying or asleep.
- Letting AI invent momentum that has not happened. If the prompt was “make it sound positive”, you got fiction.
- Writing for everyone. Pick one reader and write to them; cc the rest.
- Skipping a week because “nothing happened”. Cadence is the trust signal; send four sentences and the ask anyway.
FAQ
- What if there is genuinely nothing to report?: Send four sentences anyway: what shipped, what is blocked, what is next, and one ask. Skip-level reads the absence of an update as project death.
- Should AI write in my voice?: No. Have AI draft factually and neutrally. You add voice in the human sentence and the ask line — that is enough to sound like you.
- My company blocks ChatGPT. Workaround?: Use the on-prem or enterprise tier, or run a local model on a sanitized inputs file. The prompts in this workflow are short enough that a 7B local model handles them.
- How long should the TL;DR be?: Four sentences, max 60 words. If it does not fit, the project is too broad for one update — split into two.
- What about a status update for a project that is on fire?: Skip AI. Write it by hand, daily, with a named owner per risk. AI is for steady-state, not crisis.
- Can I use this for an upward 1:1 update instead of a team-wide one?: Yes, but shrink the bucket count to three: progress, blockers, asks. The TL;DR becomes a single sentence.