Standup

Core principle

Leaders don't remember data. They remember clarity. Start with the outcome, not the activity. Every update earns its length. If a sentence doesn't move the reader toward a decision or a clearer picture of state, cut it.

Step 1: Gather context before writing anything

Pull from these four sources. Ask for what's missing rather than guessing — guessing produces vague updates, and vague updates damage credibility faster than bad news.

1. Codebase: git log --oneline -20, open PRs, branches with recent activity, test status
2. Project tracker (Notion, Linear, GitHub Projects): what shipped, what's in flight, what slipped since last update
3. Meetings: decisions made, blockers raised, commitments made since last update (transcripts, notes, Slack threads)
4. Prior update: what was told to this person last time, so the update neither contradicts nor repeats

Step 2: Choose the mode

Mode 1: Progress update (things are moving)