There is a meeting happening right now in your organization that nobody needed to attend. Probably several. And the people in those meetings know it — they’re just not saying so.
Meeting overload has become one of the most widely acknowledged and least addressed problems in organizational life. The data on it is unambiguous. The organizational will to do anything about it remains elusive.
What the Numbers Actually Show
Atlassian’s survey of 5,000 knowledge workers found that 78% say they’re expected to attend too many meetings. The same research found that 65% of senior managers say meetings keep them from completing their own work, and 71% describe meetings as unproductive and inefficient.
Asana’s 2024 State of Work Innovation report found that unproductive meeting time for individual contributors jumped 118% between 2019 and 2024 — from 1.7 hours per week to 3.7 hours. The biggest burden isn’t falling on executives. It’s falling on the people doing the work.
The financial cost of this is significant. Research cited by Doodle estimates that unnecessary meetings cost US businesses $37 billion annually in wasted salaries and opportunity cost. Flowtrace’s analysis of 1.3 million real meetings found that employees spend approximately 392 hours per year in meetings — the equivalent of ten full working weeks.
Only 37% of those meetings use an agenda.
Why Meetings Proliferate Anyway
Meeting overload is rarely the result of bad intentions. It tends to emerge from a set of organizational conditions that individually make sense but collectively create a problem.
In hybrid and distributed environments, where informal check-ins are less frequent and visibility is lower, meetings become a stand-in for trust and clarity. If people aren’t sure whether work is progressing, they schedule a check-in. If someone feels out of the loop, they request an update meeting. If a decision needs to be made, the default is to gather everyone who might have an opinion.
The result is a calendar that’s full of meetings that exist to manage uncertainty rather than to make decisions or move work forward.
Atlassian’s research found that meetings are ineffective at disseminating information, encouraging collaboration, and accomplishing tasks 72% of the time. The meetings are happening. The outcomes aren’t following.
The Culture Behind the Calendar
Treating meeting overload as a scheduling problem — something to be fixed by better calendar management or a no-meeting day policy — addresses the symptom without the cause.
The underlying issue is cultural: what do meetings signal in your organization? In many workplaces, attending meetings signals engagement and contribution. Not attending signals disengagement or lack of commitment. Being invited to a meeting is a status signal. Running a meeting is a leadership signal.
When meetings carry this kind of cultural weight, reducing them requires changing what signals commitment and contribution — which is a much harder problem than blocking out Tuesday afternoons.
Some of the conditions that reliably drive meeting proliferation:
Unclear decision rights. When it’s not clear who has authority to make a decision, the default is to involve everyone who might have an opinion. This creates meetings that feel collaborative but often produce no decision — just another meeting to revisit the question.
Low asynchronous infrastructure. Organizations that lack strong norms and tools for communicating and collaborating without real-time interaction fill the gap with meetings. When there’s no shared system for updates, progress, and decisions, a meeting is the only available mechanism.
Presence as a proxy for performance. When being seen in meetings is how managers assess engagement, employees attend meetings they don’t need to attend — and managers schedule meetings they don’t need to run — because the alternative is invisibility.
What a Meeting Culture Audit Actually Involves
An audit of meeting culture isn’t about counting meetings or enforcing a cap. It’s about understanding why meetings are being called and whether they’re achieving anything.
A useful starting point is to categorize your organization’s recurring meetings into three types: meetings that make decisions, meetings that share information, and meetings that exist because they’ve always existed. The third category is where most of the waste lives — and it’s usually the hardest category to eliminate because no one wants to be the person who cancels the meeting that everyone secretly wants cancelled.
Some questions worth asking organization-wide:
What percentage of meetings result in a documented decision or clear next action? Flowtrace’s data suggests only 37% of meetings result in a decision. If your organization’s proportion is similar, that’s a signal that most of your meeting time is producing alignment rather than progress — and that alignment may be achievable through other means.
Who is being invited that doesn’t need to be there? Meetings grow over time as people get added for visibility or political reasons rather than necessity. A regular review of standing meeting attendee lists tends to find significant bloat.
What decisions are being made in meetings that could be made asynchronously? Not all decisions require real-time discussion. Identifying which ones do — and creating asynchronous pathways for those that don’t — reduces the meeting load without reducing decision quality.
What would happen if this recurring meeting didn’t exist? The most revealing question for any standing meeting. If the answer is “probably nothing,” that’s useful information.
The Productivity Cost That Doesn’t Show Up in the Calendar
The direct cost of unproductive meetings — time spent in them — is significant. The indirect cost is often larger.
Atlassian’s research found that 53% of workers say they spend more than half their time on busywork, with meeting overload as a primary driver. The time lost to meetings isn’t just the meeting itself. It’s the context-switching cost of moving in and out of focused work, the preparation time for meetings that don’t need it, and the recovery time afterward.
Eighty percent of workers in Atlassian’s survey agreed they would be more productive if they spent less time in meetings. That near-universal consensus represents a clear mandate that most organizations haven’t acted on.
The organizations that have reduced meeting load — through explicit audits, asynchronous-first norms, and accountability for meeting effectiveness — consistently report improvements in both productivity and employee experience. Not because meetings are inherently bad, but because the right meetings, run well, with the right people, produce something. Everything else is a tax on focused work.
The organizations that get this right don’t just have better calendars — they have more time for the work that actually matters, and employees who feel trusted to do it. That shift starts with better intelligence about how work is actually flowing, where time is being lost, and what meetings are genuinely producing.
Workbliss is building the platform that makes this possible. Join the waitlist to be first in line.
