ThemeMeetings & collaboration
CardCard 30 of 65
Questions5 to explore
StepDecide how you communicate

Meeting Protocols

Purpose, frequency, duration & participants

The question before every meeting is not how to run it but whether it needs to happen at all.

Meeting protocols are the agreements your team has about why you meet, how often, for how long, and who needs to be there. Without them, meetings expand to fill available time, calendars fill up with recurring calls that outlived their purpose, and people start joining things out of fear of missing out rather than because they have something to contribute.

In a hybrid team, the cost of a bad meeting is higher than in an office. Every video call takes more energy than an in-person conversation. A meeting that did not need to happen leaves remote participants wondering why they gave up an hour of focus time. The asymmetry of effort, some people commuting in, some dialing from home, makes it worse if the meeting itself is not well-run.

Good protocols do not mean bureaucracy. They mean a shared answer to a few basic questions: what is this meeting for, who actually needs to attend, how long does it need to be, and when does it stop making sense to run it.

Make it explicitFor each recurring meeting on your team calendar, write down its purpose, the required participants, the maximum duration, and when you will review whether it still needs to exist.

How strong hybrid teams handle it

The same building block, handled well. These are patterns from teams that work well across locations, offered as illustrations to react to, not rules to copy.

Agenda or cancel

Strong teams hold a norm that any meeting without an agenda posted at least a day in advance can be declined or rescheduled. This shifts the burden to the organizer to justify the time and ends up reducing the number of low-value calls.

Participant audit

Once a quarter, high-functioning hybrid teams review their recurring meetings and ask: who is attending that does not need to, and who is missing that should be there? The list tends to drift over time in both directions.

Default meeting length

Setting team-level defaults (25 minutes instead of 30, 50 instead of 60) creates transition time and signals that meetings should be as short as they need to be, not as long as the slot allows.

Meeting-free blocks

Teams that protect at least one or two meeting-free days or afternoons per week report better sustained focus. Making this a team norm rather than an individual preference means it actually holds.

Questions for your team

Use these on your own or in a group. There are no right answers, only better conversations.

Which meetings on your team calendar would nobody miss if they disappeared tomorrow?
Does everyone who attends each recurring meeting actually need to be there, or is some attendance just habit?
How do you currently decide whether something needs a meeting or could be handled asynchronously?
When was the last time your team reviewed its recurring meetings and cut or changed any of them?
What is the right ratio of synchronous to asynchronous communication for your team's work?

Watch for

Recurring meetings rarely get cancelled on their own. They tend to continue long after their original purpose is gone because no one wants to be the person who kills them.
Inviting everyone 'just in case' is considerate in intention but exhausting in practice. Large meeting lists also make it harder to get to decisions because more people need to be aligned.
Meetings that substitute for a written decision or update cost synchronous time for something that could have been async. This is especially costly across time zones, where you may be asking someone to show up at 7am for an information transfer.