The 3-question meeting test (cancel, shorten, or run it properly)

To be honest, most meetings aren't "bad" in a dramatic sense. They're simply vague. Nobody is quite sure what the point is, everyone turns up with different expectations, and you walk out with that familiar feeling of having spent an hour talking without anything really moving forward.

If you recognise that pattern, this is the quickest fix I learnt a few years ago. It takes about 60 seconds, and it helps you decide whether to cancel the meeting, shorten it, or run it properly so it earns its place in your calendar.

Before we get into it, a quick reality check. When meetings start to annoy us, it’s tempting to message something blunt like “This meeting is pointless”, to quietly stop accepting invites or, worse, to passively attend. That often creates more friction than it solves, and in the worst cases, it can be misread as refusal or attitude.

The safer move is to stay calm, stay professional, and ask for clarity. That’s exactly what this test does.

The situation you’re trying to solve

You’ve got a diary full of “syncs” and “catch-ups”. People turn up, the conversation drifts into status updates, and you leave without a decision, without actions, and without anyone clearly owning the next step.

The impact is bigger than it looks. Your time disappears, your own work gets squeezed into evenings, decisions get re-argued the following week because nobody captured them, and your reputation slowly shifts from “effective” to “always busy”. Over time, that’s exhausting.

Three safe routes (so you don’t feel trapped)

When you’re dealing with meeting overload, you’ve got three sensible options. The default is to reset expectations: clarify what the meeting is supposed to produce (its purpose), tighten what gets discussed, and end with clear owners and dates. If the number of meetings is the problem, you can set a limit by saying no to meetings that don't pass the test and offering an update instead. And if the problem is bigger than one meeting because your company culture is “meeting equals work” and nothing changes, then you escalate carefully by proposing a simple team standard like “no outcome, no meeting".

The 3-question meeting test

Before you accept or run a meeting, ask these three questions.

1) What is the outcome?

Not the topic but the wanted outcome or purpose of the meeting. For example, are we trying to make a decision, agree on a plan, align on a direction, or solve a specific problem?

If the organiser can’t explain the outcome in one sentence, that’s a warning sign the meeting isn’t ready. In that case, the best fix is often to ask for the outcome and suggest you reschedule once it’s clear.

2) Why does it need to be real-time?

Plenty of meetings exist because people feel they should “sync”, when a short written update would do the job.

If the purpose is mostly sharing information, then consider asking for a quick update email. Keep meetings focused on what they do best, such as making decisions, negotiating tradeoffs, and resolving roadblocks.

3) Who owns the next step, and by when?

This is where meetings either become useful or become recurring calendar clutter.If you can’t name an owner and a date for the next step, you’re very likely to have the same meeting again next week, with the same conversation and the same frustration.

Copy/paste scripts you can use immediately

If you want words that work without creating drama, start here.

Open with clarity:“Quick check — what outcome do we need from this meeting: a decision, a plan, or alignment?”

Move status updates:“If it’s mostly status, could we do those by update email and use meeting time only for decisions?”

If someone pushes back:“Happy to join when there’s a decision to make. If not, I’ll send a short update in writing so we don’t waste time.”

What to do next (a simple action plan)

Once you’ve used the test, the next steps are straightforward. Ask for the outcome in one sentence. If the outcome is unclear, suggest cancelling or going for a written update rather than guessing. If the outcome is clear, shorten the meeting to the minimum time needed. A focused fifteen to twenty-five minutes can often be plenty. Always leave yourself 5 minutes to get between meetings if you end up with back-to-back commitments. This gives you some breathing space and time to focus on the next meeting.

Then tighten the structure: ask for an agenda that covers no more than three items, each time-boxed. At the end of the meeting, say the decisions and actions out loud, including who owns what and by when. Finally, send a short recap ASAP, because that’s what makes decisions stick.

The “quiet protection” that stops meetings repeating

This last part is the bit most people skip, and it’s the part that quietly protects you.If you recap what was agreed on, e.g. the decision, the owners, the dates, and any trade-offs like “we moved Y to next week", you stop the cycle of “I thought we agreed…” and “no, I thought you were doing…”.

Keep it factual and neutral. Avoid sarcasm, avoid blame, and definitely avoid emotional venting in writing. A simple line like this is all you need: “Recapping: we decided X. Name owns Y by date. The next checkpoint is date/time.”

A quick example (what this looks like in real life)

Imagine a weekly sixty-minute “sync” that has turned into people reading their updates out loud. You ask for the outcome, you move progress updates into a short written format, and you keep the meeting only for decisions and blockers.

What usually happens next is the meeting shrinks to twenty minutes, actions become visible, and you get fewer midweek surprises because risks are surfaced earlier.

Final thought

If you take one thing from this, let it be this: meetings become tolerable when they have an outcome or purpose, a reason to be real-time, and a clear owner for the next step.

If you’re unsure what to do, start with the reset route and run the three questions. If overload is the issue, set a boundary and ask for written reports where you can. And if it’s systemic, propose a simple standard so your team stops filling calendars by default.