How to Run a Meeting That People Actually Want to Attend

How to Run a Meeting That People Actually Want to Attend

The most productive meeting I have ever been in lasted seven minutes. It was a Tuesday morning at a mid-sized logistics company in Rotterdam, the weekly operations review for the Benelux region. Seven people. One agenda item at a time. Each person had exactly 45 seconds to flag a specific blocker. No context, no preamble, no "hi everyone." At the end, three decisions were made, two actions were assigned, and the meeting ended six minutes before the scheduled half-hour. Everyone went back to work. The company has been running that meeting, in that exact format, for eleven years.

Almost every meeting I've been in since has been worse than that one. Not because the people were less capable — the Rotterdam team was good, but not unusually good. It's because the meeting had been engineered. Someone, years ago, had thought carefully about what the meeting needed to do, what it didn't need to do, and how to run it so that the useful signal wasn't drowned in ambient noise.

The default state of corporate meetings is badness. If you leave a meeting alone, it gets worse over time — longer, less focused, less actionable, more political. Making a meeting good, and keeping it good, requires deliberate engineering. Here's the version that actually works.

The Four Question Test — Apply to Every Meeting You're Running or Attending

Before you run a meeting, and — equally importantly — before you accept an invitation to someone else's, the meeting must pass four tests:

  1. What specific decision, alignment, or information transfer requires synchronous time?
  2. Who is the minimum set of people needed for that?
  3. What would make this meeting a failure, and how will we know?
  4. Could this be an email, a Loom, or a one-on-one instead?

If you can't answer (1) in one sentence, don't have the meeting. If the list in (2) has more than seven people, at least two shouldn't be there. If you can't answer (3) with specific outcome criteria, the meeting is theatre. If the honest answer to (4) is "yes, this could be a Loom," send the Loom.

These four questions kill roughly 40% of meetings in any organisation that actually applies them. The remaining 60% run better because they've been interrogated before they happen.

The Three Meeting Types — and Their Distinct Rules

Not every meeting is the same shape. The single most common error in meeting design is treating one type like another.

Type A: Decision meetings

You need a decision made. A specific person (usually you) has the call. Others are there to inform, challenge, or endorse.

Rules:

  • Maximum six people. Five is better.
  • Pre-read sent at least 18 hours in advance, no exceptions. Do not tolerate the practice of presenting a deck in the meeting itself — Amazon banned this in 2004 and their decision quality improved measurably.
  • The first 10 minutes should be silent reading of the pre-read if it wasn't sent in advance. Uncomfortable but effective.
  • The decision owner names the decision out loud at the beginning: "I'm going to decide X in this meeting. Here are the options."
  • The decision gets made in the meeting, not afterwards. If you can't decide by the end, the pre-read was insufficient — not an excuse to schedule another meeting.

Type B: Alignment / status meetings

Multiple parties need to share state with each other. Often weekly or fortnightly. No major decision is expected.

Rules:

  • Short. Thirty minutes maximum. Fifteen is often enough.
  • Each person has a time-boxed slot — 90 seconds, two minutes. Tight.
  • The agenda is rigidly consistent week to week: this week's progress, blockers, next week's focus. Don't reinvent the structure every time.
  • Anything that requires discussion beyond two minutes gets flagged and handled in a smaller follow-up, not in this meeting.
  • The facilitator's job is ruthless time-keeping. Signal when someone's slot is up. No politeness allowed.

Type C: Brainstorm / creative meetings

The agenda is genuinely to generate new ideas or explore a problem. Rarer than people claim — many "brainstorms" are actually Type A meetings in disguise.

Rules:

  • Structured generation first, discussion second. Silent ideation for 10 minutes — each person writes ideas independently before any discussion happens. This single change triples the quality of ideas surfaced, according to every study on group creativity since Yale's Osborn research in the 1950s.
  • Maximum eight people, usually fewer.
  • Explicitly separate the generation phase from the evaluation phase. Do not let anyone critique an idea in the first 30 minutes.
  • End with specific next steps — who does what by when — or the creative work will not convert into progress.

The Opening Two Minutes — the Highest-Leverage Part of the Meeting

The first two minutes determine whether the meeting will be useful. Not the final two minutes, which everyone pays attention to. The opening.

A useful opening template:

  1. One sentence on why we're here and the specific outcome we need.
  2. One sentence confirming who's responsible for what (facilitator, decision-maker, note-taker).
  3. One sentence on the time constraint and when we'll stop.

That's it. Thirty seconds, done properly. Most meetings start with five minutes of "how was your weekend" and people logging in late. This is the meeting equivalent of a warm-up lap. By the time the substantive work starts, 20% of the allocated time is gone and focus hasn't hardened.

The fix requires a social contract. Start exactly on the hour. Begin substantive work inside the first minute. Latecomers are caught up on their own time, not on the meeting's time. This feels rude for about three weeks and then becomes normal — and everyone starts arriving on time.

The Facilitator Role — Specifically Named, Not Assumed

Most meetings have no facilitator. They drift because no one is explicitly responsible for drift. The fix: for every recurring meeting, name the facilitator at the top. Rotate monthly if you want to share the load, but there must be one person whose job in the meeting is keeping it on track.

What the facilitator actually does:

  • Enforces the time slots. Signals when someone's running over.
  • Redirects when the conversation wanders. "Let's come back to the agenda item — we can pick up the other thread after."
  • Forces decisions when a decision is being avoided. "It sounds like the decision is X. Are we agreed?"
  • Captures actions as they're made, in real time, visibly (shared doc, whiteboard).
  • At the end, reads back the actions and owners and confirms with the room.

The person running the meeting is often also a participant — they have opinions on the content. The facilitator role is separable, and in higher-stakes meetings it's worth separating. The chair owns the content; a different person owns the process.

The Thirty-Second Rule for Questions and Interventions

A rule that quietly makes meetings better: any individual contribution should be under 30 seconds. A question, a point, a response — 30 seconds. If you need more, you're giving a speech, which is a different genre and should be preceded by "I'd like to take a minute on this" so the room knows to invest.

The 30-second rule does three things. It forces people to think before speaking. It prevents the usual pattern where one or two verbose participants consume 60% of the airtime. And it creates space for quieter people to contribute, because they can plan a short intervention in a way they can't plan a long one.

When someone violates the rule repeatedly — some people do — the facilitator's job is to interrupt. Polite, direct. "That's helpful — give us the headline?" Most people take the hint. The ones who don't are usually the ones whose contributions are worth the least anyway.

The End of the Meeting — the Second-Most-Important Two Minutes

Every meeting ends with a specific closing ritual. The facilitator says, out loud:

  • "Here are the decisions we made today."
  • "Here are the actions, each with an owner and a date."
  • "Is there anything unresolved we need to carry forward?"

This takes 90 seconds. It is the single highest-leverage 90 seconds in the meeting, and most meetings skip it entirely. Without it, you have five people leaving with five different interpretations of what just happened. Within 48 hours, the meeting has effectively produced nothing, because nobody agrees on what was decided.

The written follow-up — sent by the facilitator within 24 hours — is the belt-and-braces version. Decisions, actions, owners, dates. One paragraph. No narrative, no context, no "great meeting everyone." Just the record. The discipline of this habit, more than any other, is what separates meetings that move work forward from meetings that generate work without resolving it.

The Hardest Meeting to Fix Is the One You Inherited

Everyone has opinions about new meetings. The hard part is fixing recurring meetings that are already bad and that you've inherited. The political cost of changing them is real — people get attached to formats, cadences, and invite lists that have been in place for years.

The move that works best: don't try to change the meeting directly. Propose an experiment. "For the next four weeks, let's try a tighter version — 30 minutes instead of 60, pre-read required, decisions captured in writing. Then we'll review." Almost nobody refuses an experiment. After four weeks, the tighter version almost always wins, because the old version was bad and everyone secretly knew it. The experiment framing gives them political cover to acknowledge the obvious.

The Rotterdam meeting — the one that changed my entire view of what meetings can be — was engineered in 2013 by a then-32-year-old operations manager who was tired of wasting her mornings. She didn't have the authority to kill the meeting. She had the authority to propose a four-week experiment. The experiment ran, worked, and never reverted. Eleven years later, the meeting is still the most useful seven minutes of her team's week.