The weekly status email has a 100% send rate and, rounding generously, a 30% read rate. Then Tuesday's "quick question — where are we on the homepage?" proves the client never opened it. The conclusion isn't that clients don't care about status. It's that the update answered questions nobody asked.
Photo: Adikos, CC BY 2.0
What a client actually wants to know
Strip every status ritual down and clients have four questions:
- Is anything blocked on me? (the only one they'll act on today)
- Are we on schedule? — yes/no, then the honest date if no
- What changed since last time? — shipped, started, decided
- What do you need from me next?
Anything else — task counts, sprint ceremonies, percent-complete bars — is your internal bookkeeping leaking into their inbox.
Form follows attention
Send it where they already read (their chat, not your portal), keep it under 100 words, lead with the blocked-on-you item, and use their vocabulary — "the payment page", not "GAV-782". If a client can't act on an update in the thirty seconds they give it, the update failed.
Stop writing them by hand
Everything in those four questions is derivable from a live board — which means the update can be generated, not written, and sent on rhythm or on demand. That's the difference between a report and a pulse: when the client asks "where are we?" at 4pm Sunday, the answer comes from live data in their own chat thread, instantly.
The PM's hour of Friday email-writing becomes a two-minute review of a draft — or nothing at all for routine weeks. That hour, times every project, times every week, is where the AI-PM math starts paying.
← All posts