The average knowledge worker spends 31 hours per month in unproductive meetings, according to research by Atlassian. For managers, the number is higher.
The cost isn't just time — it's the trust of your team. People know when a meeting could have been an email. Repeated exposure to poorly run meetings trains your team that their time doesn't matter, their input isn't actually needed, and the whole exercise is theater.
This post covers a system for running meetings that end on time, produce real decisions, and don't waste anyone's afternoon.
---
The Three Failure Modes
Most unproductive meetings fail in one of three ways.
The meeting had no purpose. It was scheduled because something happened, because it was recurring, or because the organizer was uncertain and wanted human presence in the room. When there's no defined purpose, there's no way to know when you're done — so the meeting runs until someone has another meeting to go to.
The right people weren't there (or the wrong people were). Meetings where the decision-maker isn't present produce recommendations, not decisions. Meetings where non-essential attendees are present waste their time and dilute focus — large groups default to surface-level discussion because no one is willing to be direct in front of an audience.
Nobody prepared. When attendees arrive without context, the first 20 minutes of any meeting is typically spent getting everyone up to speed. That's information transfer, not discussion — and it could have been an email.
Fix these three problems, and you will have better meetings than most organizations have by default.
---
The Pre-Meeting Standard
A meeting without a pre-read is a meeting that starts 20 minutes late.
The meeting organizer is responsible for distributing, before the meeting: 1. The purpose of the meeting (one sentence — what decision or outcome are we here to produce?) 2. Any background information attendees need to have read to contribute 3. The agenda with time allocations per topic 4. Who is expected to have input on what
This doesn't require a formal document for routine meetings. For a 30-minute team sync, the pre-read might be three bullet points in the calendar invite. For a strategy meeting, it might be a two-page brief.
The standard is: every attendee should be able to walk in knowing what they're here to decide, having read what they need to read to be useful.
If you're not willing to send a pre-read, question whether the meeting is necessary. If you don't know what the meeting is trying to decide, you're not ready to schedule it.
---
The Agenda as a Decision Tree
Most meeting agendas are topic lists. Topic lists don't end meetings — they just give you a structure to wander through.
An effective agenda is a decision tree. For each agenda item, the organizer should know: - What decision needs to be made on this item? - Who needs to have input? - What does "resolved" look like?
If you can't answer these three questions for an agenda item, that item is either not ready to be discussed (needs more prep) or shouldn't be a meeting item at all (should be an async communication).
The time allocation on the agenda isn't a guideline — it's a discipline mechanism. If the first agenda item runs long, you're choosing between the rest of the agenda and the end time. Call it explicitly. "We're at our allocated time for this item. Can we make the decision now, or do we need to park it and continue async?" This prevents the meeting from running over, which is how meetings train people to disengage.
---
Running the Meeting
Open with the purpose, not small talk
The first sentence of the meeting should be the decision you're here to make. "We're here to decide whether to renew the vendor contract that expires at the end of the month. We have 45 minutes. Let me share where we are, and then I want your input."
This accomplishes several things: it orients late arrivals without repeating the agenda, it signals that this is a working session (not a social one), and it creates a natural endpoint — once the decision is made, the meeting is done.
Manage airtime, not just agenda time
In most meetings, the same three people talk and everyone else listens. This produces decisions that reflect the three most vocal opinions, not the best available thinking in the room.
The meeting facilitator's job is to surface input from the people who have relevant expertise, not just the people most comfortable speaking up. "Marcus, you've run this vendor relationship for two years — what's your read on renewal?" is a direct invitation that a silent but knowledgeable attendee will respond to.
Conversely, when one person is dominating a discussion at the expense of the agenda: "I want to make sure we get input from everyone before we move on — let me hear briefly from the others in the room, then we'll decide."
Make decisions visible
A meeting where everyone nods and then leaves uncertain about what was decided is not a productive meeting. It's a conversation that generated the illusion of progress.
At the end of each agenda item, the facilitator should verbalize the decision explicitly: "We're moving forward with renewal. Keiko owns the contract paperwork by next Friday. Marcus will brief the vendor on our terms by end of this week. Is there any disagreement with that?" Then write it down — in the shared notes, in the project management tool, somewhere.
The act of verbalizing and recording the decision converts group nod into organizational commitment.
---
The Post-Meeting Standard
A meeting produces three things: decisions, action items, and parking lot items (things that came up but belong in a different discussion).
Within 24 hours of the meeting, the organizer sends a meeting summary with: - Decisions made (one sentence each) - Action items (who owns what, due when) - Parking lot items (what came up that needs a different conversation)
This doesn't need to be a formal document. It can be a short message in Slack or email. The point is to create a written record that attendees can reference and that non-attendees can be brought up to speed from.
The meeting summary also closes the loop on accountability. When action items are written and attributed to specific people, "I forgot" becomes harder to say.
---
Which Meetings to Cut
The most effective change most teams can make to their meeting culture is to eliminate the recurring meeting that has outlived its purpose.
Every recurring meeting should be audited annually with one question: "If we hadn't had this meeting last month, what would have been worse?"
If the answer is "nothing specific," the meeting is a habit, not a necessity. The information that gets shared in it can be sent asynchronously. The decisions that get made can be made in other forums or delegated.
The test for whether a meeting should exist: it requires real-time discussion to produce an outcome that can't be produced asynchronously. Brainstorming, conflict resolution, decision-making where stakeholders need to negotiate — these are meetings. Status updates are not.
---
Further Reading
For the complete meeting system — including facilitation techniques, agendas for common meeting types (strategy, 1:1, retrospective, all-hands), and how to rebuild a meeting culture that's already broken — [The Meeting Standard](https://www.amazon.com/dp/B0GYGLBBFW) covers the full framework.
---
*Published by Tanta Holdings. For management consulting and operational systems work, visit [tantaholdings.com/consulting](https://tantaholdings.com/consulting).*