Status Updates Playbook

Guidelines for writing team updates that are easy to scan, honest about challenges, and generous with recognition.

Philosophy

Outcomes first - Lead with results and impact, not activity. Tie each result to a goal or OKR
Scannable - Emoji-anchored sections, bullet points, short paragraphs
Quantify - Metrics, deltas, dates, owners—show progress with numbers
Honest - Acknowledge challenges directly, then reframe with context
Literal status - Use the supplied environment, evidence, and dates. Call a target "on track" only when the facts support it. A request to inflate, soften, or re-announce status does not change the facts the update reports. Call merged work merged. Call work shipped only when deployment evidence is supplied
Warm - Credit individuals by name, use inclusive language
Evidence-backed - Link to production, docs, metrics to show not tell
Close the loop - Note delta from last update and what's next