Writing a status update that doesn't need a meeting
What you'll learn
- Three sentences: shipped (outcome), blocked (specific + who), one improvement.
- Outcomes beat activities. 'Shipped login fix' beats 'worked on auth'.
- Specific help-asks unblock; vague ones invite another meeting.
A useful status update has three parts in order: what shipped (outcome, not activity), what's blocked (specific blocker + who you need help from), one thing you're doing differently next week (continuous improvement). Three sentences each, max.
What kills status updates: activity lists ('worked on auth, fixed bugs, attended meetings'), apologies for low output, and vague help-asks ('any thoughts?'). Each of these makes your manager schedule a clarification call you could have avoided.
Manager-side: read every update before the team meeting; ask clarifying questions in the doc, not in the meeting. The meeting is for blockers that couldn't be unblocked async.
Key points
- Three sentences: shipped (outcome), blocked (specific + who), one improvement.
- Outcomes beat activities. 'Shipped login fix' beats 'worked on auth'.
- Specific help-asks unblock; vague ones invite another meeting.
Examples
"Shipped login fix; cohort dashboard scoped (link). Blocked Friday on staging creds — Anita unblocked me Mon AM. Next week: batch creds requests Thu so block doesn't repeat."
Pitfalls
- Activity-only updates that force a clarification call.
- Apologising for honest output; manager loses the signal of where to help.
Ask your L&D team
In a real Adept rollout this routes to your company's L&D Claude project; in the demo it opens a fresh Claude chat.