Async Video Communication: When to Record and What to Say

Most async videos fail for a boring reason: they're a meeting with the other people removed. Four minutes of "so, um, I was looking at this and..." before the point, and no clear ask at the end. The viewer gives up, types "can we just hop on a call?", and the meeting you tried to avoid happens anyway.

The short answer: async video works for one-way communication that needs a screen. Bug reports, code and design reviews, walkthroughs, status updates and handovers are good fits. Keep each video under 2 minutes, open with what you need and by when, show the screen instead of describing it, and add captions. Use text for anything someone needs to search or skim. Use a live call for disagreements, decisions under real uncertainty and a new hire's first weeks.

Why bother? Meetings aren't working well as the default:

• Microsoft's 2025 Work Trend Index found people are interrupted every two minutes during core work hours, about 275 times a day, by meetings, emails or chats. About 57% of meetings were ad hoc calls with no calendar invite (Microsoft WorkLab).
• Atlassian's survey of 5,000 knowledge workers found meetings were ineffective 72% of the time, and 54% of workers often left meetings unclear on next steps or who owned them (Atlassian).

Async video won't fix either problem on its own. A badly made one adds another interruption. Below: when to record, a four-part structure for every video, and the team rules that stop async from becoming a slower meeting.

When to Record, When to Write, When to Meet

Pick the format from what the message has to do, not from habit.

The bottom half of that table matters as much as the top. GitLab, one of the best-known async-first companies, now says this plainly in its handbook. Its sync vs. async guidance tells teams to default to async for "status, FYIs, decisions with clear context, proposals". It also says sync is for "decisions under ambiguity, conflict resolution, building trust with new people" and early brainstorming. It warns: "Don't let a thread run for a week when a 20-minute call would resolve it."

The decision rule: if the message is one-way and needs the screen, record it. If it needs a real exchange, meet. If someone needs to find it later, write it down too.

The Four-Part Structure for Every Async Video

A good async video answers four questions in this order. Say them out loud, even if they feel obvious.

1. What is this, and what do I need? (first 10-15 seconds) "This is the new billing page. I need you to approve the copy by Thursday."
2. The context. (15-20 seconds) Only what the viewer needs to judge the ask. Assume they have none of your background.
3. Show it. (most of the video) Click through the thing. Point at the problem. Say what you expected and what happened.
4. The ask again, plus a deadline. (last 10 seconds) Repeat what you need, from whom, by when, and where to reply.

Putting the ask first matters because viewers don't all watch to the end. Wistia's data on business videos found videos under one minute average a 52% engagement rate, so typical viewers watch about half (Wistia). An ask buried at 1:45 may never be heard.

GitLab's handbook makes the same point for written async: "tag decision owners explicitly and set a 'respond by' date so threads don't drift". Long messages need "a TL;DR and a clear ask". A video is no different.

If you can't state the ask in one sentence, you're not ready to hit Record.

How to Record Async Videos People Actually Watch

The recording itself takes minutes. These habits decide whether anyone watches it.

• Aim for 60-120 seconds. At the average speaking rate of about 150 words per minute (National Center for Voice and Speech), 2 minutes is roughly 300 words. That's enough for one topic. Two topics means two videos.
• Write three bullet points first. Not a script, just the ask, the key context and what to show. It cuts the "um, so" opening.
• Show the screen, not your face. A face bubble is fine. The viewer is there for the screen.
• Make the cursor easy to follow. Move slowly, pause on what matters, and zoom in or enlarge the cursor if your recorder supports it.
• Close everything private. Mute notifications and close unrelated tabs and messages before you start.
• Add captions. People watch with the sound off in open offices and on calls. For published, prerecorded video, captions are a baseline accessibility requirement under WCAG 2.1. Many recorders now generate them automatically. Check names and technical terms before sharing.
• Title it like a search result. "Billing page copy, approve by Thu" beats "Quick update".

Re-record only if the ask is unclear. A stumble mid-sentence is fine. A missing deadline is not.

Five Async Videos That Replace Recurring Meetings

These five replace the meetings that are mostly one person talking.

Status updates. Replace a daily or weekly round-the-table with a 60-90 second video: what shipped, what's next, what's blocked. Blockers go first, so they get seen. Microsoft found nearly a third of meetings now span multiple time zones. A recorded update saves one person from a 7 a.m. or 9 p.m. call.

Code review walkthroughs. Record yourself stepping through a pull request: what changed, why, and the one part you want a second opinion on. Link the video in the PR description, and keep line-level comments in the code review tool, where they belong.

Bug reports. Reproduce the bug on camera. Say what you clicked, what you expected and what happened. Paste the URL, browser and any error text below the video, since nobody can copy text out of a recording.

Design and product feedback. Click through the prototype and talk while you point. "This button" is clear on video and vague in a comment thread.

Handovers and how-tos. Before vacation, a role change or a release, record how the thing works. Put it in your wiki next to the written steps. It's the one async video that keeps paying back. For a fuller method, see how to make a tutorial video.

Pick one of these meetings, replace it for two weeks, and compare. That's a fairer test than switching everything at once.

Team Rules That Make Async Video Work

Async fails quietly when there are no rules. These five keep it working.

1. Every video has an owner and a reply-by date. No date means no one is responsible for answering.
2. Reply in the format that fits. A one-word approval can be a comment. A counter-proposal with screens can be a video.
3. Write down the outcome. Once a decision is made, post it as text in the thread or ticket. Videos are bad at being searched.
4. Batch your watching. Set one or two slots a day for team videos instead of watching each as it arrives. Each new notification is another interruption.
5. Escalate stuck threads. If a thread has gone back and forth three times without agreement, book a short call, then write up the result.

Rule 5 has research behind it. Microsoft's Human Factors Lab measured the brain activity of 14 people in video meetings with EEG caps. Stress-related beta waves rose steadily across two hours of back-to-back calls, and stayed steady when short breaks were added between them (Microsoft WorkLab). Async video earns its place by protecting those gaps, not by banning calls.

The test of your rules: can someone who missed the last week catch up from the written trail, without watching every video?

Choosing an Async Video Tool

Any recorder works if recording takes seconds and sharing takes one link. Check for:

• One-click start and an instant share link
• Screen plus microphone, with an optional face bubble
• Automatic captions you can edit
• Viewer comments or reactions, so replies stay with the video
• Cursor highlighting or zoom
• Download as MP4, so the video isn't stuck in one app

For platform-specific steps, see how to screen record on a Mac without a watermark and the best screen recorders for Windows. If you're on Loom's free plan, read how to download a Loom video as MP4 before you rely on keeping your videos.

One honest limit: a raw recording is right for internal async. It's often not right when the same walkthrough is going to customers, a whole company or a launch post. That's where Poko Motion fits. It takes a screen recording you already have and turns it into a polished video, and you refine it by typing what to change instead of editing a timeline. For your team's Tuesday status update, a raw recording is still better.

Your Next Step

Look at your calendar for next week. Find one recurring meeting where one person mostly talks and the rest listen. Replace it with a 2-minute video that opens with the ask and ends with a reply-by date. Run it for two weeks, then ask the team whether they want the meeting back.