Bad meetings: The cost and signal of the organization

• Quick math: how much bad dates are costing you (with an example)
• 7 signals that meetings are not a communication problem, but a system problem
• 3 causes that make a "meeting" (decision rights, rhythm, standard)
• Minimum meeting operating system (4 meetings + output)
• Rules that immediately reduce the number of meetings
• Checklist for the first 14 days
• The most common mistakes (and how to avoid them)

How much bad dates really cost you

(an example that you can calculate immediately)

The cost of a meeting is not just the hourly rate of the people in the room. But let's start from the basics, so that it is tangible and you can calculate immediately.

Formula

Quick example

Let's say you have a weekly operations meeting:

• 6 people
• average hourly wage 20 EUR
• lasts 60 minutes (1 hour)
• held once a week

Then the cost per meeting is:

And on a monthly basis (4 weeks):

And that's just the "visible" cost.

What usually doesn't count (and is often more expensive)

• context switching (after the meeting it takes time for people to "get back to work")
• delaying decisions (the problem drags on for weeks)
• rework (the same thing is done several times because the standard and criteria are not clear)

If you want a simple metric: a bad meeting is the one after which the number of escalations increases.

7 signals that meetings are not a communication problem but a system problem

If you recognize yourself in this, you don't need "better facilitation". You need a clearer system.

• The meeting ends without a decision
• After the meeting, messages arrive: "Just checking with you..."
• It is not clear who owns the next step
• The meeting is a status update, not a blocker resolution
• The same topics return week after week
• Decisions are made outside the meeting (ad hoc), so the team does not have a common context
• The operation escalates to one person, even when it is not critical

If you want to quickly diagnose where the system breaks (decision rights, rhythm, standard) and stop putting out fires through meetings, start from business analysis.

What bad meetings reveal: 3 systemic causes

Bad meetings are the consequence. The cause is usually one (or a combination) of these three:

1) Decision rights are not clear

When it is not clear who gets to decide, meetings become a "place for approval". People come for confirmation, not for a decision.

Practical test: if the same type of question escalates more than 3 times in two weeks, it is not a problem in humans. This is a signal that the decision rule is missing.

2) There is no operational rhythm

When there is no rhythm, everything is solved ad hoc. Meetings are scheduled because it is "on fire", not because there is a predictable management mechanism.

Rhythm does not mean more meetings. Rhythm means that decisions are made on time.

3) The quality standard is not defined

When the criteria are not clear, the meeting becomes a place to "negotiate" what is good enough. That's why things go back for work and that's why the team goes around in circles.

The solution is not control. The solution is standard.

The solution: a minimal meeting operating system

The goal is not to have perfect dates. The goal is for meetings to stop being a substitute for the system.

The minimum system includes:

• a clear purpose for each meeting
• clear output (decision, owner, term)
• a rhythm that is stable (so that the team does not live in exceptions)

If you want the team to adopt this as a standard (not as "another initiative"), Efficient Management training is a good next step

4 meetings that work in most teams (and what the output is)

You don't need 12 dates. You need 4 mechanisms that cover planning, exceptions, learning and decisions.

1) Weekly planning (30–45 min)

Purpose: agreement on top priorities and risks.

Output:

• 3–5 priorities
• Who is the owner?
• what is risk and how do we cover it

2) Short sync (2x a week, 15 min)

Purpose: exceptions only.

Rule: don't go through all tasks. It only talks about:

• What's late?
• what is blocked?
• What decision is needed?

3) Weekly review (30 min)

Purpose: closing the loop.

Output:

• what is finished
• what is not and why
• what decision is made so that the problem does not happen again

4) Monthly KPI/retro (60 min)

Purpose: trends and causes.

Output:

• 2–3 key insights
• 1-3 resolutions for the next month
• what do we change in the process/routine

Rules That Instantly Reduce "Meeting"

These are the rules that most quickly return control to the operative:

• There is no meeting without an agenda.
• Without an owner, there is no task.
• Each meeting ends with: decision + owner + deadline + next step
• The status goes asynchronously (before the meeting), the meeting serves for decisions. For asynchronous status and clear agreements, Microsoft Teams can be a great framework if set up correctly
• If there is no decision, there is no need for everyone to be there

Checklist for the first 14 days

If you want to move without major reorganization, start like this:

1. List the top 10 topics that keep meetings recurring
2. For each topic, define: team decides / needs approval / escalates
3. Switch 50% update status to asynchronous (shortly before the meeting)
4. Introduce a weekly review that ends with decisions (not conclusions)
5. Define Definition of Done for 3 key deliverables (not to go back for rework)
6. Measure: number of meetings, number of decisions, number of escalations (before and after) If you want owner + deadline + next step to be visible to everyone (without additional meetings), Microsoft Planner is the fastest way to introduce it

The most common mistakes (and how to avoid them)

• You add more meetings instead of establishing a rhythm
• You change the format, but the decision rights remain unclear
• You try to "fix people" and the system remains the same
• You keep the quality standard in your head, so everything comes back to you

Related blogs