timer.new
← All posts
· 3 min read

Your standup is too long. Here's how to fix it.

A 9-person standup that 'should take 15 minutes' usually takes 35. The fix is a shared, visible timer.

The honest answer to "why does our 15-minute standup take 35 minutes" is that you don't have a 15-minute standup. You have a meeting that someone calls a standup.

A standup, original Agile-flavor, is three updates per person at ~30 seconds each. Yesterday, today, blockers. Nine people × 90 seconds = under 14 minutes. Plus a buffer = 15. The math works.

What breaks the math is the visible time pressure. There isn't any. Someone gets into a story about a flaky test, someone else asks a follow-up, suddenly two engineers are debugging in real time while seven other people listen.

The cheapest fix: a visible countdown that everyone in the meeting sees. Not a phone timer. Not a "I'll watch the clock." A real shared timer projected on the screen-share.

Open timer.new/t/standup, claim the name (Pro), set 10 minutes, hit start. Now everyone is watching the same number tick down. Behavior changes within one meeting. The flaky-test rabbit hole gets cut off because the person telling it can see they've used 90 of their 30 seconds.

This works because timers are an externalization of a social pressure that's hard to apply yourself. "Hey can we move on" is hard to say. A red countdown saying "0:43" is easy to point at.

Try the thing this post is about.