Is There a Bad Meeting Epidemic?
You have been in the meeting I am about to describe.
Nine people. One hour. A vague title on the invite. Somebody shares a screen and starts clicking through some slides. Somebody else asks a question that reopens a decision made three weeks ago. The last ten minutes get spent scheduling the next meeting. Everyone leaves and nothing moves.
The easy read is that meetings are broken. The research says something more precise, and more useful.
Atlassian’s research on workplace meetings found that roughly 71 percent are considered unproductive by the people attending them. Lucid put the annual cost of unnecessary meetings in the United States at around 399 billion dollars. And a University of California, Irvine study found that 63 percent of meetings are held with no predefined agenda at all.
Sit with that last number. Not a bad agenda. No agenda.
Here’s what’s actually happening. The meeting is not failing in the room. It is failing on the calendar, days earlier, when someone hits Send on an invite they have not thought through. Not defined. The hour then gets spent doing the definition work in public, at full salary, with an audience. That’s painful, expensive, and inefficient.
There is a second cost, and nobody counts it. When a meeting is undefined, you cannot know who actually needs to be there. So you over-invite. You add people to be polite. You add people to keep them in the loop. You add people because leaving them off feels like a slight. And if you do not really have a plan, you honestly do not know if they need to be there. Every one of those invitations is a tax you charge someone else because you did not do your own thinking first.
I worked for several general managers who solved this with a single rule. If an invite did not carry a clear Purpose, a defined Outcome, and a named Process, they declined it. Not rudely. Automatically.
Three words. It changed how I plan every hour I ask people to give me.
1 - Purpose: Name the Direction
Purpose is the why. Honoring people’s valuable time starts with a clear reason to meet.
Sometimes you just have a gut feel that you need to meet. Something needs to be wrestled down. An upcoming event. A competitor moved. A problem to be solved. A milestone is closing in. That instinct is usually right, and acting on it is a good thing.
But the instinct has to survive contact with words. It cannot live in your head. People need context, grounding, framing. They need to know why you are meeting and what will happen there. That is the first step to a great meeting.
Simon Sinek built a career on starting with why. His central insight is simple: until people understand why something matters, they have little reason to care. That is what Purpose is about.
I challenge you to keep this first part as simple as possible. That doesn’t necessarily make it easy. But it will get easier over time as you build the skill. Perhaps two or three words: a topic and an action word. It might look something like this:
Portfolio Prioritization
Candidate Decision
Design Review
Townhall Dry-run
It is only a few words, but it does several things. It frames the topic quickly, so people can see what this is about with a quick scan. It belongs in the meeting notice title. And the shorter it is, the easier it makes it to develop the discipline of POP.
Two or three words and the Purpose is done. Do not spend your morning polishing the why. Get the direction right in a few words and move on. The discipline and precision that saves or loses the meeting lives in what comes next.
APPLICATION
Write your Purpose in the meeting title itself. If it fits in five words, it belongs in the subject line. If it does not fit in five words, you have not finished thinking about it yet.
2 - Outcome: Name the Deliverables
The Outcome comes next. You cannot design a path without a destination, and you cannot know who you need without knowing what you are building toward.
The Latin is useful here. Agenda is from the Latin agere, to act. A gerundive: things that must be acted upon. Not things to discuss. Things to finish. An agenda is not a list of things to browse. It is a list of things to close.
A meeting without an Outcome is an hour of browsing followed by a second trip to the same store.
This is where the discipline breaks down for most people, and the failure is usually the same. They write a Purpose. Then they write it again in different words and call it the Outcome. Remember: Purpose is why the meeting exists. Outcome is what you carry out of the room.
Purpose is directional and we try to keep it simple to help anchor the mind. Outcome is concrete and checkable. Purpose is “Advance our Culture.” Outcome is “three joint commitments, each with a named owner and a date, in writing.”
You can argue about whether trust was rebuilt. You cannot argue about whether three commitments got written down.
Outcomes need to be specific, and you can have more than one, provided you have the time and a process to get there. The outcomes are usually something better captured in a bullet point. If there are several, make them separate bullets.
Examples
Top 3 priorities and 2 things we will not do
Candidate Decision to make an offer
Changes required for design sign off / before townhall
An Outcome you cannot verify at the end of the hour is not an Outcome.
APPLICATION
Write your Outcome as a physical artifact. A decision recorded. A document approved. A list of three, owned and dated. If you cannot photograph it, hold it, or paste it into an email when the hour ends, they are not outcomes.
3 - Process: Name the Path
Once you have your Outcome defined, you can design a path to get there. The Process is the path and the steps you take to deliver your Outcomes.
Keep in mind, there is more than one kind of meeting, and each runs on a different recipe and a different way to involve the room. Below are a few examples:
The Brainstorm. Post-it notes, physical or digital. Silent generation first, share out second. Prevents groupthink and surfaces ideas from internal processors.
The Convergence. Dot voting. Each person allocates their votes. Before you close, capture the rationale. A decision nobody understands will be revisited.
The Project Update. Five minutes of update, ten of questions. Forces discipline on the presenter and gives the room time to engage instead of just receive.
The Decision. Make the case, hear the objection, decide in the room. Name a challenger before you walk in (someone whose job is to argue the other side).
You do not owe anyone a minute-by-minute agenda. The bar is lower than that, but it should be well structured enough so that it can be facilitated without friction.
Here is the move most meeting runners miss. Process is not a delivery mechanism for what you need. It is a design decision for the people you invited. Death by PowerPoint happens when the Process is built for the presenter, not the room. The room becomes an audience of bystanders. Disengaged observers give you less, remember less, and commit to less.
Don’t just present. Design it the other way. When the Process invites the room to contribute, to rank, to react, to push back, to co-create, they lean in. The output improves and alignment builds naturally. People support what they helped shape, choose, and own. The decision does not belong to the person who ran the meeting. It belongs to the room.
APPLICATION
Name the meeting type in the invite, in plain words and how you will get the outcome. Ask yourself: what does the Process ask the room to do? If the answer is ‘sit and watch,’ redesign.
If your culture runs on pre-reads, that already is the Process. Name it in the invite: ‘Deck attached. Come ready to decide.’
Your One Move
Open with this live. Thirty seconds. Sets the room.
We are here for [purpose]
We walk out with [outcome]
Here is how we get there.
When your Purpose, Outcome, and Process are clear, meetings have a better outcome for you and a better experience for the participants.
But something else resolves. The people who actually need to be in the room become obvious. Not because you cut the list, but because the meeting defined itself. The role the meeting needs follows directly from the process you named. A divergence needs someone protecting half-formed ideas. A decision meeting needs a designated challenger: someone whose explicit job is to argue the other side so the group does not mistake agreement for rigor. An hour with an agreed Outcome needs someone writing down what was decided, because a decision nobody recorded is a decision you will relitigate.
You do not figure any of that out in the room. You figure it out when you build the POP.
That is not an efficiency gain. That is a form of respect.
The invisible tax of a vague meeting is not just the wasted hour. It is the nine people who could not tell whether they mattered, so they showed up just in case.
So here is your one move.
Take the next meeting you are about to schedule. Before you hit Send, write three lines in the invite body.
Purpose: 2-3 words (e.g. portfolio prioritization)
Outcome: The artifact we leave with (e.g. Top 10 ranked opportunities)
Process: How we get there (dot ranking exercise with rationale share out)
Then look at your invite list again. I suspect it gets shorter.
Better outcome for you, better experience for those invited (and not invited)
Subscribe to Wired To Connect for more. New piece every week.