How to Record an Async Video Update Your Team Will Watch

You recorded a seven minute screen video explaining the project status, posted it in the team channel, and two days later nobody has watched past the first minute. The questions you answered in the video are now arriving as chat messages. An async video update can save a meeting, but only if it is built for someone watching on a phone between two other tasks.

I have reviewed a few hundred of these recordings from distributed teams, and the ones that get watched share a small set of habits. None of them require better equipment.

When an async video update beats a written message

Video is slower to consume than text. Most people read around 230 words per minute and speak around 140, so a written update is usually faster for the reader. That means video has to earn its place.

It works best in four situations:

Walking through something visual, such as a design, a dashboard, or a bug that only shows up in a certain sequence of clicks.
Delivering news with tone, such as a change in priorities that people might take personally.
Explaining a decision with trade-offs, where hearing your reasoning reduces back-and-forth.
Replacing a recurring status meeting where people mostly listened anyway.

If your update is a list of dates, numbers, or links, write it. A clear written note, like the ones in our guide to the email that gets answered in one reply, will beat a video every time for that kind of content.

Keep it under three minutes

Viewer drop-off is steep. In most workplace tools, a large share of viewers leave in the first 30 seconds if the opening is vague, and completion falls sharply after the two minute mark. Aim for 90 seconds to 3 minutes. If you need longer, split the content into two videos with clear titles, so people can pick the one that matters to them.

A practical way to hit the length: write three bullet points before you press record. One point per minute. If you have six points, you have two videos or one written message.

A structure that holds attention

First 10 seconds: say who it is for and what you need. "This is for the design and support leads. I need a yes or no on the new returns page by Thursday."
Next 60 to 120 seconds: show the thing. Share your screen, point with the cursor, and narrate what changed.
Last 20 seconds: repeat the ask and the deadline. Say where to reply, for example in the thread under the video.

That opening line is the most important sentence in the recording. People decide whether to keep watching based on it, the same way they decide whether to open an email based on the subject line.

Write the message around the video

The text you post with the video matters as much as the recording. Many people will never press play, and that is fine if the post gives them what they need.

Include three things in the post itself:

A one sentence summary of the update.
The specific ask, with a name and a date.
Timestamps if the video covers more than one topic, such as "0:40 new checkout flow, 1:50 open questions."

Turn on captions or the auto transcript if your tool offers one. Teammates across time zones, people in open offices and anyone working in a second language will thank you. Transcripts also make the update searchable later, which is a quiet benefit when someone asks "where did we decide that?" three weeks on.

The advice to look polished is wrong

A lot of guidance tells people to treat work videos like mini productions: good lighting, a script, a ring light, multiple takes. For internal updates, this usually makes things worse.

The reason is cost. If recording a two minute update takes you 40 minutes of setup and retakes, you will stop recording them, and the team goes back to meetings. Polished videos also tend to sound rehearsed, and a rehearsed tone reads as less honest when you are delivering bad news or asking for help.

Instead, set one standard: the audio must be clear. A cheap wired headset will do more for comprehension than any camera upgrade. Record in a quiet room, look at the camera for the first and last sentence, and accept one stumble. One take, maybe two, is the right budget.

There is an exception. Videos that will be watched by dozens of people for months, such as onboarding walkthroughs, deserve a script and a second take. Weekly updates do not.

Make replies easy across time zones

The point of async is that people respond on their own schedule, so tell them how. Name one reply location. If you post in a channel, ask for replies in the thread. If the decision needs a quick vote, add simple reaction options in the text: a thumbs up for yes, a question mark for "need to talk."

Give a realistic window. A 24 hour deadline excludes anyone who is 10 or more hours away and has a day off. For distributed teams, 48 business hours is a fair default. Our piece on scheduling meetings across time zones fairly covers the same principle for live calls.

Finally, close the loop. When the decision is made, post a short written follow-up in the same thread. People who skipped the video then see the outcome without watching anything.

A quick checklist before you hit send

Under three minutes, or split into separate videos.
First sentence names the audience and the ask.
Screen shared only when there is something to see.
Clear audio, captions on.
Post text includes a summary, the ask, a deadline, and timestamps.
One reply location named.

If you notice that your recorded updates still leave people tired, it may be the format rather than the content. We explored this in why video calls wear people out faster than meetings, and some of the same causes apply to recordings.

Frequently asked questions

How long should an async video update be?

Aim for 90 seconds to 3 minutes. Beyond that, viewers drop off quickly, especially on mobile. If you have more to say, split it into two videos with clear titles or move the details into the written post.

Should I show my face in an async video?

Showing your face for the opening and closing helps with tone, particularly for sensitive news. During a walkthrough, the screen matters more, so a small camera bubble or no camera at all is fine.

Is async video better than a status meeting?

For one-way updates, usually yes, because people can watch when it suits them and skip what does not apply. For decisions that need debate, a short live call is still faster. Many teams use video for the update and keep a 15 minute call only when there is real disagreement.