How to decide whether a recurring meeting should exist

A recurring meeting should exist when people need to interact live to make a decision, solve a problem, resolve uncertainty or discuss a sensitive issue. If participants only receive information and their responses will not change the next step, use a written update, recording or shared document instead.

A useful test is: Can what participants say during the meeting change what happens next? If not, the meeting probably does not need to happen live.

A topic is not a reason to meet

Names such as “sales update”, “operations” and “project status” describe subjects. They do not explain why several people need to discuss those subjects at the same time.

Live interaction is usually justified when participants need to:

• choose between options or approve a decision;
• solve a problem that requires several perspectives;
• ask follow-up questions to clarify uncertainty;
• coordinate changing responsibilities or dependencies;
• discuss conflict, risk or an issue affecting people;
• agree on actions and assign ownership.

Information can still appear in a meeting when it provides context for a decision. The problem is not sharing information. The problem is making one-way reporting the entire purpose of the meeting.

Audit the purpose, participants and result

Start with a list of recurring meetings, including team calls, management meetings, project reviews and reporting sessions. For each one, compare its stated purpose with what actually happens.

Use three questions:

Then make an explicit choice: keep, change, replace or cancel the meeting.

Audit what happens, not what the calendar invitation claims will happen. A meeting described as a decision forum may consist mainly of people reading reports aloud. A status meeting may reveal operational conflicts that genuinely require a shared discussion.

Invite people according to their role

Attendance should reflect the role each person plays in producing the result. Participants usually fall into four groups:

1. Decision makers: People with the authority and responsibility to choose a course of action.
2. Essential contributors: People who hold facts, experience or constraints needed for the decision.
3. Action owners: People responsible for carrying out the agreed next steps.
4. Information recipients: People who need the outcome but do not need to shape it live.

The fourth group usually does not need to attend. Send them a concise record containing the decision, relevant context, owner and deadline.

Do not judge attendance only by how often someone speaks. A quiet participant may hold essential expertise or be accountable for implementation. Ask whether the meeting can reach and carry out a sound decision without that person.

Attendance can also vary by agenda item. A specialist may join for one decision rather than sitting through the full meeting.

Move one-way reporting into a reviewable format

Information that does not require an immediate response can usually be shared in a short written update, dashboard, recording, shared document or the team's existing work system.

A useful update should state:

• what has changed;
• what is on track or at risk;
• which decisions have already been made;
• who owns the next actions;
• what needs input, from whom and by when.

Replacing a meeting with an unclear document only moves the problem. The update still needs an owner, a review deadline and a clear way to raise questions or escalate risks.

For example, routine figures can be published before a weekly operations meeting. Participants review them in advance and flag exceptions. The live discussion then covers blocked work, conflicting priorities and decisions involving more than one team.

Do not create a coordination gap

Cancelling a meeting does not remove the decisions, dependencies or disagreements it handled. Before cancelling it, decide how those functions will continue.

Removing the meeting may cause problems when:

• no other forum has authority to make the required decisions;
• operational issues require rapid questions from several people;
• responsibilities regularly cross team boundaries;
• the subject is sensitive and unlikely to be raised in writing;
• written messages would divide one discussion across several disconnected threads;
• nobody is responsible for recording decisions and following up.

Sensitive issues are particularly poor candidates for an automatic move to text. Tone can be misunderstood, concerns may go unstated and each question may depend on the previous answer.

If a meeting is necessary but ineffective, redesign it. Narrow its purpose, shorten it, reduce attendance, require preparation or move routine reporting into pre-reading.

Choose one of four outcomes

Every meeting audit should end with an explicit decision.

Keep it. Live participation is necessary and the meeting regularly produces a defined result.

Change it. The meeting is necessary, but its frequency, agenda or attendance is wrong. Remove passive attendees and reserve discussion for decisions and obstacles.

Replace it. The purpose remains valid, but live interaction is unnecessary. Define who publishes the replacement update, who reviews it and how questions are escalated.

Cancel it. The original purpose no longer exists, another process already covers it or the meeting produces no decision or action. Record where any remaining information will go.

Consider a weekly management meeting in which each department reports what happened. Move those reports into brief written updates submitted beforehand. Keep a shorter live session for cross-team obstacles, priority conflicts and decisions requiring joint input.

The reporting was unsuitable for a meeting. The decisions were not.

Frequently asked questions

How often should recurring meetings be reviewed?

Review a meeting when its purpose, participants or operating conditions change. Also check established meetings periodically. A useful meeting can continue from habit after its original purpose has disappeared.

Does every recurring meeting need an agenda?

It should at least state its purpose, required preparation and intended result. A detailed agenda is helpful when several decisions compete for limited time, but it should not become paperwork that adds no clarity.

Should optional participants be invited?

Use optional invitations sparingly. If someone only needs the result, send them the record. If their expertise is needed for one item, identify that item and invite them for the relevant part where practical.

What should the meeting record include?

Record decisions, action owners, deadlines, unresolved questions and issues requiring escalation. A transcript rarely replaces this summary. People need to know what was agreed, not everything that was said.

What if people do not read written updates?

Do not automatically restore a meeting that exists only to force attention. Keep updates concise, assign a review deadline and identify anything requiring a response. When missing an update could have serious operational consequences, require acknowledgement and define an escalation process.