Quick answer: Replace daily standup with a 2-minute async video per person posted into Slack or Linear. Each person records once a day with their face, screen, and voice; the team scans the thread instead of sitting in a 15-minute call. The full 2-minute format and 30-day pilot plan are below.

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 is standup 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 use 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.

What is the 2-minute async standup 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.

How does the async standup workflow look 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 does async standup preserve?

  • 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 does async standup lose?

  • 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.

What are common objections to async standup?

"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.

How do I run a 30-day async standup 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).

What tools do you need to run async standup?

  • 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.

Frequently asked questions

Does async standup work across time zones?

Yes — it’s arguably better. Each person records during their working hours, so nobody loses sleep for a sync call. Set a soft window (e.g., “post by 11am your time”) so the thread is reasonably current when the next person reads it.

How do you keep engagement high without a meeting?

Two patterns work. First, react with emoji or a one-line reply on every video so people know they were watched. Second, surface unblocks: when someone says “blocked on X,” the unblocker replies in the same thread within an hour. The thread becomes the social proof that async actually moves work forward.

Should this replace 1:1s and project syncs too?

No. Async standup replaces the daily status sync. 1:1s, retrospectives, and product/design discussions still benefit from being live because they involve back-and-forth, conflict, or creative work. Use async for what async is good at — status broadcast.

Do I need a paid tool to do this?

No. Clipy is free with no recording cap and no watermark, which removes the usual reason async standup pilots fail (“you hit a 5-minute cap or a 25-video lifetime limit”). You can also use any other recorder; the format matters more than the tool.

What if a blocker is urgent?

Anything urgent shouldn’t wait for standup, async or otherwise. Default to a Slack DM or a quick 5-minute live call when something is on fire. Async standup is for the everyday “here’s where I am, here’s what’s next” rhythm.


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.