Online meetings have a bad reputation they mostly earned one invitation at a time. The meeting itself is rarely the problem — the preparation was. A meeting with a stated purpose, a real agenda, and named roles is a different instrument from a calendar block with a title and nine invitees.
Almost everything that makes a meeting productive happens before anyone joins the call. This guide covers that preparation in the order it occurs: decide, draft, assign, set up, run, follow up.
Decide whether the meeting needs to exist
Before writing an invite, write one sentence: what will be different after this meeting? If the honest answer is “nothing — people will be informed,” send a written update instead. Async-first teams reserve meetings for what genuinely needs real-time interaction:
- Decisions with trade-offs that people will want to argue in real time
- Workshops and brainstorming where building on each other matters
- Difficult or sensitive conversations where tone carries information
- Kickoffs, where alignment and energy are the point
Status reporting, one-way announcements, and “quick questions” almost never need a slot on eight calendars. A written update reaches everyone, takes each person two minutes instead of thirty, and leaves a searchable record.
Prepare an agenda that does work
An agenda is not a list of nouns. “Roadmap, budget, misc” is a container, not an agenda. Each item needs three parts:
- The question the item answers — “Do we delay the launch to include SSO?” not “Launch.”
- The owner — the person who brings the material and speaks first.
- The time — an allocation that adds up to less than the meeting length. The slack is for reality.
Put the agenda in the invite itself or link a document from it — never in a separate message that half the room never opens. Attach anything attendees should read beforehand, and mark clearly which items are “decide” versus “discuss.” If every item is “discuss,” you’ve scheduled a conversation, and the agenda should say so honestly.
Assign roles before the call
Three roles make online meetings run noticeably better, and none of them is “the person who talks the most”:
- Facilitator — owns the agenda and the clock, pulls in quiet participants, and parks tangents. On small calls this is the organizer; on important ones it’s deliberately someone else.
- Note-taker — captures decisions and action items live, in the shared document, so the record exists the moment the call ends. Rotate this role; it’s how people learn to run meetings.
- Timekeeper — optional on short calls, essential on long ones. Signals when an item reaches its limit so the facilitator can decide to wrap or extend deliberately.
Name the roles in the invite. Roles that exist only in someone’s head don’t survive the first tangent.
Set up the technology beforehand
Technical friction burns the first five minutes of most calls, which is precisely when attention is highest. A short habit list prevents it:
- Join two minutes early — as the organizer, you test your own mic and screen share before others arrive.
- Share the link where people look — in the calendar invite, not in a chat thread from last week.
- Check guest permissions — if external participants join, verify the meeting settings allow them, and that the waiting room is on if your policy requires it.
- Have the document open — the notes doc should be shared in the meeting chat within the first minute, so latecomers land somewhere useful.
Run the meeting with intent
Three minutes of opening discipline sets the tone for the rest:
- State the purpose and the finish line. “We’re here to decide X; we have 50 minutes; here’s the agenda.”
- Start with the decision items, not the easy updates. Energy is a resource; spend it on what matters.
- End every item by asking, “Are we decided, or do we need another session?” Ambiguity here becomes a week of chat threads.
Facilitation online is mostly invitation: people who are muted need to be asked by name. “Dana, you’ve done this before — what are we missing?” works better than “any thoughts?” and silence.
Follow up while decisions are fresh
The meeting isn’t done when the call ends; it’s done when the record exists. Within an hour — ideally while still at the desk:
- Post the notes link to the channel where the topic lives, with a three-line summary of decisions and owners.
- Create the action items as actual tasks with owners and dates, not as lines in the notes nobody rereads.
- If a decision affects people who weren’t in the room, tell them directly — the notes are the record, not the announcement.
This closing ritual is the difference between meetings that compound and meetings that evaporate. For making it automatic on recurring calls, see Building Repeatable Meeting Workflows.
A reusable pre-meeting checklist
Copy this into your team’s wiki next to the meeting templates:
- One sentence: what changes because of this meeting?
- Agenda in the invite — questions, owners, minutes per item
- Roles named: facilitator, note-taker (timekeeper if long)
- Pre-reads attached and marked “read before”
- Invite list: everyone who decides or is affected — everyone else gets the notes
- 25/50-minute slots, link in the invite, notes doc pre-created
- Post-meeting: notes to the channel, tasks with owners, direct tells for absent stakeholders
Run the checklist for a month and it stops being a checklist — it becomes just how your team sends invites. For the surrounding habits, pair this with Practical Ways to Improve Workplace Communication, or browse the full guides library.