Updated April 26, 2026.

The daily standup is the most reflexively defended meeting in software, and the easiest one to replace. This is the playbook for swapping a 15-minute live standup for a 2-minute async video — without losing the things standup is actually good at.

What standup is actually for

Standup answers three questions:

  1. What did I do yesterday?
  2. What am I doing today?
  3. What's blocking me?

Notice none of these require a synchronous meeting. They require visibility and a place to surface blockers. Live standup is one way to do that. Async video is another, and it's much cheaper for teams in two or more time zones.

Why video and not text

Plenty of teams replace standup with text in Slack. It works, but it loses two things:

  • Tone. "Blocked on the auth migration" in text reads as a routine update. The same line on video, with a sigh and a screenshot of the failing build, reads as "help me, this is bad." Engineers under-flag blockers in text.
  • Showing. A 30-second screen share of yesterday's progress is more informative than three bullets describing it.

Video keeps the tone and lets you show. Text keeps it searchable. The right answer is usually video for the update + text caption with the headline + link.

The 2-minute format

  1. 30s — yesterday. Show the PR, the failing test, the design doc — whatever you actually worked on. Narrate in one breath.
  2. 30s — today. What you're picking up. If it's the same task as yesterday, say so and explain why.
  3. 30s — blockers. Be explicit. "I'm blocked on @sarah's review of #402." If nothing's blocking you, say nothing's blocking you.
  4. 30s buffer. If you go over because the bug is interesting, fine. Don't pad to fill time.

Two minutes max. If you're hitting four minutes regularly, the standup is hiding a bigger problem — it should be a longer post or a 1:1.

The workflow with Clipy

  1. Open clipy.online first thing in the morning.
  2. Click record. Pick the tab or window with the actual work (PR, design, doc).
  3. Hit record, run through yesterday/today/blockers, stop.
  4. Paste the clipy.online link in #standup with a one-line caption: "@here Yesterday: shipped 402. Today: starting 415. Blocked on Sarah's review of 408."
  5. Watch your teammates' standups in any order, on your schedule.

Total time per engineer: 2 minutes recording + 5 minutes watching the team = 7 minutes. The live standup it replaces was 15 minutes for everyone, plus context-switch overhead.

What this preserves

  • Visibility. Everyone still knows what everyone's working on.
  • Blocker surfacing. The format forces you to name them out loud.
  • Tone. Easier to spot "this engineer is stuck" in voice than in text.
  • Searchability. The text caption gives you grep; the video gives you depth.

What this loses

  • Spontaneous coordination. Two people realizing in real time they're working on the same thing. Mitigation: a single shared status doc that updates as standups land, or a dedicated #pairs channel.
  • Hallway moments. Standup is sometimes the only time the team sees each other. Replace this on purpose with a weekly 30-minute "social standup" that has no agenda.

Common objections, addressed

"We need standup for accountability."

You need visibility, not accountability theater. Async video posted to a public channel gives the same signal: did this person check in, did they say what they were doing? The signal is stronger if it's archived and timestamped.

"What about people who don't speak English natively?"

Async video is friendlier. Recording lets you re-take. Live standup penalizes anyone who needs an extra beat to formulate. Several distributed teams cite this as the main reason they switched.

"What about the team in the same office?"

Even fully co-located teams benefit from skipping standup and using a shared async post. Standup is a poor use of synchronous time when everyone is already pinging each other in Slack all day.

30-day pilot

Don't argue about it. Run it for 30 days.

  1. Pick the team. Tell everyone "we're trying async standup for 30 days."
  2. Pick the format above. Don't bikeshed it.
  3. Cancel the live standup for those 30 days.
  4. At day 30, ask the team: keep, kill, or modify? Ship the answer.

Most teams keep it. The ones that don't usually find a hybrid (async 4 days, live 1 day for cross-team coordination).

Tools

  • Recording: Anything that gives you a fast share link. Clipy is free and works in the browser. Loom works too if your team already pays for it.
  • Posting: Slack thread, Linear update, Notion page, or whatever your team uses. The recorder is agnostic.
  • Watching: Browser. No extra app required for any modern recorder.

Try Clipy free. One-click screen recording in your browser, instant share link, no watermark, no time limit, no sign-up to watch. Start recording at clipy.online — or download the desktop app for system-audio capture.