Most organisations talk about having too many meetings. Very few actually do anything about it. The reasons are predictable: meetings feel productive even when they are not, cancelling someone's meeting feels personal, and nobody wants to be the executive who misses the one discussion that turns out to matter. So the calendar stays packed, 62 meetings per month on average, and everyone quietly accepts that this is simply what work looks like. But one mid-sized technology company decided to challenge that assumption head-on. Over the course of a single quarter, they reduced their total meeting hours by 60 per cent — and saw productivity, employee satisfaction, and decision speed all improve measurably. This is not a theoretical framework. It is a practical account of what they did, what went wrong, and what you can learn from their experience.

The company succeeded by auditing every recurring meeting, eliminating those without clear decision outcomes, shifting status updates to asynchronous channels, and introducing two meeting-free days per week. The playbook is replicable for any leadership team willing to tolerate short-term discomfort.

The Problem They Were Trying to Solve

The company, a 400-person technology firm with offices in three cities, conducted an internal time audit that revealed a startling figure: their senior leadership team was spending an average of 27 hours per week in meetings. That left fewer than 15 hours of productive work time, and much of that was fragmented into 30-minute gaps between sessions. The executives were not making decisions in these meetings — they were listening to updates they could have read in five minutes.

Employee surveys told the same story from a different angle. Seventy-one per cent of staff rated their meetings as unproductive, mirroring the broader Harvard Business Review finding. Middle managers reported spending four hours per week preparing for status meetings that added no value beyond what a shared document could provide. The cumulative cost, when calculated using loaded salary figures, exceeded half a million pounds annually for the leadership team alone.

The breaking point came during a quarterly planning session that ran three hours over schedule. The CEO asked a simple question: how many of the 14 agenda items required everyone in the room? The answer was two. The remaining 12 could have been handled by smaller groups, asynchronous updates, or not discussed at all. That conversation launched the meeting reduction initiative.

The Audit Phase: Understanding What Meetings Actually Do

Before cutting anything, the company spent two weeks categorising every recurring meeting into four types: decision meetings, information-sharing meetings, relationship-building meetings, and legacy meetings. Decision meetings had a clear question to resolve and a defined decision-maker. Information-sharing meetings existed to broadcast updates. Relationship-building meetings served team cohesion. Legacy meetings were those that nobody could explain but nobody wanted to cancel.

The results were sobering. Only 22 per cent of recurring meetings were genuine decision meetings. Thirty-eight per cent were information-sharing, 12 per cent were relationship-building, and a full 28 per cent were legacy meetings — gatherings that had outlived their original purpose but persisted through inertia. The Bain research finding that the average meeting has two to three attendees too many proved accurate here as well; most meetings included at least three people whose presence was neither required nor valuable.

Armed with this data, the leadership team applied a simple rule: information-sharing meetings would be replaced with written updates, legacy meetings would be cancelled immediately, and decision meetings would be restructured using the RAPID framework to ensure the right people, and only the right people, were in the room. Relationship-building would be preserved but moved to informal formats.

The Reduction Strategy: What They Actually Changed

The company implemented four changes simultaneously. First, they cancelled every legacy meeting — a total of 34 recurring events across the organisation. This alone freed up roughly 120 hours per week of collective time. Second, they replaced all status update meetings with a Monday morning written brief that each team lead submitted by 9 a.m. The brief followed a strict template: three accomplishments, three priorities, one blocker. Anyone who wanted to discuss a blocker could request a 15-minute slot.

Third, they introduced two meeting-free days: Tuesday and Thursday. On these days, no internal meetings were permitted except genuine emergencies, defined as issues that would cost the company money or customers within 48 hours. Research from MIT Sloan had shown that companies with meeting-free days reported 73 per cent higher employee satisfaction, and the company wanted to test whether the same held true for them.

Fourth, they applied the 50/25 Meeting Rule to all remaining meetings. Every 60-minute meeting became 50 minutes; every 30-minute meeting became 25. This created natural buffers between sessions, addressing the Microsoft Human Factors Lab finding that back-to-back meetings reduce cognitive performance by 20 per cent. The buffers were not optional — calendaring software was configured to enforce the shorter defaults.

The Resistance and How They Managed It

Not everyone embraced the changes. Several department heads argued that their meetings were different, essential, and could not possibly be replaced with written updates. The CEO addressed this by asking each sceptic to run a two-week experiment: cancel the meeting, send the written update instead, and track whether any decisions were delayed. In every case, the answer was no. The information still flowed; it simply flowed through a different channel.

Middle managers faced a different challenge. Many had built their professional identity around facilitating meetings. Removing meetings felt like removing their role. The company addressed this by redefining the management expectation: instead of running meetings, managers were evaluated on the clarity of their written communication and the speed of their team's decision-making. The shift was uncomfortable but ultimately empowering.

The most unexpected resistance came from junior staff who relied on meetings for visibility. In a meeting-heavy culture, attendance was a proxy for importance. When meetings disappeared, some employees felt invisible. The company solved this by creating a weekly showcase channel where anyone could post a short summary of their work. Visibility was maintained without the time cost of synchronous gatherings.

The Results After One Quarter

After 12 weeks, the data was unambiguous. Total meeting hours had dropped by 61 per cent. The MIT Sloan and Otter.ai study had predicted that a 40 per cent reduction would yield a 71 per cent productivity increase; the company's internal metrics showed a 68 per cent improvement in project completion rates, closely tracking that benchmark. Decision speed — measured as the time from problem identification to resolution — improved by 35 per cent.

Employee satisfaction scores rose by 29 points on their internal survey. The most frequently cited reason was not fewer meetings but more uninterrupted time. Engineers reported being able to complete deep work in blocks of three to four hours for the first time. Sales leaders said they were spending more time with clients instead of sitting in internal reviews. Finance described the quarter as the first time they had finished month-end close without working evenings.

The financial impact was also significant. The company estimated that reclaimed meeting time translated to roughly 1,200 additional productive hours per month across the leadership and management layers. At their blended cost rate, that represented an annual saving exceeding £1.8 million — not from headcount reduction, but from redirecting existing capacity toward revenue-generating and strategic work.

The Playbook You Can Adapt for Your Organisation

If you want to replicate this approach, start with the audit. Categorise every recurring meeting using the four-type framework: decision, information-sharing, relationship-building, and legacy. Be ruthless about legacy meetings — if nobody can articulate why a meeting exists, it should not exist. Apply the NOSTUESO check to every surviving meeting: does it have a stated purpose, expected outcomes, and an owner? If not, redesign or cancel it.

Next, pick your meeting-free days. Two is ideal, but even one makes a measurable difference. Protect those days with the same intensity you would protect a client commitment. The moment you allow exceptions to become routine, the meeting-free day collapses. Communicate the policy clearly, enforce it visibly, and celebrate the teams that respect it consistently.

Finally, measure the impact. Track total meeting hours per week, decision speed, project completion rates, and employee satisfaction before and after the changes. Data turns a cultural experiment into a business case. When you can show that 60 per cent fewer meetings produced better results across every metric that matters, the argument for reverting to the old way becomes impossible to make.