Why Meetings Fail, and the Simple Rules That Fix Them

Meetings are not effective because nobody decided what the meeting was for. A meeting can make a decision, surface information that exists only in people’s heads, get work done together, or build agreement on something contested. Each of those needs a different length, a different guest list and different preparation. Most bad meetings are the mismatch.

This is the general diagnosis rather than a guide to running any particular session. It covers what actually goes wrong, the short set of rules that address it, and two pieces of received wisdom that get quoted more than they deserve.

Why are meetings not effective?

Because the failure happens when the invite is created, not in the room. Someone has a feeling that the group should get together on a subject, picks a length from the calendar’s defaults, and invites everyone plausibly connected to it. Nothing in that sequence involves deciding what has to be true when the hour ends.

By the time people arrive, the meeting is carrying several incompatible jobs. Half the room came to be informed, two people came to argue, and one came because they always come. The chair cannot satisfy all three, so the meeting drifts to the safest of the three, which is talking about the subject. Everyone leaves feeling it was fine and nothing changes.

There are roughly four honest reasons to put people in a room together. Each has different requirements.

What the meeting is for	What has to exist before it starts	Rough size	How you know it worked
Make a decision	The options in writing, and a named decider	Small enough that everyone speaks	A choice was made and written down
Surface what only exists in people’s heads	A question specific enough to answer	Whoever holds the knowledge, plus whoever needs it	Something was said that nobody could have written in advance
Do the work together	The work itself, open in front of people	Only the people doing it	The work is further along than when you started
Build agreement on something contested	An honest statement of the disagreement	Everyone who could block it	The people who disagreed can state the other side accurately

Note what is not on that list. Reporting progress is a broadcast, and a broadcast does not need everyone in the same hour. Nor does approval of something already agreed elsewhere.

The failures follow from mixing the jobs

Almost every recognisable bad meeting is one of the four jobs run with another one’s setup. Four that show up everywhere:

• The decision meeting with fifteen attendees. It was sized like a briefing, so it behaves like one. Past a certain headcount people stop arguing and start being careful, and the choice gets deferred to a smaller conversation that happens afterwards anyway. Settling who holds the call before anyone is invited is the cheapest available fix.
• The status meeting that could have been a message. Nine updates delivered live, seven of which concern nobody else present. It survives because it feels like management and asks nothing of anyone.
• The working session where nobody brought the work. The document was going to be drafted together, and the hour goes on agreeing what should be in the document. Working sessions need the artefact open on screen from minute one, or they turn into planning the working session.
• The alignment meeting run as a presentation. Contested things do not become agreed because someone presented forty slides at them. Disagreement that is not spoken in the room gets spoken in the corridor, and then in the delivery phase, at much greater cost.

The pattern is the same each time. The organiser knew the subject and never chose the job.

Five rules that cover most of it

These are not a methodology. They are the small number of things that, done consistently, remove most of the failures above. Each one exists to prevent a specific failure.

1. Name one decider for anything that needs a decision. Prevents the meeting that ends with “let’s take that away and pick it up next time”. If nobody can say who makes the call, the room will search for consensus, fail to find it, and adjourn.
2. State what each agenda item has to produce. Prevents the item that gets discussed for twenty minutes and closed with a nod. “Supplier contract” names a topic. “Agree whether we extend the supplier for six months or go to tender” names a result, and anybody can see whether the item closed. The handover from agenda to discussion is where most of this leaks away.
3. Either the pre-read gets read, or you read it in the room. Prevents the first half of the meeting being a summary of the document for the people who did not open it. Reading in silence for eight minutes at the start feels strange for about a week and then feels normal. It is also honest about what was happening anyway.
4. Keep the guest list down to what the job needs. Prevents the careful, quiet, expensive meeting. A useful test: the right list is the set of people you would have had to consult one by one if the meeting never happened. The rest can read what came out of it, which is a better use of their morning.
5. Get the decisions and owners into writing before the room empties. Prevents the account that everybody nods at afterwards and nobody works from. Written later, the record is one person’s memory of the discussion, and the qualifications people attached to their agreement are the first thing to fade. Whether you want notes, a transcript or formal minutes depends on the meeting, but something has to exist before people disperse.

None of that is difficult. It is unpopular, because each rule involves telling someone their meeting is not what they thought it was.

The two rules everyone quotes that do less than they promise

Two lines get repeated in every conversation about meetings. Both contain something true and both stop short of being useful.

“No agenda, no attenda.” It is memorable and it is not much help, because the agenda is usually the problem rather than its absence. Most agendas are a list of nouns: budget, hiring, Q3, AOB. A room can spend an hour on a list of nouns and finish exactly where it started, and the invite was fully compliant. The rule people actually need is stricter. Decline the invite when you cannot tell what the meeting is supposed to produce, whether or not a document was attached.

“This could have been an email.” Frequently true, and worth saying out loud more often than it is said. It also flattens a real distinction. Some things genuinely need argument in real time, because the disagreement is not yet articulate enough to be written down, and email is a poor place to work that out. Broadcasting information asynchronously is easy. Resolving a contested question asynchronously is a different skill, and teams that assume the two are the same end up either meeting about everything or writing long threads that settle nothing.

There is a third shape that neither slogan accounts for: a written discussion with structure, where the questions are put in a fixed order and people answer in their own time. Projan is built around that for planning specifically, pulling an existing brief or ticket in as context and then asking the scope and ownership questions in a Slack or Microsoft Teams thread rather than booking an hour to ask them out loud.

Nobody ever deletes a recurring meeting

Meetings are created in about eight seconds and removed almost never. That asymmetry, not any individual bad hour, is what fills a calendar. The weekly that made sense during a launch is still running eighteen months later because cancelling it would be a small act of judgement about someone’s work, and nobody wants to be the person who says the thing they set up is no longer needed.

The discipline that fixes it is unglamorous: give every recurring slot an expiry the day you create it, written into the invite, and treat that date as a real question rather than an administrative one. Two questions make the review honest. Who would notice if this stopped? And what has this meeting changed in the last month that would not have changed anyway? A meeting that cannot answer either one is a habit with a room booking.

Halving the frequency is usually a better first move than deleting the slot outright. It gives you evidence, and people accept it more readily. If nothing breaks at fortnightly, the answer to the original question is now obvious to everybody, and chasing the actions between meetings turns out to have been doing the real work all along.

What is the 10-10-10 rule for meetings?

There is no single agreed meeting rule of that name, so treat any confident definition with suspicion. Most often the phrase points at Suzy Welch’s personal decision heuristic, which tests a choice against three horizons: ten minutes from now, ten months, ten years. That is about decisions rather than meetings, and it gets borrowed into management contexts fairly loosely.

The version people quote as a meeting rule is usually a timeboxing device: split a thirty minute slot into ten minutes of context, ten of discussion and ten of deciding. That is a reasonable shape for a short decision meeting and a poor one for a working session, which needs the whole slot on the work. Use it as a default if it helps, but the split is a scheduling convention, not a finding.

What are the 3 C’s of a meeting?

The three C’s are a mnemonic rather than a standard, and the letters change depending on who is teaching it. There is no authoritative source, so anyone presenting one version as the definition is guessing. The formulation that circulates most widely is:

1. Clarity. Everyone can state what the meeting has to produce before it starts. If the chair and the attendees would give different answers, the meeting has already failed and just has not noticed.
2. Contribution. The people with something to add actually said it. A meeting where two people spoke for fifty minutes and six people spoke for none did not need six of them.
3. Conclusion. It ended with something written: a decision, an owner, a date, or an explicit statement that the question remains open and who is holding it.

Other versions substitute content, context or conduct for one of the three. The variations matter less than the fact that all of them are checking the same three moments: before, during and at the end. If you want the mnemonic to earn its place, apply it as a test after the meeting rather than a plan before it. Clarity and contribution are hard to judge in advance and obvious in hindsight.

Frequently asked questions

Is it rude to decline a meeting invitation? No, provided you say why and offer what you can give instead. Reply asking what the meeting has to produce and whether your input is needed live or in writing. Most organisers answer honestly and half of them realise they invited you out of politeness. Declining silently is the rude version, because the organiser cannot tell whether you saw it.

What should you do if the person who has to decide cannot attend? Move the meeting or get the decision delegated in writing before it starts. A decision meeting without the decider becomes a rehearsal, and rehearsals are expensive. If the decider genuinely cannot come and will not delegate, run the session as a working meeting instead, produce a written recommendation, and give them a deadline to accept or reject it.

Can one person fix meetings in an organisation that runs them badly? Only the ones they own, which is usually enough to matter. Fix your own invites first: state the outcome, cut the guest list, write the decisions down before people leave. Colleagues notice the difference in the meetings they attend. Trying to reform everyone else’s calendar without any authority tends to produce a policy nobody follows.

How do you end a meeting that is overrunning? Stop five minutes early on purpose and spend the time restating what was agreed and who is doing what. If the discussion is not finished, name the open question, name who takes it forward, and book the follow-up before people disperse. Running over quietly borrows time from whatever people had planned next, and they will remember that more clearly than the discussion.

Meetings do not fail because people lack facilitation skills. They fail because the hour was booked before anyone decided what it was for, and no amount of good behaviour in the room recovers that. Decide the job, size the room to it, and write down what came out.