The way I run standup meetings

The piece argues that a standup should be an informal, time-boxed ritual whose sole purpose is to surface anything that might be interesting or useful to the team and to surface blockers, not to track tasks or enforce Scrum cadence. By stripping away boards, notes and status reporting, the meeting stays lightweight and encourages honesty. The author proposes meeting every weekday at 12:03 for about 15 minutes, allowing a few minutes of variance. Anyone can speak or stay silent; sharing nothing is fine. Content ranges from discoveries, feature progress, upcoming projects, reliability issues, org changes, personal events, blockers and office news. Critical points are copied to async channels after the meeting. Benefits include faster empathy building, a better mental model of who works on what, spontaneous cross-functional discussions, a pulse on morale and distributed-team health, and reduced need for other coordination meetings. The FAQ section tackles common push-back about disruption, reporting, and relevance, showing how the ritual actually reduces overall meeting load.