Running and Joining a Remote Meeting

The remote meeting concentrates all the difficulties of the channel: reduced signals, screen fatigue, the temptation to multitask, overlapping turns or, conversely, awkward silences. A badly run video meeting is far worse than a bad physical one. Fortunately, a few precise rules transform the experience — whether you are the facilitator or a participant.

Before the meeting: half the work

A good remote meeting is won before it starts:

• An agenda sent in advance, with the objective and the expected outcome ("decide X," "scope Y").
• The right length and the right people. Remotely, fatigue sets in faster: prefer 30 dense minutes to 60 flabby ones, and invite only those who contribute or decide.
• Documents shared upstream, so the synchronous time is for discussion, not reading.

The best remote meeting is often the one you managed to replace with a well-made shared document. If it happens, it's because it provides what writing cannot.

During: the facilitator's role

The facilitator of a remote meeting does work that the physical room used to do for them. Their key moves:

An effective technique against silence: ask a question and then name a person rather than throwing "anyone have an idea?" into the void. Remotely, an unaddressed question almost always falls flat.

During: the participant's role

The quality of a remote meeting doesn't depend on the facilitator alone. As a participant:

• Be genuinely present. Multitasking shows (drifting gaze, slow reactions) and impoverishes the meeting. Close your email.
• Signal your wish to speak. Raising a hand (physical or button), or using the chat, avoids talking over each other because of latency.
• Use the chat wisely: for links, additions, +1s, without creating a parallel meeting that disrupts the spoken one.
• Help the facilitator: paraphrase, ask clarifying questions, bring things back on topic.

Managing turns and latency

The micro-latency of audio is responsible for most of the "sorry, go ahead / no you go." Two remedies: pause for one second before speaking (to be sure the other has finished), and, for the facilitator, regulate explicitly ("let me let you finish, then Sofia"). The one-second silence is not a void to fill: it's the lubricant of remote conversation.

After: with no notes, the meeting didn't happen

Remotely, collective memory is weak. A short record of decisions — who does what, by when — sent right after anchors commitments and includes those who were absent. It's the written equivalent of the end-of-meeting handshake.

graph LR
    A[Before: agenda + docs] --> B[During: frame, turns, summaries]
    B --> C[After: record of decisions]
    C --> D[Clear, shared commitments]

What to say / what not to say

Practical exercise

At your next remote meeting, as facilitator or participant, apply a single rule: one named round-robin on the main point ("let's go around: each in one sentence"). Observe the effect on attention and participation. Then, at the following meeting, add sending a three-line record of decisions.

Summary

A successful remote meeting is decided before (agenda, right people, documents shared upstream), during and after. The facilitator must speak the frame, hand out speaking turns explicitly, do named round-robins, paraphrase and state decisions out loud — all functions the physical room used to handle on its own. The participant must be genuinely present, signal their wish to speak and help the facilitator. Latency is managed with a one-second pause and explicit regulation. Finally, without a record of decisions sent right after, the remote meeting fades from memory.