What We Found When We Actually Looked at How a Meeting Got Organised
Nobody thinks of scheduling a meeting as a significant drain on organisational time. It's just something that happens — a few emails back and forth, a calendar invite, done. Except in most organisations, it isn't quite that simple.
The situation
A department head at a medium-sized organisation asked us to look at why her team's calendar felt so chaotic.
When we looked at how meetings were actually being organised, the hidden cost became visible almost immediately.
What she was noticing
- ✓Meetings booked with little notice
- ✓Key people regularly unavailable at the times chosen
- ✓Preparation materials arriving late or not at all
- ✓Meetings ending without clear outcomes
The typical process
Someone decides a meeting is needed and emails to find a time
Replies trickle in over the next day or two — "can't do Tuesday", "Thursday but not after 3", "any day except Wednesday"
The organiser consolidates responses and sends a calendar invite for a slot that seems to work
Two people reply with a conflict. A new time is found. The invite is updated.
emails exchanged, on average, to organise one meeting
The meeting itself was forty-five minutes. The preparation for organising it — not preparing content, just finding a time — had consumed nearly as much collective time as the meeting would.
And that was before accounting for meetings scheduled without checking anyone's actual availability, because the organiser had given up on the email exchange and just picked a time and hoped.
The organisation had Microsoft 365, which meant they had Bookings, shared calendar visibility, and the ability to see free and busy time across the team. Almost none of it was being used.
Three changes
Shared calendars, configured properly
Everyone could see their colleagues' availability without sending an email to ask first.
A simple Bookings page
For recurring internal meetings, team members could book time directly — no back-and-forth required.
A clear norm, said out loud
Meeting invites had to include an agenda and preparation materials at the point of sending — not the morning of. This was the most significant change.
It sounds obvious. In practice, it almost never happened, because nobody had ever said it out loud as an expectation.
The email volume around meeting scheduling dropped noticeably within a fortnight. Meetings started with people who'd had a chance to prepare. Outcomes were clearer because the agenda had been visible in advance.
The lesson
The hours saved on scheduling were modest — but the improvement in the quality of the meetings themselves was harder to put a number on, and probably more valuable. Meetings where people arrive prepared and the purpose is clear make better decisions in less time. That compounds across every week of the year. Scheduling is one of those processes that organisations never examine because it feels too small to be worth examining. That's exactly why it's worth examining.
Does this sound familiar?
If any of this resonates — the wrong versions, the chasing, the tools nobody quite trusts — it's worth a conversation. Most of the problems we fix are more straightforward than they feel from the inside.
No obligation. No hard sell. If it's not the right fit, I'll tell you.
