In April 2014, Perkins Coie attorney Jonathan Perkins filed what became a widely cited productivity study in the Journal of Business and Psychology, finding that 71% of senior managers considered their organization's meetings "unproductive and inefficient," and 65% said meetings prevented them from completing their own work. The year was not unusual. The numbers have barely moved in the decade since.
You are not just a victim of this problem. If you have called a meeting in the last month, you are also a contributor to it.
The Difference Between a Topic and a Destination
Almost every bad meeting has the same structural flaw: it was organized around a topic rather than a destination. "Project X update" is a topic. It describes a subject the group will orbit. "Decide whether to delay Project X launch by two weeks or hold the original date" is a destination. It describes where the conversation needs to land.
The distinction matters because topics have no natural end. You can discuss the project update indefinitely. You can add context, background, complications, opinions, and tangents, and the topic will absorb them all without complaint. A destination, by contrast, is either reached or it is not. When the group decides on the launch date, the meeting is over. When you have no destination, the meeting ends when time runs out - which is a completely different thing.
Think of it like the difference between a sailing trip and a voyage. A sailing trip ends when you feel like heading back in. A voyage ends when you arrive. You want to be running voyages.
Writing the One-Sentence Test
Before you send any meeting invitation, you should be able to complete this sentence: "By the end of this meeting, the group will have ___." If you cannot complete it in a single clause - without using the word "discussed" or "reviewed" or "touched base on" - the meeting is not ready to be scheduled.
Fill in that blank with a verb that describes a concrete output. "Decided which vendor to contract for Q3." "Identified the three biggest blockers on the rebrand and assigned an owner to each." "Approved or rejected the proposed budget reallocation." These are completable. They tell every participant exactly what their job is before they even read the agenda.
This is not a bureaucratic exercise. It is a cognitive forcing function. When you try to write the one-sentence test and find yourself unable to, you are discovering - before you waste twelve people's time - that you do not yet know what you actually need from the group. The fix is to figure that out first, then schedule the meeting.
Key Point: A meeting organized around a topic gives participants no signal about what success looks like. A meeting organized around a destination tells participants exactly what they are there to accomplish - and gives the facilitator a clear criterion for knowing when to end the meeting.
The Agenda Is a Contract, Not a Preview
Sending an agenda the morning of a meeting is not the same as not sending one, but it is close. An agenda sent twenty-four hours in advance does something that a same-morning agenda cannot: it gives participants time to prepare.
Preparation is not just about reading materials. It is about cognitive priming - the process by which your brain does low-level processing on a problem before you consciously engage with it. When you give someone a day to sit with the question "should we delay the launch," they arrive at the meeting having already turned it over subconsciously. Their first contribution is better. The group reaches resolution faster.
Your agenda should contain three things and nothing else: the destination sentence, the specific questions the group needs to answer to get there, and any material someone needs to have read in order to contribute meaningfully. It should not contain vague items like "team updates" unless those updates are genuinely decision-relevant. If they are informational only, send them in an email. Information transfer does not require a meeting.
Handling the "Can You Just Add Me?"
Every meeting has them: people who want to be included for political reasons rather than functional ones. They are not bad actors. They are just responding rationally to an organizational culture that equates meeting attendance with relevance.
Your job is to make the functional criteria explicit. When someone asks to be added, the only fair question is: "Which part of the destination requires your input or authority?" If they can answer that cleanly, they belong in the room. If they cannot, they belong in the post-meeting summary. That distinction is not an insult - it is a description of their role.
The most respectful thing you can do for someone's time is to not invite them to meetings where their presence is decorative.
Key Point: Meeting attendance should be determined by function, not politics. The destination sentence is your filter: if someone cannot connect their presence to the specific output the meeting is designed to produce, they are not a participant - they are an audience.