The Meeting That Solved Nothing (But Made Everyone Feel Better)
Fourteen people. Ninety minutes. A shared screen with bullet points. Action items assigned. Everyone leaves feeling productive.
Three weeks later, the same items appear on the same agenda. Different wording, same problems. Nobody mentions the pattern.
This is not a meeting problem. This is a systems problem wearing a meeting's clothes.
The Performance of Progress
Somewhere along the way, businesses confused the appearance of coordination with actual coordination. The weekly check-in became sacred — not because it drives results, but because it feels like leadership is happening.
You know the format. Status updates that nobody acts on. Problems raised and then parked. Decisions that require "further discussion" which never occurs. The meeting ends, everyone disperses, and the real work continues exactly as it did before.
The calendar shows alignment. The reality shows drift.
Why This Happens (And Why It Keeps Happening)
Meetings like this survive because they serve a psychological function, not a business one. They reassure owners that the team is connected. They give managers a stage. They let employees feel heard without anything actually changing.
But here's the cost: when meetings become theatre, they train your team to treat all process as theatre. If the Monday meeting doesn't lead to consequences, why would the CRM update? Why would the handover document? Why would the quality check?
Your systems start to decay from the inside. Not because people are lazy, but because you've demonstrated — repeatedly — that going through the motions is enough.
A Practical Example
A services business in Belfast held a fortnightly operations meeting. Fifteen people, two hours, comprehensive agenda. The owner believed it was the backbone of communication across departments.
When we audited their workflows, we found something telling: decisions made in meetings weren't being recorded anywhere except in the minutes document that nobody opened after the meeting ended. Action items had no owners, no deadlines, and no mechanism for follow-up.
The result? Teams were solving the same problems independently, often in conflicting ways. A pricing change agreed in April was still being ignored by half the sales team in July. Not out of defiance — they simply didn't know. The meeting had discussed it. The system hadn't embedded it.
The Gap Between Said and Done
This is the quiet failure mode that doesn't show up on dashboards. Your business says it has processes. Your team attends the meetings, fills in the forms, updates the trackers.
But what's actually happening underneath?
- Decisions are made verbally and forgotten within days.
- Ownership is implied but never explicit.
- Accountability exists in theory but has no mechanism.
- Follow-through depends entirely on individual memory and initiative.
The result is a business that looks coordinated on the surface but fragments under pressure. When something goes wrong, everyone remembers a different version of what was agreed.
What a Functional Meeting Actually Requires
A meeting that works isn't about better agendas. It's about what happens before and after.
Before: The issues being discussed should already be visible in your systems. If you're reviewing sales performance, that data should be live, not compiled manually the night before. If there's a problem with a project, it should have been flagged in writing before anyone walks into the room.
During: Decisions must be recorded with three elements — what was decided, who owns it, and when it's due. If those three things don't exist, you haven't made a decision. You've had a conversation.
After: Those decisions must feed directly into a system that tracks them. Not a minutes document buried in a shared drive. A live task, a CRM note, a project update — something with visibility and consequence.
The meeting itself is just a checkpoint. It's not where the work lives.
The Test You Can Run This Week
Pull up the minutes from your last three operational meetings. For each action item recorded, ask:
- Was it completed?
- Was it completed on time?
- Was it completed without someone chasing it manually?
If the answer is "no" to more than half, your meetings aren't broken — your execution layer is. The meeting is a symptom, not the cause.
The Illusion Worth Naming
A business can hold weekly meetings, send status updates, and maintain shared documents — while still operating in complete disarray underneath. The artefacts of coordination are not the same as coordination itself.
The question isn't whether your team is meeting. It's whether anything happens because of it.
Until that changes, you're paying for the appearance of progress — and wondering why the reality doesn't match.