Free to read · no account needed

11 min · writing

Stakeholder update that gets read

Goal: Friday updates with traffic-light status + owned asks—facts yours, model only polishes.

Best for: Weekly updates to managers, clients, or cross-team stakeholders who skim on mobile.

Leaders do not need your diary. They need a traffic-light read: are we fine, are we delayed, and what do you need from them? AI is good at turning messy bullets into that shape. It is bad at inventing wins, owners, or dates you never said. Keep the facts yours.

Why beginners skip this

Leading with feelings then bolting on facts feels sincere—stakeholders need three decision lines. Facts first, then risk.

Step 1 — Steal a skim-friendly shape

Paste the empty win / risk / ask template every week. Fill brackets from *your* notes before you chat.

Audience: [manager / client / partner]
Project: [name]
Status color: Green / Yellow / Red — one sentence why
Wins (≤3): [fact bullets only]
Risks (≤3): [what could slip + earliest signal]
Asks (≤3): [person + decision + by when]
Boundaries: Max 150 words. No fluff openers. Do not invent metrics, owners, or dates.
Input notes:
[paste your raw bullets]

Step 2 — One worked week (API migration)

Example

Filled prompt

Audience: eng manager
Project: Checkout API migration
Status color: Yellow — cutover slipped 3 days; canary still green
Wins:
- Migrated read path for 40% of traffic
- Zero Sev-1 in canary week
Risks:
- Write path still on legacy; dual-write lag spikes at 18:00 HKT
- Two contractors end Friday unless extension approved
Asks:
- Approve 1-week contractor extension by Wed noon
- Confirm freeze window Thu 22:00–02:00
Boundaries: Max 150 words. No fluff. Do not invent % complete.

What good output looks like

  • Opens with Yellow + one honest reason
  • Asks name a person/decision/deadline
  • Stays under ~150 words; no “hope you’re well”
  • Does not invent a completion percentage you never gave

Step 3 — Kill the fluff before you send

After the draft, run one micro-pass: cut empty openers, fake greens, and any percentage you cannot point to.

Edit for skim only. Keep facts. Delete greetings, “just circling back”, and any metric not in my notes. Return the update + a 3-line “what I removed” list.

If the model adds a sunny Green when your notes said Yellow, reject it. Color is a judgment call—you own it.

Example

Filled prompt

Audience: product director (skims on phone)
Project: Mobile checkout beta
Status color: Yellow — internal beta live; public date blocked on design review
Wins:
- Internal beta live for staff cohort (n≈40)
- Crash-free for 3 days in canary
Risks:
- Public mobile date slips if design review misses Wed
- Copy freeze not signed by legal
Asks:
- Confirm design review Wed 15:00 with Mei
- Legal sign-off on freeze by Thu noon
Boundaries: Max 150 words. No fluff. Do not invent % complete or user counts beyond notes.

What good output looks like

  • Opens Yellow with the design-review blocker named
  • Asks name Mei + Legal with deadlines
  • Stays ≤150 words; no “hope you’re well”
  • Does not invent a public launch % or external user count
Example

Filled prompt

Yellow: API cutover +2 days; canary green.
≤3 wins/risks/asks with owners. ≤150 words. No invented % complete.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.

What good output looks like

  • Matches outline/voice freeze for “Send a short status leaders can skim in about one ”
  • No AI-slop openers; one concrete proof from your notes
  • Numbers/names frozen — polish does not invent
  • Pass/fail: phone-skim 20s still clear

Red flag

Unowned asks; invented metrics; model inventing status—traffic-light with your facts only.

Save this card

Card: Traffic-light status + owned asks—facts are yours; the model only polishes. Keep this beside the tool; read before you start.

Before you start

Name the reader and freeze facts on paper for “Send a short status leaders can skim in about.” If outline bullets do not exist yet, stop before prose. Guide: writing-stakeholder-update. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.

How to use this week

This week write a real update: progress / risk / ask in three lines each; move feeling sentences to the end or cut them.

Pitfalls

PitfallFix
Pasting a week of Slack and asking “summarize”Pre-sort into wins / risks / asks yourself
Letting the model invent “85% complete”Ban new metrics; only reuse numbers you typed
Three soft asks (“thoughts?”)Each ask needs owner + decision + date
Writing for yourself, not the skimmerRead it on your phone in 20 seconds
Example

Filled prompt

Temptation: skip the habit for writing-stakeholder-update to save five minutes.
Job still: Send a short status leaders can skim in
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.

What good output looks like

  • Names the shortcut refused (specific to writing-stakeholder-update)
  • Still delivers checkable output for “Stakeholder update that gets read”
  • Unknowns labeled; draft-only
  • Pass/fail: refuse-line dated (writing-stakeholder-update #4)

Practice now

Tonight write a real update: progress / risk / ask in three lines each; move feeling sentences to the end or cut them.

Tonight write a real update: progress / risk / ask in three lines each; move feeling sentences to the end or cut them.

Delta only: lead with what changed since last update (Asia/Shanghai).

Tonight write a real update: progress / risk / ask in three lines each; move feeling sentences to the end or cut them.

Tonight write a real update: progress / risk / ask in three lines each; move feeling sentences to the end or cut them.

Tonight write a real update: progress / risk / ask in three lines each; move feeling sentences to the end or cut them.

Risk line: one risk + mitigation or “none” (Asia/Shanghai).

Ask line: every update ends with one explicit ask or “no ask” (Asia/Shanghai).

Stakeholder drill: one update with decision-needed line + owner + date; no fluffy status (Asia/Shanghai).

Tonight write a real update: progress / risk / ask in three lines each; move feeling sentences to the end or cut them.

Close the loop

Write one line: next time I lead with feelings then bolt on facts, I refuse send.

One sentence takeaway

Progress / risk / ask three lines each; feelings to the end or cut.

Next

Outline before prose · Reject AI slop · Office weekly routine

← Back to home · Learn · Tools · Compare · Start