There is no need to restart every recurring meeting automatically after summer. Keep a meeting if it requires simultaneous discussion, a complex joint decision or immediate coordination. Shorten it if only part of the agenda is valuable. Replace it with asynchronous work if participants mainly provide status updates, read information or approve a clearly formulated proposal. A practical meeting audit is not limited to reducing the number of calendar entries. For each recurring meeting, establish its purpose, required participants, expected outcome and the least costly way of working that can reliably deliver that outcome.
A meeting audit assesses outcomes, not habits
A recurring meeting often continues simply because it is already in the calendar. Its original purpose may have disappeared, the group of participants may have changed, and unrelated issues may gradually have found their way onto the agenda. The question ‘Do people like this meeting?’ is therefore not a sufficient starting point for an audit. Instead, ask: ‘What specific work outcome would be impossible to achieve, or become significantly riskier, without this meeting?’
Information exchange alone cannot be treated as an outcome. A more precise outcome might be an approved decision, a resolved cross-team dependency, an assigned owner, a reviewed risk or a shared understanding of an unclear situation. If you cannot say what changed after the meeting, it may not have a clear purpose.
The subject of the audit is the entire meeting portfolio, not one particularly unpleasant meeting. Assessing meetings individually can obscure duplication: the same status may be discussed in a departmental meeting, a project meeting and a management review. A portfolio view allows one source of information to serve several needs instead of repeating the same report for different audiences.
Create a meeting inventory before assessing anything
Collect all recurring meetings from at least one complete work cycle. If some meetings take place monthly, one week of calendar entries will not be enough. Include brief status calls, one-to-one conversations and recurring client or supplier calls if the team can influence their format.
Record the following for each meeting:
- its name, frequency and planned duration;
- the meeting owner and participants’ roles;
- its current purpose and typical agenda;
- the decision, document or next action produced after the meeting;
- what participants must prepare before the meeting;
- where decisions and owners are recorded;
- which other meetings cover the same information.
Calculate the time cost as the combined time of all participants, including preparation and the time spent switching between tasks. This calculation is not an argument for automatic cancellation. It merely makes the cost visible so that it can be compared with the outcome. An hour-long discussion of a complex risk may be justified, while a brief round of status updates for a large group may prove more expensive than its calendar duration suggests.
Decision matrix: keep, shorten or replace
You can assess each meeting using four questions.
|
Criterion |
What to check |
What the answer usually indicates |
|
Simultaneous interaction |
Do participants need to respond to one another in real time? |
If so, a synchronous format may be justified. |
|
Uncertainty and conflict |
Is it necessary to understand conflicting assumptions, interests or risks? |
High uncertainty often requires a conversation. |
|
Standardisation of information |
Can contributions be submitted using a shared template? |
If so, status reporting can move to an asynchronous channel. |
|
Verifiability of the outcome |
Can the decision, deadline and owner be seen without a meeting? |
If so, a full meeting may not be necessary. |
The combination of criteria matters. The fact that a decision is made during a meeting does not mean everyone must be on the same call. A clear, low-risk proposal can be circulated for comments and approval by a defined deadline. Conversely, written exchanges about an issue that is difficult to describe or involves parties with different interests may take longer and create more misunderstandings than a brief, well-facilitated conversation.
When to keep a meeting
Keep a meeting when its main value comes from high-quality interaction rather than people’s presence in the calendar. This applies when a deadlock must be resolved, several trade-offs must be assessed jointly, sensitive feedback must be handled or action must be coordinated quickly during an incident.
Even a meeting that is retained needs a clear outcome. In the calendar description, specify the decision or question to be resolved, the preparation materials, the participants’ roles and where the outcome will be recorded. Someone does not need to be invited merely because they might find the outcome interesting later. A summary will often be sufficient in that case.
If a team follows a specific methodology, its events should not be removed mechanically. For example, the official Scrum Guide defines the purposes and timeboxes of Scrum events. An audit should assess whether a particular event achieves its intended purpose, rather than cancelling the event while retaining a process that uses the Scrum name but lacks its essential components.
When to shorten a meeting
Shortening is appropriate when synchronous discussion is necessary for only one part of the agenda. Status updates and facts can be collected before the meeting, leaving only deviations, obstacles and decisions for discussion. This avoids spending meeting time on information that participants can read when it suits them.
For a shorter format to work, changing 60 minutes to 30 in the calendar is not enough. You must reduce the scope of the agenda or change the preparation process. For each item, specify an owner, the desired outcome and the available time. If material is not submitted by the deadline, defer the item unless doing so would create a greater risk.
Another option is to divide the audience. Only the decision owner, required experts and people whose work will be directly affected take part in the core decision discussion. A wider group receives the documented outcome. This reduces the total time spent without restricting access to information.
When to choose asynchronous work
Asynchronous work does not mean cancelling a meeting without providing a replacement process. It is a way of working in which people do not need to be available at the same time, while contributions, deadlines, responsibilities and outcomes remain clearly visible. GitLab’s public handbook links asynchronous communication to documentation and access to information; these principles are also useful for teams that do not work entirely remotely.
An asynchronous format is usually suitable for:
- recurring status updates submitted through a shared template;
- comments on a proposal prepared in advance;
- straightforward approval based on clear criteria;
- distributing information when an immediate response is not required;
- collecting questions before a brief decision meeting.
It is less suitable when an issue is emotionally sensitive, urgent, difficult to formulate or not supported by a shared understanding of the context. An asynchronous discussion can also stall if there is no decision owner or deadline. The choice is therefore not between ‘a meeting’ and ‘a chat message’, but between two fully designed work processes.
How to create an asynchronous replacement
A reliable replacement requires one designated location, a consistent input structure and a clear conclusion. Scattering information across email, chat and several documents increases the likelihood that participants will see different versions.
Include the following in a simple asynchronous template:
- Objective. What decision or outcome is required?
- Context. Which facts, constraints and previous decisions need to be known?
- Proposal. What action is recommended, and which alternatives have been considered?
- Requested input. Is a comment, objection, approval or additional data required?
- Deadline. By when must input be provided?
- Decision owner. Who makes the final decision if there is no consensus?
- Conclusion. Where will the decision, rationale, owner and implementation deadline be published?
An escalation rule must also be defined. For example, if a substantial conflict emerges in writing, there is insufficient data or a decision is still impossible after the deadline, the owner convenes a focused discussion involving only the necessary people. This prevents the asynchronous format from becoming an obstacle when real-time dialogue is genuinely more effective.
Introduce changes as a measurable pilot
Do not irreversibly clear the entire calendar in one day. Select a few recurring meetings, document the starting position and test the new format for two to four weeks. This duration is a practical audit period, not a universal standard; less frequent meetings will require a longer observation period.
Before the pilot, decide what you will measure:
- total participant time, including preparation;
- the proportion of decisions made and follow-up actions completed;
- the number of missed contribution and approval deadlines;
- instances when uncertainty required an additional discussion;
- participants’ assessment of how clear the objective, decision and responsibility were.
Time saved alone is not a sufficient measure of success. If meetings disappear but decisions are delayed, responsibility becomes unclear or people spend even more time in chat, the work system has not improved. Conversely, an additional brief discussion does not automatically indicate failure: it may be the correct escalation for an issue whose complexity became apparent only after written preparation.
At the end of the pilot, make one clear decision for each meeting: retain it, change its frequency, shorten it, combine it with another meeting, replace it with an asynchronous process or discontinue it. Add the next review date to the calendar entry so that the new format does not itself become an unexamined habit.
Limitations and risks
Reducing the number of meetings can shift the coordination burden onto people who write summaries or answer the same questions individually. You should therefore assess the total time involved and identify who takes on the new work. Take particular care not to let documentation become an invisible responsibility assigned to one team member.
A written format can lead to unequal participation. People with less context may not know when to object, while more active participants may effectively make a decision before others have read the material. A reasonable response deadline, an explicit request for specific roles to provide input and a visible decision status can mitigate this risk.
Confidential, personnel-related or legally sensitive information must not automatically be moved to a widely accessible document. Follow the organisation’s rules on access, data retention and information security. In some cases, a restricted discussion and a brief, appropriately protected decision record will be more suitable than a detailed asynchronous discussion.
Finally, not every meeting is merely a production mechanism. One-to-one conversations, relationship building and complex feedback can create value that cannot fairly be assessed solely by the number of decisions made. These meetings also need a purpose, but their audit must not ignore trust, psychological safety or a manager’s responsibility to identify problems promptly.
A brief meeting audit checklist
Before restarting recurring meetings, check:
- whether each meeting has a named owner and a specific outcome;
- whether status updates can be submitted before the meeting;
- whether only people whose participation is needed in the discussion have been invited;
- whether decisions, owners and deadlines are stored in one place;
- whether the asynchronous process has a response deadline and an escalation rule;
- whether the new format will be measured and reviewed again.
A good meeting audit does not leave the team with an emptier calendar and greater uncertainty. It produces an understandable work system: conversations are used where live interaction is needed, while predictable information flows and straightforward approvals take place through a documented asynchronous process.