One Team, One Week, Eleven Meetings Gone: A Calendar Audit in Five Books

The suspicion is common enough among UK managers: the team is not underperforming, it is over-scheduled. The diary fills first and the work fits around it. The experiment described here set out to test that proposition rather than assert it, over one working week, with a fourteen-person operations team at a Midlands manufacturing business (anonymised at the team's request).

The method was deliberately unglamorous. On the Monday, five diaries were exported — the manager plus four team leads — and every recurring series was tagged by purpose: decide, coordinate, inform, or ritual. Duration and attendee count were recorded alongside. The five books were read in the fortnight beforehand and each was assigned one job in the audit, rather than treated as general inspiration.

What the five books were asked to do

The Surprising Science of Meetings — Steven Rogelberg. Assigned to mechanics. Rogelberg's evidence on attendee numbers, agenda discipline and the value of stand-ups informed the tagging and the first round of cuts. It is the most useful of the five for this exercise because it is the least rhetorical: the recommendations can be implemented on a Tuesday.

Death by Meeting — Patrick Lencioni. Assigned to typology. The argument that most bad meetings are a type mismatch — a strategic question handled in a tactical slot — explained several series the team had been unable to justify or cancel. The book is a fable, and the evidence is anecdotal, but the categories are practically useful.

The Art of Gathering — Priya Parker. Assigned to the protected list. Parker is strongest on purpose and closure, and weakest on the routine operational sync. Her questions were applied only to the meetings that survived: why this gathering, why these people, and how does it end.

Deep Work — Cal Newport. Assigned to the honest conversation. Newport's contribution was not a technique but a refusal: a manager cannot schedule their way into protected time, only decline their way there. This proved the least comfortable book of the five.

Shorter — Alex Soojung-Kim Pang. Assigned to framing. The compressed-week evidence shifted the team's thinking from saving hours to budgeting them. Once the week's meeting load was expressed as a fixed budget rather than an open account, the cuts became easier to argue for.

What the audit found

The five diaries contained 68 recurring series, consuming 41 hours of team time each week — a little over 2,100 hours a year across fourteen people. Tagged by purpose, the split was roughly 38 per cent coordination, 27 per cent information-sharing, 22 per cent decisions and 13 per cent ritual. The ritual category, which included a fortnightly review that no attendee could date the origin of, was the smallest and the easiest to remove.

The single most expensive item was a Monday 09:00 week-ahead meeting: sixty minutes, eleven attendees, no agenda, and a habit of overrunning. It was replaced with a twenty-minute standing session and a written note circulated on Friday afternoon.

The eleven cuts

Eleven recurring series were removed or compressed. Four were information meetings where the content was already in a weekly written update. Three were project syncs at which, over two observed sessions, six of nine attendees said nothing. Two were duplicated coordination calls between sites. One was the Monday meeting. One was a monthly review that had become a status report by another name.

The measured return was nineteen hours of team time per week, close to 950 hours a year. That figure should be treated with some scepticism: not all of it becomes productive work, and some of it simply becomes email. The more reliable measure was the count of decision items closed per week, which rose from four to seven in the fortnight after the cuts.

What broke

Two things, both predictable in hindsight and neither visible on a calendar export.

The first was an escalation route. A site supervisor had been catching a supplier problem informally in a Thursday coordination call before it reached the formal process. With the call gone, the issue surfaced eleven days later and cost a week of production time. The lesson is that some meetings carry undocumented work, and a manager cannot see that work from a diary.

The second was external. A stakeholder in a neighbouring department who had attended a now-cancelled series felt excluded from decisions that affected her team. A fortnightly note was reinstated, addressed to her specifically.

One decision was also made worse. A supplier selection that had previously been discussed in a nine-person forum was closed in a three-person meeting. It was faster, and the choice was later questioned on grounds nobody in the smaller room had thought to test. Fewer voices is not automatically better; it is faster.

Decision quality, measured loosely

The remaining decision meetings were given a written pre-read 24 hours in advance and a named owner for each item. Three decisions that had drifted for weeks closed in the first fortnight, largely because the smaller rooms made it harder to leave without an answer. That improvement is real but modest, and it owes as much to the pre-read as to the cancellations.

What the team kept

A five-minute daily huddle, which had been widely mocked and which quietly replaced three separate email threads. The fortnightly review, restored at a shorter length, with an agenda circulated in advance. And the Monday note, which the manager now writes on Friday and which has become the team's most-read document.

If you run the same experiment

Four rules, drawn from what went wrong rather than what went right. Tag before you cut, so the purpose of each series is on record. Never remove a meeting without naming who owns the decisions inside it. Speak to the people who attend but never talk, because they are often the ones carrying the informal work. And review after thirty days, not after one week, because the costs of a cancellation arrive more slowly than the benefits.

The wider conclusion, after a month rather than a week, is that the team's diary was not the whole bottleneck — but it was hiding the bottleneck, which is nearly as bad. The five books between them supplied a method, a vocabulary and one uncomfortable question that no calendar tool asks: which of these hours would you defend if you had to justify it out loud?