Practice knowledge base
Remote-first meeting protocol
A remote-first protocol makes a hybrid meeting equally accessible for in-office and remote participants: everyone joins under the same rules, with personal audio, video, and a shared screen.
Documentation sections
What it is
This is a team protocol for meetings where at least one participant works remotely. The team designs that meeting as remote for everyone: each person speaks into their own microphone, sees the shared screen, uses one chat, and follows the same rules for joining the discussion. This practice addresses the problem of the in-office part of the team making decisions faster and more quietly than remote colleagues can join in.
When it helps
- Remote participants learn about decisions after the meeting instead of during the discussion.
- In-office colleagues talk among themselves without a microphone, and it is hard for remote participants to follow the conversation.
- Hybrid meetings often end with repeated clarifications in chat.
- Part of the team rarely speaks up because the discussion happens around the meeting room.
- The manager wants to keep a hybrid format without remote employees losing their voice.
How to start
- 1 Set one rule: if there is a remote participant in the meeting, everyone joins the shared video call from their own device.
- 2 Assign a moderator to manage the speaking queue, watch the chat, and make sure decisions are spoken into the microphone.
- 3 Define the minimum setup: a personal microphone or headset, camera on when possible, a shared screen, and one shared document for notes.
- 4 Run one regular meeting using the new protocol, and separately ask remote participants where it was hard for them to join in.
- 5 After the meeting, check that decisions, owners, and next steps are recorded in one place that is accessible to all participants.
Expected effect
The team reduces the risk of unspoken in-office agreements: decisions are voiced in a shared channel, questions go into one queue, and next steps are documented for everyone. It also becomes easier for the manager to notice who has dropped out of the discussion and bring that participant back into the conversation before a decision is made.
Common pitfalls
- Leaving one shared microphone in the meeting room: remote participants hear the room worse than in-office colleagues hear each other.
- Treating the camera as the main rule: clear audio, a shared screen, and an understandable speaking queue matter more.
- Not assigning a moderator: the in-office part quickly shifts into talking among themselves.
- Using the protocol for every meeting in a row, including short in-office conversations without remote participants.
- Not documenting decisions in writing: remote participants once again depend on retellings after the meeting.
Further reading
- Book: Jason Fried, David Heinemeier Hansson, Remote: Office Not Required
- Book: Lisette Sutherland, Work Together Anywhere
- Report: Microsoft Work Trend Index, materials on hybrid work
- Documentation: Google re:Work, materials on distributed teams
FAQ
Who should own the protocol?
Usually, the meeting owner: the manager, facilitator, or person who calls the discussion. They set the format in advance, assign a moderator, and make sure decisions are voiced and documented in the shared channel.
Can you start without new equipment?
Yes, if participants have personal devices, headsets, and a stable video call connection. If the meeting room audio is still poor, start with personal microphones or headsets for everyone in the room.
What if in-office participants are uncomfortable being on the same call?
Explain the practical reason: the rule protects the quality of decisions, rather than adding formality. Start with meetings where decisions are made or disputed issues are discussed, and collect feedback after a few rounds.
How do you know the practice is working?
Look for signs in the work: fewer clarifications after the meeting, remote participants asking questions more often during the discussion, and decisions and owners appearing in the shared document before the call ends.