# How to Run Async Video Standups

> **Category:** Workflow · **Date:** November 19, 2026 · **Read time:** 6 minutes

**URL:** https://screenrecord.in/blog/async-video-standups

A daily standup is a status report wearing a meeting costume. Most of it is one person talking while five people wait their turn. Async video keeps the useful part, the context, and drops the scheduling. Here is a format that survives contact with a real team.

## What async standups fix, and what they do not

Async updates work when the goal is information transfer: who is doing what, what changed, what is stuck. They fail when the goal is a decision that needs back-and-forth. Be honest about which one you are running.

- **Good fit** — distributed teams, several time zones, focused makers who lose an hour of flow to a 15-minute call.
- **Poor fit** — a team that needs a daily live triage, a new team still building trust, or an incident week where decisions change hourly.

You can mix them. Async on normal days, live when something is on fire. The rule is that the live call is the exception, not the default.

## The 90-second format

Every update answers the same three questions in the same order:

1. **What I finished** — one or two items, with the ticket or link.
2. **What I am doing next** — the thing you will actually work on, not the whole quarter.
3. **What is blocking me** — name the person or decision, or say "nothing".

Ninety seconds is the cap, not the target. A good update is often 40 seconds. The cap exists because a video is harder to skim than text; a five-minute video gets skipped, and a skipped update is worse than no update.

## Show the work, do not describe it

The reason to use video instead of a text post is context. Share the screen and show the thing:

- The ticket moving across the board
- The dashboard with the metric you are talking about
- The error in the console or the failing test
- The design file with the region you changed

A camera bubble helps people read tone and keeps the team human. It is optional for a solo update and useful for anything that involves a disagreement.

## Record it in one take

Do not script, do not re-record, and do not edit. A polished standup video is a sign that someone is spending 20 minutes on a status update. One take, rough edges, real information.

Open the recorder, pick the screen or the tab you want to show, add your microphone, and press record. Ninety seconds later you have a link. The whole habit should cost less than the meeting it replaces.

## Post in one place

Pick a single destination and keep it boring: one channel, one thread per day, one link per person. The archive is the point. Six weeks later, when someone asks "when did we change the retry logic", the answer is searchable.

- One thread per day, named with the date.
- Each person posts a link, not an attachment.
- Replies go in the thread, not in direct messages.
- Blockers get an owner and a next step, or they are not blockers.

## Respond in writing

The most common failure of async standups is that the videos go up and nobody watches them. Fix that with a small obligation: everyone reads the thread and answers anything addressed to them before their own update. Blockers are resolved in the thread, not in a new call.

If a thread turns into a real discussion, take it to a two-person call and post the outcome back. Do not let the standup thread become a slow-motion meeting.

## Watch what happens over a week

Friday is the moment to check whether the format is working. Skim the week of updates and look for patterns:

- The same blocker appearing three days in a row means the escalation path is broken.
- The same ticket appearing in "next" all week means it is too big or nobody is working on it.
- Updates getting longer means the format is drifting; restate the 90-second cap.
- Updates getting shorter and emptier means the team does not believe anyone reads them.

Fix the process, not the people. Adding a live call to police the videos defeats the purpose.

## Tooling that stays out of the way

You need two things: a recorder that produces a link, and a place to post it. Anything else is optional.

A browser recorder is the lowest-friction option because there is nothing to install and no seat licence to argue about. Team members on managed laptops, Chromebooks, or a borrowed machine can still post. If you want a Loom-style workflow without the per-seat cost, see our [Loom alternative guide](https://screenrecord.in/loom-alternative).

Viewer analytics are worth a look for the first month. If nobody opens the links, the problem is the format or the thread, not the recorder.

## Common mistakes

- **Making it mandatory viewing at 9am.** That is a meeting with extra steps.
- **Letting one person post 10-minute monologues.** Split the update or write the long version down.
- **Recording your whole desktop.** Share the tab or window; notifications are not status.
- **Skipping the blocker question.** It is the only part that changes what happens next.
- **No archive.** If the videos disappear after a week, the team will go back to chat messages.

## Conclusion

Async video standups are a format, not a tool. Three questions, 90 seconds, one take, one thread, and a written reply when someone is blocked. Try it for two weeks and keep it only if the team reads it.

[Start recording free](https://screenrecord.in/)
