In this article
The Meeting Problem
Meetings are one of the most expensive activities in any organisation — and one of the most poorly managed. Every hour in a meeting is an hour not spent on actual work, multiplied by the number of people in the room.
A 60-minute meeting with eight people doesn't cost one hour — it costs eight hours of collective productive time, plus the switching costs of getting everyone back into deep work afterward. Most meetings are worth that cost. Many are not.
The dysfunction is widely acknowledged and almost never fixed. People complain about too many meetings, attend them anyway, and then schedule more. The key insight: meetings are a tool for a specific purpose. When they're used as the default for communication, decision-making, and status-signalling, they become a tax on the organisation's productivity.
Does It Actually Need a Meeting?
Before scheduling anything, ask: what type of outcome does this situation require?
- Decision needed, but the decision-maker has all the information: No meeting needed. Make the decision. Send an email or message explaining the reasoning.
- Information needs to be shared: Usually no meeting needed. A written document is faster to produce, can be read asynchronously, and produces a searchable record. Use a meeting only if the information requires significant dialogue, context, or emotional sensitivity.
- Complex decision requiring input from multiple people: Meeting justified. But define the decision in advance, circulate the background, and give people time to prepare.
- Relationship building, brainstorming, conflict resolution: Meeting justified. Human presence and real-time dialogue have genuine advantages here that async can't replicate.
- Status update: Almost never requires a meeting. A written update with a standing format is faster for everyone. Reserve meeting time for exceptions and decisions, not for reading reports aloud to each other.
Before the Meeting
Define the purpose in one sentence
Before you schedule anything, you should be able to complete this sentence: "This meeting will be a success if we ___." If you can't complete it, the meeting isn't ready to be scheduled. "Discuss the project" is not a purpose. "Decide on the go-live date and assign ownership for the three remaining blockers" is.
Invite the right people — and only them
Every person in a meeting is a decision about whose time matters. Invite people who are genuinely necessary: those who need to contribute to the decision, those who have essential information, and those who need to be aligned on the outcome. Do not invite people "to keep them in the loop" — send them a summary afterward.
Send an agenda in advance
An agenda sent at least 24 hours in advance does three things: it forces you to clarify your own thinking, it gives attendees time to prepare, and it signals that this is a purposeful use of time rather than a default conversation. Include: the purpose of the meeting, the specific questions or decisions on the table, any pre-reading required, and the owner of each agenda item.
Respect the time
30-minute meetings end in 30 minutes. 45 minutes is usually better than 60 — the time pressure creates focus. If you can't cover the agenda in the time available, trim the agenda rather than expand the time. Overly long meetings don't produce better decisions; they produce tired, distracted people making decisions in the final 15 minutes.
During the Meeting
Start on time — always
Waiting for latecomers penalises the people who arrived on time and rewards those who didn't. Starting on time without exception, consistently, changes the culture around punctuality within weeks.
State the purpose at the start
"We're here to make a decision on X by the end of this meeting." This creates shared accountability from the first minute and gives everyone a reference point if the conversation drifts.
Manage the conversation actively
Good facilitation is one of the most undervalued organisational skills. It means: keeping the conversation on track, giving airtime to people who haven't spoken, cutting off unproductive tangents, and summarising where you are periodically so everyone stays oriented.
Park the tangents
When important topics come up that aren't on the agenda, they deserve attention — just not now. A visible "parking lot" (physical or digital) where these topics are noted for later prevents them from hijacking the meeting and ensures they're not lost.
Make decisions explicit
Many meetings end without any clear decision having been made — even when one was reached. State decisions explicitly out loud: "So we've agreed that X will do Y by Z. Is that everyone's understanding?" This sounds elementary but it prevents a surprising amount of post-meeting confusion.
Assign ownership before you end
Every action item needs a named owner and a deadline. "We should look into this" produces nothing. "Sarah will send the analysis to the group by Friday" produces something. The meeting chair owns making this happen before the meeting closes.
After the Meeting
A meeting without follow-through is a conversation, not a decision. Within 24 hours:
- Send a summary. The decisions made, the action items with owners and deadlines, and anything that was parked for later. Keep it short — a bullet list is better than paragraphs.
- Update relevant systems. If decisions affect project management tools, roadmaps, or shared documents, update them immediately while the context is fresh.
- Follow up on overdue actions. At the start of recurring meetings, briefly check in on last meeting's actions. This creates accountability and signals that commitments made in meetings are taken seriously.
Common Meeting Types — Done Right
The one-on-one
Weekly or biweekly, 30–45 minutes, between a manager and direct report. The agenda should be primarily driven by the direct report, not the manager. It's for development, support, feedback, and building the relationship — not project status updates. Skipping these habitually is one of the most damaging management mistakes.
The team standup
15 minutes, daily or a few times per week. Each person answers: what did I do yesterday, what am I doing today, any blockers? The purpose is coordination and early problem-detection, not deep discussion. If something needs discussion, note it and have a separate conversation with the relevant people afterward.
The decision meeting
30–60 minutes, when a consequential decision requires input from multiple people. The decision criteria, relevant data, and options should be shared in advance. The meeting exists to discuss, align, and decide — not to receive information for the first time.
The retrospective
45–60 minutes, at the end of a project or sprint. What went well, what didn't, and what would we do differently? The key discipline: retrospectives must produce changes, not just observations. A list of insights that no one acts on is worse than no retrospective at all.
How to Behave as an Attendee
Good meetings require good participants, not just good facilitators. Your responsibilities as an attendee:
- Prepare. If pre-reading was sent, read it. If there's an agenda, think about your perspective on each item before you arrive. Coming unprepared and contributing nothing is a waste of everyone's time including your own.
- Be present. Laptop open, half-reading email, occasional head-nod is not attendance — it's a pretence. If the meeting isn't worth your full attention, the honest response is to say so and not attend, or to ask for the summary afterward.
- Contribute actively. If you have a relevant perspective and you're not sharing it, you're costing the meeting quality. The most common failure mode in meetings is that people have useful thoughts they don't voice because they're waiting for the perfect moment, or because they're unsure if it's the right moment. It usually is.
- Decline meetings you don't add value to. This requires some political judgement, but there are meetings where your presence adds nothing and you're there out of habit or because someone invited you without thinking. Politely declining and asking for the summary is a legitimate option — and signals to organisers that invites should be made with purpose.
FAQ
What do I do if I'm a junior employee in a culture of terrible meetings?
Start with what you can control: your own meetings, your own behaviour as an attendee, and your own team's practices if you have any influence there. When you do run a meeting, model the behaviours — agenda, time discipline, explicit decisions, follow-up. Cultural change usually starts at the edges and works inward. You don't need authority to change meetings you run.
Should cameras be on in remote meetings?
For short meetings where engagement and dialogue matter, yes — visible faces improve attention and connection. For long information-sharing sessions, the "camera fatigue" cost starts to outweigh the benefit. The most useful norm: cameras on during discussions, optional for pure information delivery. Never mandate cameras on for every meeting regardless of format.
How do I deal with someone who always derails meetings?
Address it directly but politely in the moment: "That's an important point — let's park it and come back to it after we've addressed the main agenda." If it's a recurring pattern with the same person, a brief private conversation after the meeting is usually more effective than repeated public redirections.
Is "no meeting Wednesday" or similar policies worth it?
The research on designated focus time is positive, and several large organisations have implemented it successfully. The critical factor is whether the policy has real teeth — whether executives and senior leaders visibly respect it. A no-meeting day that applies to everyone except senior leaders, or that gets overridden whenever it's inconvenient, signals that focus time is a perk rather than a priority.