Effective virtual meeting best practices connect preparation, facilitation and follow-up. Start with the result the group needs, choose a format that allows useful contributions, and finish with a clear record of decisions and next actions.
These ten practices cover team meetings, workshops and hybrid discussions. The virtual meeting agenda below is designed to be copied and adapted. For individual camera, microphone and participation habits, see our video call etiquette guide.
1. Build the agenda around a specific outcome
Replace a broad topic such as “support update” with the question the group must answer: “Which onboarding problem should we investigate next, and who will own it?” List the evidence participants should review and identify who can make the decision.
Give each agenda item an intended output, an owner and an estimated duration. Allow room for a relevant question to change the plan. A time estimate helps the facilitator notice a problem; it should not force an uninformed decision when essential information is missing.
Share the agenda early enough for meaningful preparation and include the meeting time zone. GitLab’s own meeting guidance provides a useful documented example: it asks organizers to consider an asynchronous route, supply an agenda and record decisions in a shared document. Those are practices you can adapt rather than a universal company policy.
Virtual meeting agenda Title: Date, time and time zone: Meeting owner: Desired outcome: Decision maker or approval route: Required participants and their contributions: Optional participants: Preparation and document links: Input deadline for anyone unable to attend: Agenda item | Lead | Question to answer | Time estimate | Output 1. 2. 3. Facilitator: Note taker: Chat/remote-participant monitor, if needed: Participation routes and accessibility arrangements: Fallback if the call or shared tool fails: Decisions and reasons: Open questions and missing evidence: Action | Owner | Due date | Tracking location Next review or checkpoint:
For a fictional thirty-minute support-team meeting, you might allocate five minutes to agree on the reported problem, ten to examine evidence, ten to choose an investigation and five to confirm owners. The allocation is an illustrative plan, not a research-based ideal meeting length.
2. Test the actual meeting setup
Check the devices, documents and features you intend to use. Open the presentation in the meeting platform and confirm that another participant can see the relevant content. Include a representative dialog or screen transition if it matters to the task.
In Google Meet’s desktop prejoin preview, you can choose the microphone, speaker and camera, check the microphone meter, play a speaker test and inspect the camera preview. A device check does not prove a recording or shared whiteboard will work; test those separately when needed.
Prepare a fallback that preserves the meeting’s purpose. That could mean sharing a written decision brief, continuing an approved audio conversation or rescheduling a demonstration. If an essential participant cannot access the evidence, pause the decision rather than treating their silence as agreement.
3. Facilitate the discussion deliberately
Assign someone to guide the conversation. In a small group, the organizer may also facilitate and take notes; in a complex workshop, separate those responsibilities so the facilitator can follow the discussion.
At the start, explain how people can contribute and how the group will reach a decision. Keep a visible list of questions awaiting discussion. When a new topic emerges, decide whether it belongs in the current item, a later item or a separate follow-up.
Use a round of input when the question benefits from hearing each person’s perspective, while allowing someone to pass or respond in writing. For a breakout activity, specify the question, expected output and reporting method first. Confirm the feature is available and suitable for the people joining.
4. Agree on practical meeting norms
Make the important expectations explicit: how to signal a question, when to mute distracting background noise, where to place links and how to report a technical interruption. A brainstorming session may need different turn-taking rules from a client presentation.
Explain camera expectations in context and provide alternatives where needed. Avoid using camera status, background or eye contact as a measure of attention. Someone contributing through captions, chat or a written document can still supply essential information.
When discussion overlaps, summarize the point currently being considered and give the next contributor a clear turn. Apply the same approach to senior colleagues and new participants. The facilitator’s job is to keep the discussion usable, not to embarrass people for a minor interruption.
5. Use a shared visual only when it helps the task
A diagram can clarify dependencies; a comparison table can make options easier to inspect. Choose the simplest shared artifact that helps the group answer its question. Introducing a separate whiteboard adds access, orientation and follow-up work.
Prepare a clear starting area and a short example contribution. Check that participants can open and use the tool with their actual accounts. Provide another way to submit input if they cannot edit the board.
Keep recommendations current. Google confirms that Jamboard reached end of life on December 31, 2024; it should not appear as a current meeting-tool recommendation. Evaluate a supported alternative against your requirements instead of replacing it with an untested list of features.
At the end, identify which artifact contains the agreed result and who maintains it. A busy canvas of ideas is not automatically a decision record.
6. Design participation for the people attending
Ask about access needs before the meeting and offer spoken, written and asynchronous input routes where practical. Give participants time to inspect a question before requesting answers. Do not require everyone to improvise immediately in front of the group.
For Teams, live captions are available through More actions → Language and speech → Show live captions. Teams does not save those captions; a saved transcript is a separate feature. Verify the arrangement your participants need rather than assuming a live caption display creates an accessible permanent record.
For recurring global meetings, review whose working hours repeatedly bear the burden. Rotate times when feasible and provide a clear deadline for written input. If somebody could not attend, give them a way to challenge an assumption or supply missing evidence before an irreversible decision proceeds.
7. Document decisions and follow-up during the meeting
Write down the decision, its reason and any unresolved qualification while the group can confirm the wording. Give each action an owner and a date or explicit checkpoint. “Team to investigate” does not identify who will move the work forward.
Teams meeting notes support agendas, notes and tasks. On desktop, add an agenda when scheduling or select Notes during the meeting. Microsoft states that external attendees cannot access or edit these notes, so arrange an approved document or summary they can receive when appropriate.
If recording is useful, confirm its approved purpose and audience separately. Check the saved output and give the replay context. Use our written call-record template for a focused record of decisions; use the recording archive guide when the team will reuse recordings over time.
8. Make interaction serve the outcome
A useful activity gives the group information it needs. Ask participants to compare two options, identify a missing constraint or inspect a proposed result. Avoid inserting a poll or exercise merely because a fixed interval has elapsed.
For a training discussion, have participants apply the instruction to a safe example and explain the result. For a decision meeting, ask what evidence would change the recommendation. For a status update, consider whether a written update would be sufficient.
Schedule breaks for longer sessions and make transitions clear. Describe important visual information aloud, identify the document section being discussed and leave space for questions. More animations, mandatory standing or constant camera use do not establish comprehension.
9. Plan hybrid meetings from the remote participant’s view
Test whether remote participants can hear each relevant person in the room and read the shared material. A room that works for in-person conversation may leave a remote attendee unable to follow side comments or see a physical board.
Nominate someone to monitor remote questions and bring them into the same discussion. Put the agenda and decisions in a shared location. Repeat important in-room comments into the meeting and pause before closing a topic.
When using Google Meet, Companion mode can give an in-room laptop access to shared content and participation features while its microphone and meeting audio are off. Use the room’s audio arrangement to speak and listen. Availability of particular features depends on the account; test the intended setup before the meeting.
Do not join several nearby devices with active microphones and speakers without checking the room’s audio plan. If the group cannot provide usable remote participation, change the format rather than continuing as though everyone has equal access.
10. Choose live and asynchronous work intentionally
Use a live discussion when the work needs rapid clarification, a sensitive conversation or a decision among people with different constraints. Use a written update, reviewed demonstration or shared question list when people can contribute independently.
Explain the expected response time and decision process for asynchronous work. Someone who submits a question needs to know where the answer will appear. Someone who misses the live meeting needs a concise record, not only a long replay.
Review recurring meetings periodically. Keep the parts that help the team make progress and move routine reporting elsewhere when appropriate. Cancel or change a meeting whose purpose no longer exists.
A ten-practice review for your next meeting
| Practice | Question to check |
|---|---|
| Agenda | What output must the group produce? |
| Technology | Can participants use the required devices and material? |
| Facilitation | Who guides discussion and handles new topics? |
| Norms | How do people ask questions and report interruptions? |
| Visual collaboration | Does the shared artifact help answer the question? |
| Inclusion | Can people contribute through suitable routes? |
| Documentation | Where are decisions, owners and due dates recorded? |
| Interaction | Does each activity supply useful information? |
| Hybrid access | Can remote attendees follow and influence the discussion? |
| Live versus asynchronous work | Which parts actually need simultaneous participation? |
Afterward, compare the meeting’s intended output with what the group produced. Note one change to the agenda, facilitation or access arrangement for next time. Use that observed result to improve the format.
