Standups exist for two reasons: visibility (what is everyone working on?) and unblocking (who needs help?). Both are real. But neither requires synchronous attendance.
This is the playbook we use, and the one we’ve watched a dozen other teams adopt successfully.
The case against the daily live standup
Live standups have hidden costs:
- Attendance tax. Even a 15-minute standup eats 30+ minutes once you account for context-switch and “wait, am I on mute” overhead.
- One pace for everyone. Fast updates feel rushed. Slow updates burn the room. Async lets each person set the pace per item.
- Time zone bias. Someone is always inconvenient. The same someone gets used to it.
- Recency bias. Whoever talked last is what people remember. Async lets each update stand alone.
We’re not arguing for “no standup.” We’re arguing for the same standup, recorded once, watched on each person’s clock.
The 90-second template
Three sections. Stick to time. The whole thing runs under two minutes:
1. Yesterday (~30 seconds)
What you actually finished. Not “worked on” — finished. If something is half-done, save it for “today.”
“Yesterday I shipped the email-export endpoint. Wrote the migration, added tests, deployed it. Hooked it into the dashboard’s Settings page.”
2. Today (~30 seconds)
What you’ll have done by EOD. One or two things, max.
“Today I’m finishing the Stripe webhook for the same flow. Goal is to send a receipt email when a subscription renews.”
3. Blockers / asks (~30 seconds)
Specifics, not vibes. “I’m stuck on auth” is not a blocker. “I need someone to review PR #482 before I can merge” is.
“I need a five-minute pairing on the webhook signing. @dani if you have time today, ping me. Otherwise I’ll figure it out tomorrow.”
If you have nothing to ask, just say so and stop.
What to put on screen
The recording is more useful with a screen than without. Pick one of three modes:
- Code or PR. If your update is a code change, scroll through the diff while you talk.
- Dashboard / Linear board. Walk through the cards you’re moving today.
- Just camera. Sometimes there’s nothing to show. That’s fine. A 60-second talking-head clip still beats text.
The mistake is over-producing. This isn’t a presentation; it’s a status update.
If your standup recording takes more than three minutes to make, you're doing more than a standup. Either trim or send a separate "deep dive" recording.
Where to post it
Pick one place. We’ve seen each work:
| Channel | When it works |
|---|---|
| Slack #team channel, threaded | Default. Inline preview, threads for follow-ups. |
| Linear / Notion / project doc | Updates live next to the work. Good for product teams. |
| Loom team page | If everyone already has Loom. Comment per video. |
| Internal RSS / digest | For larger orgs. Aggregated daily email. |
The mistake is posting in three places to “make sure everyone sees it.” Pick one. Trust people to check.
What you give up
A few real costs:
- Spontaneous unblocking. Live standups occasionally produce “oh, I just hit that — let me show you” moments. Async doesn’t. Mitigation: a 30-min weekly “office hours” call where the team can show their work and pair.
- Newcomer onboarding. New hires use the live standup to learn names and context. Mitigation: pair them with a buddy for the first two weeks; loop them into a few specific recordings.
- The team-bonding ritual. Live standup is sometimes the only time the team is together. Mitigation: a weekly social call. Not a standup — actual unstructured time.
If those mitigations sound expensive, async standups are not for your team. That’s OK. The point is to be honest about the trade-off.
Tools
You need three things:
- A fast recorder. Hotkey, talk, stop, paste link. We built Zenguy for exactly this — a 90-second clip should take 95 seconds end-to-end.
- A shared place to post. Slack channel, Notion page, whatever. Convention matters more than the tool.
- A signal someone watched it. A 👀 reaction, a quick reply, an emoji-flow. Not analytics — just the human “I saw this.”
If you’re already on Loom, that works fine. If you want to keep your clips on your machine and not in another company’s cloud, Zenguy vs Loom has the comparison.
A 30-day trial plan
If your team is on the fence, run a structured trial:
- Week 1: Replace one of five standups with async (Wednesday is good — middle of the week, not weekend-adjacent).
- Week 2: Replace three.
- Week 3: Full async, with a Friday wrap-up call.
- Week 4: Retro. What did people miss? What did they reclaim?
Most teams discover by week 2 that they don’t miss live standup at all — they just need the Friday social call. Some teams discover the opposite. Both are valid; you can’t know without trying.
Make recording your standup take 95 seconds
Zenguy gives you a hotkey, a 90-second clip, and a shareable link. No upload step, no platform tax. Free forever on Mac.