How to Run Effective Meetings (and Why Most Fail)

Effective meetings are rare. They shouldn’t be.

Effective meetings don’t seem to happen very often.

Or is it just me?

After two decades inside organisations, I’ve come to a slightly uncomfortable conclusion: most meetings are ineffective by design. Too long. Too crowded. Too vague. Too polite. And strangely resistant to decision-making.

That matters — because meetings are expensive. Not just in time, but in attention, energy, and morale. They often sit between idea and value – and that is cost.

If you run meetings — or spend a good chunk of your working life inside them — it’s worth getting good at them. Not “slick”. Not theatrical. Just effective.

What a meeting actually is

A meeting, as I see it, is simple:

A gathering of people to make a decision that no single person can make alone.

That definition quietly rules out a lot of calendar nonsense and clutter.

• A brainstorming session? That’s a workshop.
• A strategy offsite? Also a workshop.
• A 1:1? A conversation.
• An interview? A meeting — a decision will be made from it.

If there is no decision to be made, I’d question whether you need a meeting at all.

Meetings exist because:

• the information is distributed,
• the expertise is shared,
• or the authority is collective.

When none of those are true, a meeting is usually a substitute for confidence.

Why meetings fail

Meetings tend to fall apart for predictable reasons:

• the wrong people are invited,
• the purpose isn’t clear,
• no one knows who decides,
• the meeting runs to time rather than outcome,
• politeness replaces honesty,
• consensus replaces judgement.

Large groups are particularly vulnerable to this. They’re good at generating ideas. Much worse at deciding between them — especially when responsibility is vague.

Before booking a meeting, ask yourself one honest question:

“Could I make this decision on my own?”

If the answer is yes — do that.

If not, then the meeting needs to earn its place.

Principles for effective meetings

There’s no single formula, but a few principles hold up remarkably well, taken from the Communication Superpower Workbook.

1. Decide before you invite

Know what decision needs to be made before you book the room. If you can’t name it clearly, neither can the attendees.

Invite only those who:

• hold relevant information,
• bring necessary perspective,
• or have decision rights.

Every additional person adds complexity and cost, not value.

2. Shorter beats longer

An hour is not a requirement — it’s a habit.

Book 25 minutes. Or 40.
Finish early and give time back.
Declare victory and leave.

Parkinson’s Law applies to meetings as much as it does to work.

3. Use an agenda — always

Not a formality. A signal.

An agenda answers:

• why we’re here,
• what we’re deciding,
• what preparation is expected.

No agenda?
It’s allowing vagueness, opinions and chaos to walk in ahead of you.

4. Set a few clear norms

Not rules for the sake of control — agreements that protect attention.

Start on time.
Participate honestly.
No passive nodding followed by private dissent.
Disagree in the room. Commit outside it.

Psychological safety matters here. Strong teams can challenge hard because trust exists. Until then, a few shared expectations help.

5. Presence beats performance

The most influential people in meetings are rarely the loudest.

They:

• sit comfortably,
• listen properly,
• speak clearly,
• ask good questions,
• say less — but say it well.

Presence isn’t dominance. It’s steadiness.

6. Capture what matters

Someone owns the notes.
Actions are named.
Decisions are recorded.
Follow-up is visible.

If nothing survives the meeting, the meeting didn’t really happen.

A quick word on contribution

If you have something meaningful to add, don’t save it for the final minute.

Late revelations often cost the group another meeting.

Speak when it matters.
Support what you say.
Then stop talking.

Listening is not a passive act — it’s the other half of influence, and the greatest compliment you could give someone.

And now… a familiar story

If all of this sounds a little idealised, let me show you the other version.

The one you probably recognise.

10:00am – You pitch up for the 10am meeting eager to get stuff done, only to find that the previous meeting is over running.

10:02am – After standing outside the meeting room making over enthusiastic “watch checking” gestures you decide to make a coffee.

10:05am – You return with your coffee. The meeting room is still busy with the previous meeting. No other attendees have turned up for your meeting yet.

10:06am – The Project Manager from the over running meeting holds up his index finger to indicate he will be no longer than one minute. You resist the urge to hold a different finger back at him.

10:10am – The previous meeting finally finishes. Attendees leave the room, scowling at you for making them end their meeting before any decisions were made.

10:15am – Still no one has turned up for your meeting. On a positive note though you’ve bagged the best seat at the back where you can “people watch” through the window.

10:17am – With no-one yet turning up for this meeting, you decide to make another coffee.

10:18am – Whilst making a coffee you suddenly become overwhelmed with a streak of mischievousness. You decide to unscrew the lid from the sugar pourer, so it looks like the lid is still on but it’s not really. Hilarious. The next person’s going to get more sugar than they thought.

10:20am – You return to the meeting room to find all the attendees there waiting for you. You’re now the last one to arrive. You are gobsmacked but make your apologies for being late. You now only have the choice of one chair. The one at the front.

10:21am – The Product Owner (PO) decides to make a phone call and leaves the room.

10:23am – The PO returns but the “decision making exec” decides she now wants to leave the meeting.

10:24am – The project meeting finally kicks off. First agenda point is raised; how to eliminate waste and unproductive activity in the project.

10:24:20am – You bite your lip and keep your late meeting comments to yourself, after all, everyone now thinks you were the late one.

10:26am – You start to throw rolled-up balls of paper at the tech lead.

10:27am – Apparently the defect count is down.

10:27:10am – Smiles and “hurrahs”

10:28am – The low defect count is because nobody is doing any work as the IT systems have crashed the servers. General feeling of disappointment floods around the room.

10:36am – After more pointless stats, cost models and other illusions of productivity, the urge to go to the toilet is high.

10:45am – The PO announces, after checking emails on his phone during the meeting, that the CEO has just had a sugar-shaker full of sugar dumped in his coffee, and demands that the child responsible for this behaviour steps forward.

10:45:10 am – You face turns grey. You feel faint.

10:45:20 am – You start humming with nervous energy.

10:45:30 am – You are asked top humming.

And to sit still.

And to stop throwing bits of paper at people.

And whether you are ok because your face is really grey.

10:48am – The discussion moves to team morale.

10:49am – A blame session erupts and heated exchanges are made. Even though it is “not a blame culture”, it is definitely the product lead’s fault.

10:52am – Someone suggests a coffee break, someone else suggest we just abandon the meeting. The PO suggests we press on.

11:09am – The meeting ends after being harangued by the next meeting room attendees. The group disperse. You charge to the toilet. The only decision made was that the team need another meeting.

11:15am – You turn up late to your next meeting, an ironically scheduled training session from HR......on….time management.