Video, text or a meeting? How to choose the right format

The meeting that could have been an email and the ten minute video nobody finishes share a cause: the sender picked the format before thinking about the reader. Three questions, asked in order, fix that.

By the VeoRec team · Oct 3, 2026 · 11 min read

Every day you make the same small decision dozens of times: should this be video, text or a meeting? Usually it happens on autopilot. The person who likes calls books a call. The person who likes writing sends four paragraphs. The person who just discovered screen recording sends an eight minute video about a typo.

This guide gives you a quick way to decide based on the message and the reader rather than habit. It has three questions you can run in your head in ten seconds, a table of sixteen common situations, a short quiz to test your instincts, and a few rules for combining formats so nothing gets lost.

Ask three questions, in this order

The order matters. Meetings are the most expensive format for everyone involved, so you rule them in or out first. Video comes next because it only wins in specific cases. Text is the default for everything else.

1. Does it need a live back-and-forth, or does it carry emotional weight? If yes, meet (or call). Disagreements, bad news, a tangled problem with many unknowns, or the first conversation with someone new.
2. Is it visual, or a sequence across screens? If yes, record a short video. Bugs, user flows, design reviews, walking through code, a dashboard that needs explaining.
3. Will people scan it, search it, quote it, or act on precise details? If yes, write it. Decisions, specs, instructions, numbers, anything that becomes a reference.

If none of the three gives a clear yes, write it. Text is the cheapest format to send and to receive, and it is the easiest to turn into something else later.

Run them on a real example. You want to tell the team the new onboarding flow is ready for review. Does it need a live back-and-forth? Not yet; nobody has seen it. Is it visual, a sequence across screens? Yes: five screens, in order, with reasons behind each. So record a three minute walkthrough. Then ask question three about the follow-up: the list of open questions and the review deadline will be referred to later, so they go in writing next to the link. One message, two formats, no meeting, and if reviewers disagree strongly, the call comes after they have all seen the same thing.

Meet when the conversation is the work

Meetings are good at a narrow set of things, and those things are important. A live conversation lets people interrupt, read faces, adjust tone mid-sentence and converge quickly when nobody yet knows the answer. No document does that.

Meet when:

• There is conflict or real disagreement. Two people with opposing views will exchange ten comments and end up further apart. Fifteen minutes on a call usually resolves it.
• The news is bad or personal. Missed targets, a cancelled project, feedback on someone's performance. Text strips tone and readers fill the gap with the worst version.
• The problem is tangled. When you cannot even write the question clearly, talking it through is how you find the question.
• People do not know each other. The first conversation with a new client, a new hire or a new partner team builds trust that makes every later async message easier.
• Speed matters more than everyone's time. An incident in progress. A launch-day decision.

Even then, the meeting should end in writing. Microsoft's 2023 Work Trend Index found 55% of respondents said next steps after meetings were unclear. Three lines in the channel afterwards (what we decided, who does what, by when) fix most of that.

Watch out for the unplanned call. Microsoft's 2025 report on the "infinite workday" found 57% of meetings were ad hoc calls without a calendar invite. Some of those are exactly right. Many are a question that could have been a two-line message, interrupting someone mid-task.

Record a video when the screen does the explaining

A short screen recording beats text when the thing you are describing moves, has a sequence, or is hard to point at with words. "The dropdown on step three overlaps the button when the window is narrow" takes a paragraph and still leaves room for doubt. A twenty second video of it happening leaves none.

Record when:

• You are reporting a bug. Show the steps and the failure. The developer sees exactly what you saw. More in video bug reports.
• You are reviewing visual work. Design, copy in context, a landing page. Point at things as you talk.
• You are walking someone through a flow. Onboarding, a new feature, how to use an internal tool.
• You are explaining code or data. Scroll through the pull request or the dashboard, and explain the part that is not obvious.
• Tone helps and the topic is not sensitive. A thank you, a welcome to a new teammate, context for a decision. A face and voice carry warmth that text struggles with.

Keep it short: under five minutes, ideally two or three. Say the point in the first ten seconds. And always put the ask in writing next to the link, because some people will skim the channel and never press play.

This is the case VeoRec's Chrome screen recorder is built for: record a tab, window or your whole screen in Chrome with your voice and an optional camera bubble, and the share link is copied when you stop. Viewers need no account. Every recording gets an automatic transcript, so someone who would rather read can, and anyone can leave a timestamped comment on the exact moment they have a question about.

Write it when people will scan, search or quote it

Writing is the default because it is the most flexible format for the reader. They can read it at their own speed, skip to the part that matters, copy a number, search for it in six months, and forward it to someone who was not involved.

Write when:

• It is a decision. What was decided, by whom, why. Decisions in videos or meetings get relitigated because nobody can find them.
• It contains precise details. Numbers, dates, URLs, configuration, steps someone will follow while doing the task.
• It is a request with a deadline. The ask, the context, the deadline and the default if nobody replies.
• It will become a reference. Specs, how-tos, policies, onboarding docs.
• It is short. A two-line answer is a two-line answer. Recording it wastes the viewer's time.

Writing also exposes muddled thinking, yours included. In his 2017 letter to shareholders, Jeff Bezos explained that Amazon does not use slide presentations in meetings; it uses narratively structured six-page memos, and he noted that the great ones are written and rewritten over a week or more. You do not need six pages or a week. But try writing three clear paragraphs about a plan you have not thought through, and you will find the gaps before your reader does.

Compare the cost from the reader's side

People often pick video because it is faster to make. Talking for three minutes is quicker than writing 450 careful words. But you send a message once and it is consumed by everyone who receives it, so the reader's cost matters more. Post a three minute video to a channel of twelve people and, if they all watch, you have spent 36 minutes of the team's attention to save yourself perhaps ten minutes of writing. Sometimes that trade is worth it. It should be a choice, not an accident.

For plain explanation, reading is usually faster than listening. A 2019 meta-analysis by Marc Brysbaert estimated average silent reading of English non-fiction at about 238 words per minute, faster than people typically speak. Move the slider to see the gap for a message of your length.

So video earns its place when the visuals carry information that would take many more words to describe, not when it is simply narration of text. Meetings add another cost on top: finding a time that suits everyone, the context switch before and after, and the people who sit through parts that do not concern them.

Look up your situation

The table sorts sixteen situations a product team runs into most months, with the format that usually wins and why. "Usually" matters: context can flip any of these, especially the sensitive ones.

Test your instincts

Try these four. The explanations matter more than the score.

Combine formats so nothing gets lost

The best work messages often use two formats, each doing what it is good at. Four combinations cover most cases:

• Video plus the ask in writing. Post the link with one or two lines: what you need, from whom, by when. Skimmers act; watchers get the detail.
• Meeting plus a written summary. Decisions, owners and dates in three lines, posted where the work lives.
• Document plus a walkthrough. A spec or proposal with a three minute recording that explains the reasoning. Readers who want the why can watch; others read.
• Screenshot plus one sentence. Sometimes the visual is a single state, not a sequence. A marked-up screenshot is faster than any video. Screenshot, GIF or video covers that choice in detail.

The common thread: the written part carries anything someone might need to find again. Video and meetings carry context, tone and nuance. In VeoRec, the screenshot tools sit next to the recorder (visible area, full scrolling page, a selected area, or the whole screen), so you can pick whichever the message needs without switching tools.

Adjust for the person on the other end

The three questions are about the message. The reader can shift the answer, and a few adjustments come up again and again.

• People reading in a second language. Many prefer text, because they can read at their own pace and run a sentence through a translator. If you do send video, a transcript and captions make a big difference.
• Executives and busy stakeholders. Lead with a three line written summary. Offer the video as optional detail. They will often read the summary on a phone between meetings.
• Clients. Early in a relationship, lean towards calls and personal videos; trust is still being built. Once it is established, written updates with occasional walkthrough videos respect their time.
• New teammates. More video and more calls in the first weeks. They do not yet know the shorthand your written messages rely on.
• People in very different time zones. A meeting means someone joins at a bad hour. Default to text and video, and rotate the inconvenient slot when a call is unavoidable.

When you are unsure what someone prefers, ask once and remember. "Do you prefer a quick video or a written summary for these reviews?" is a perfectly normal question, and the answer saves both of you time for months.

Spot the signs you picked the wrong format

You will get it wrong sometimes. The useful skill is noticing early and switching. These are the common signals:

One example of a switch done well. A product manager posts a written spec for a new export feature. Within a day the thread has fourteen replies, and half of them are variations of "wait, which button do you mean?". The words were fine; the reader could not picture the screen. She records a ninety second walkthrough of the mockup, pins it above the spec, and the next five replies are about the actual decisions. The spec stayed in writing, where it belongs. The video carried the part words were bad at.

Switching mid-stream is normal and healthy. Saying "this thread is going in circles, let's talk for ten minutes and I'll post the outcome here" is one of the most useful sentences in remote work.

Give your team a few defaults

You do not need a policy, but a few shared defaults stop the same arguments recurring. Write five or six lines in your team space, along these lines:

• Status and standups are written or recorded, never a meeting.
• Bugs come with a recording and written steps.
• Decisions are written proposals with a deadline and a decider.
• Disagreements that survive two rounds of comments get a 15 minute call.
• Every meeting ends with a written summary in the project channel.
• Videos stay under five minutes and come with the ask in text.

Then revisit them once a quarter. If people keep breaking one, it is either a bad default or one nobody remembers; find out which. The async communication guide has a fuller charter template, including reply times per channel.

What to do next

For the next week, before you send anything longer than two lines or book any meeting, run the three questions. Notice which format you would have picked by habit and which one the questions point to. Keep a tally if you like. The pattern tends to be personal: some of us book calls for things that needed one written paragraph, others write long messages about things that needed a thirty second recording. Once you know which way you lean, you can correct for it.