Strip the ritual away and the daily standup answers exactly three questions: what changed since yesterday, what’s blocked, and what happens next. The meeting exists because the team has no cheaper way to answer them. It’s a workaround for 24-hour information latency.
Which reframes the whole debate. The problem was never “meetings are bad.” The problem is that for most teams, the only place work becomes visible is a person’s mouth, once a day.
The cost isn’t the 15 minutes
Everyone knows the standup isn’t 15 minutes. It’s the context switch before it, the “quick question” after it, and the dead zone on either side where nobody starts anything deep because the meeting is coming. The standard estimate is an hour of focus per person, per day — for a six-person team, a full working day of attention spent weekly on reporting work instead of doing it.
But here’s the subtler cost: latency hides problems. A blocked PR on Tuesday morning becomes spoken information on Wednesday morning. That’s a day of someone waiting who didn’t need to wait. Multiply by every blocker, every week.
What kills the meeting
The standup dies when its three questions answer themselves:
- What changed? — the commits and merges, visible on the board the moment they happen.
- What’s blocked? — the PR that’s been open three days, the CI run that’s red, the card with no activity. Visible, not reported.
- What’s next? — the top of the list, which was already there.
None of this requires new discipline. The team already produces all of it — in GitHub. It just lives in the wrong place, so someone has to transcribe it into speech every morning.
What replaces the meeting
Not another meeting, and not a wall of Slack messages nobody reads. The durable replacement is a board that reads status from the work itself: commits, PRs, and CI streaming in next to the tasks they belong to. People write a note when judgment is needed — a decision, a surprise, a real blocker — and stay silent when the artifacts already say it. Most days, the artifacts say it.
That’s the bet behind Kahoona: point it at your repo and the board fills with live GitHub activity next to your tasks, so “what changed since yesterday” is a thing you can see, not a thing you have to schedule.
👉 Kill your status meeting — free to start
Related: How to run async standups from your GitHub activity · Jira shows tickets, not truth