Guide · Video & communication
Should This Update Be a Video or a Meeting?
Choose a recorded update when people need context they can review, and a meeting when the work needs a live decision.
The calendar invite arrives with an agenda that says "project update." That could mean someone needs to explain a change, or it could mean three people disagree about what happens next. Those are different jobs. Decide which one you're asking people to do before choosing the format.
Use a recording to carry context
A short recording works well when the sender can explain the situation without needing an immediate answer. A walkthrough of a completed change, a progress update, or a demonstration of a bug gives viewers something concrete to inspect on their own schedule.
Make the response expectation explicit. "Please check the two checkout screens and leave approval or corrections by Thursday" is easier to act on than "Thoughts?" Include the destination for feedback so replies don't split across email, chat, and comments on an older document.
A recording also helps when people need to revisit the explanation. Someone taking over the project next week can watch the same walkthrough instead of asking the sender to repeat it. Keep a brief written summary beside the video so they can decide whether it contains what they need.
Use a meeting to resolve a dependency
A live discussion is useful when the next step depends on people comparing options, negotiating a constraint, or making a shared decision. Sending four increasingly long videos back and forth can cost more effort than a focused conversation.
For a hypothetical website project, the designer can record what changed in the new navigation. If the client must choose between a simpler menu and a requirement from another department, the team may need a meeting with the right decision-makers. Send the walkthrough beforehand, then use the meeting to resolve the choice.
Give the recording a clear shape
Start with the reason to watch. Show the relevant screen, explain what changed or needs attention, and finish with the requested response. Close unrelated tabs and prepare the example before recording. A viewer shouldn't have to watch you search for the thing you intended to show.
There is no universal ideal length. Keep what the recipient needs to understand the work, and remove detours. If the update contains several unrelated decisions, separate them or provide a written list with timestamps so the reviewer can respond precisely.
Protect the decision from the format
Whether you choose a video or a meeting, record the outcome in the place where the work is managed. A verbal approval that stays inside a call is easy to lose. A comment on a video may be useful evidence, but the task still needs its status, owner, and next action updated.
Try the change on one recurring update before replacing a team's whole meeting schedule. Ask whether recipients understood the work, responded on time, and knew where the decision lived. Keep the live conversations that help people resolve real uncertainty. Replace the meetings whose job is simply to deliver an explanation everyone can review independently.