Deliver clarity-first status updates that land

Deliver clarity-first status updates that earn decision or awareness, not fluff

Engineers and PMs who need to keep leadership informed without writing essays, and want their updates actually read instead of skimmed (because every sentence moves someone toward a decision or clarity).

• · Current project state (git log, PR status, test results)
• · Decisions made since last update (from meetings, notes, Slack)
• · Work in flight vs shipped vs slipped
• · Any blockers or decisions needed

• · One-line outcome / current state
• · Reasoning (what drove that, what data shows, what changed)
• · Next step + timeline
• · Explicit ask: 'Nothing needed' OR 'Need decision on X by [date]' OR 'Want your read on Y'

• · Gather data from 4 sources (git, tracker, meetings, prior update) before writing
• · Know whether mode is 'progress' (on track) or 'blocker' (decision needed)

• · Update is all activity, no outcome (shipped code ≠ user value)
• · Asks are vague ('check back in later' instead of 'need decision by Thursday')
• · Blocker mode presents 3+ options instead of exactly 2 (means thinking isn't done)

• · Hard ceiling: 5 sentences max for Slack, 150 words for email, 30-45 seconds spoken
• · Outcome first, then reasoning, then next — not chronological narrative
• · Mandatory explicit ask at end (removes ambiguity about what role leader plays)
• · Blocker mode: exactly 2 options + lean stated + decision deadline