Why Your Team’s Work Is Getting Lost in Email — And What a Good Manager Can Do About It
29 May 2026
Why Your Team’s Work Is Getting Lost in Email — And What a Good Manager Can Do About It
The Inbox That Ate the Working Day
Email was supposed to make work easier. In principle, it’s a fast, flexible communication channel — easier than picking up the phone, quicker than writing a memo, more traceable than a corridor conversation. And for many tasks, it does exactly what it promises.
The problem is that over the past two decades, email has quietly expanded to cover everything: task assignment, decision-making, document storage, project updates, meeting follow-up, approval processes, and a hundred other functions it was never designed to handle. The result is an inbox that functions less like a communication tool and more like a very disorganised filing cabinet — one that everyone in the organisation is constantly shuffling through, usually under time pressure, and frequently missing things.
Research from McKinsey Global Institute puts the average knowledge worker’s email time at around 28% of the working week — roughly eleven hours. Other analyses push that figure higher. Either way, it’s a substantial chunk of the working week consumed by a channel that an increasing body of evidence suggests is actively working against the people using it.
For managers, this isn’t just a personal productivity issue. When work gets buried in inboxes, the whole team suffers — missed tasks, unclear accountability, delayed decisions, and a background anxiety that nobody quite knows what’s happening or who’s responsible for what. Understanding why this happens, and what can actually be done about it, matters.
Why Work Gets Buried: The Real Causes
Email overload tends to produce a few predictable failure patterns, each one making the others worse.
Volume that defeats attention
The sheer quantity of email most professionals now receive makes genuine prioritisation almost impossible. A 2024 survey of knowledge workers found that the average professional receives between 50 and 100 emails per day, with many receiving considerably more. Crucially, research suggests that only around 10% or fewer of those messages are genuinely business-critical. The rest — newsletters, CC’d threads, status updates, internal announcements — arrive alongside the urgent items with no reliable way for the reader to tell them apart at a glance.
The practical effect is that important emails get buried, low-priority messages absorb attention they don’t deserve, and everything starts to feel equally urgent even when it isn’t. That false urgency is its own problem: it trains people to respond quickly rather than thoughtfully, and it rewards visible responsiveness over genuine progress. A team culture built around fast reply times is, almost by definition, a culture that struggles to do sustained, focused work.
What interruptions actually cost
Research from the University of California, Irvine found that it takes an average of around 23 minutes to fully recover cognitive focus after an interruption. Email notifications — or the habit of checking the inbox mid-task — generate interruptions continuously throughout the day. A randomised controlled trial at the University of British Columbia found that participants who checked email just three times per day reported significantly lower daily stress than those who checked continuously, with no measurable reduction in overall productivity.
For managers, that finding has direct implications. The norm of constant inbox monitoring isn’t producing better communication — it’s producing more interruptions, more stress, and less sustained thinking. Teams that have shifted to batched email checking report doing the same quality of work with considerably less cognitive cost. The expectation of instant replies is, in most organisations, a cultural norm rather than a genuine operational requirement — and it’s one that managers have the authority to change.
Email as an unintentional task manager
Here’s a useful exercise: open your inbox and count the emails that contain actual tasks. Then ask how many of those tasks are clearly defined, tracked anywhere outside the email thread, or confirmed as completed.
For most teams, the answer is uncomfortable. Email wasn’t designed to manage work, but it functions as a de facto to-do list for millions of people. Tasks sit buried in long threads, key details are embedded mid-paragraph, and follow-ups go untracked. The more email volume increases, the less thoroughly messages get read — which means more ambiguity, more missed commitments, and a steady erosion of accountability. Not because people are careless. Because the system they’re using was never built for the job it’s been asked to do.
The Management Dimension
None of this is purely an individual problem. The way a team uses email reflects, to a significant degree, the norms and expectations set by the people leading it. If the manager sends emails at 10pm and expects a response by morning, the team learns that constant availability is the standard. If important decisions get buried in 30-reply chains, the team learns that finding information is hard work — and gradually stops trying.
Long threads hide what matters
Anyone who’s opened an email thread running to 27 replies and tried to piece together what was agreed will know the feeling. Somewhere in there is an important decision, a key figure, or an action someone needs to take — buried under a sequence of “Sounds good!” and “Just looping in Sarah” messages. Reading the whole thing from the top to extract one piece of information is exhausting, time-consuming, and a reliable way to miss something critical.
When information is hard to find, it effectively doesn’t exist. Teams can’t act on decisions they can’t locate, and managers can’t hold people accountable for commitments that were never clearly stated or recorded. This is where the absence of a clear system creates the most damage: in many teams, email is the default precisely because there is no system, which means responsibility and accountability become genuinely ambiguous.
Clarity as a leadership responsibility
A significant portion of email overload in teams comes from unclear communication norms. People CC others “just in case.” Threads multiply because nobody owns the decision. Messages are vague because the sender hasn’t thought through exactly what they’re asking for. Managers who set clear expectations about how communication should work — what belongs in email, what belongs in a project tool, what warrants a direct conversation — can reduce inbox complexity considerably.
This connects directly to broader questions of team accountability and clarity of responsibility. When everyone knows what they own and how they’re expected to communicate about it, the inbox stops being the default home for everything that doesn’t have a better one.
Practical Steps That Actually Help
Inbox zero is a reasonable personal aspiration but a weak management strategy. It addresses symptoms rather than causes. The more productive question is: what would need to change about how this team works for email to stop being a problem?
Separate communication from task management
The single most impactful change most teams can make is to stop using email as a task management system. Dedicated project tools — whether something lightweight like Trello or a more comprehensive platform — give tasks a proper home where they can be tracked, assigned, updated, and closed out. Email threads then become context and confirmation, not the primary record of what’s been agreed.
This requires management discipline to implement. If the manager continues assigning work by email while nominally using a project tool, the team will follow suit. The norm has to be modelled, not just announced.
Adding a layer of visibility
One of the subtler effects of email overload is that it creates a genuine visibility gap — managers and team members lose track of where time and effort are actually going. Tasks assigned by email may or may not be progressing. Follow-ups may or may not have been sent. The picture of what’s happening in the team becomes patchy, and the inbox noise makes the signal harder to find.
Automatic time tracking tools can help here. Rather than relying on people to manually log their time — which adds its own overhead and is notoriously inaccurate — tools like Memtime run quietly in the background and record activity across programmes including email, building an honest picture of where workday time is actually going. For teams where privacy matters — and it should — Memtime stores all activity data locally on the individual’s own device. Nothing is uploaded to the cloud, and the information is visible only to the person whose work is being tracked. That’s an important distinction from employee monitoring software: this is about giving individuals genuine clarity over their own working day, not feeding data back to management.
When people can see accurately where their time goes, conversations about what should change become considerably more productive. Good time management at team level starts with that kind of shared, honest understanding.
Set communication expectations explicitly
Teams benefit from clear, shared agreements about how communication works. What’s the expected response time for a non-urgent email? Is there an expectation of availability outside working hours? What should a subject line communicate to signal urgency? When is a direct conversation the right call rather than an email exchange? These aren’t bureaucratic rules — they’re the kind of clarity that lets people work with focus and confidence, without the background anxiety that they might be missing something important.
Reducing the CC reflex is part of the same effort. Much of the volume problem in team inboxes comes from copying people in “just in case” — which transfers the cost of making a relevance judgement from the sender to every recipient. Managers who actively discourage unnecessary CC’ing, and model that behaviour themselves, can make a meaningful dent in team email volume without losing any important information.
What This Means for How You Lead
The email problem is, at root, a communication culture problem. And communication culture is shaped by leadership. Teams where the manager sends clear, purposeful messages — specific requests, threads that reach a conclusion, subject lines that communicate content — gradually develop the same habits. Teams where the manager treats email as a running commentary, expects continuous availability, and buries decisions in long chains tend to replicate that pattern too.
None of this requires a dramatic overhaul. Small, consistent changes to how you use email as a manager have a disproportionate effect on how your team uses it. Email overload can reduce worker productivity by up to 40%, according to cloudHQ workplace research. That’s not an individual failure. It’s a system problem, and it responds to system-level changes — most of which sit firmly within a manager’s control.
Further Reading
- Threadly: Email Management Statistics 2025 — A well-sourced summary of the research on email overload, interruption cost, and what high-performing teams do differently. Useful background before running a communication audit with your team. Read the article
- cloudHQ: Workplace Email Statistics 2025 — Detailed data on email volume, productivity impact, and burnout rates across different workforce groups. Good for building the case for changed communication norms. Read the report
- Cerkl: Preventing Employee Email Overload — Practical guidance on tackling email overload at team level, with a focus on the manager’s role in setting expectations and reducing volume. Read the article
Disclaimer
The content on this site is provided for general information and educational purposes only. It reflects the author’s views and experience and is not intended as professional HR, productivity, or management consultancy advice. Management situations vary considerably, and readers should use their own judgement before making changes to team communication practices based on anything published here. The Happy Manager and Apex Leadership Ltd accept no liability for actions taken in reliance on the content of this article.
References
- McKinsey Global Institute. The Social Economy: Unlocking Value and Productivity Through Social Technologies. Referenced in: Clean Email (2026). https://clean.email/blog/insights/email-productivity-statistics-report
- Mailbird (2024). Email Overload Survey: Insights on How It Impacts Business and Productivity. https://www.getmailbird.com/email-overload-survey/
- Kushlev, K. & Dunn, E. (2015). Checking Email Less Frequently Reduces Stress. University of British Columbia. Referenced in: Threadly (2026). https://threadly.live/blog/email-management-statistics-2025/
- cloudHQ (2025). Workplace Email Statistics: Usage, Productivity, Trends. https://blog.cloudhq.net/workplace-email-statistics/
- Goodwin, M. (2025). Reducing Email Overload to Enhance Communication Strategies in the Middle-Level Corporate Environment. Referenced in: Cerkl (2026). https://cerkl.com/blog/employee-email-overload
Building well-being through better teams

Containing 240 pages and 50 tools, these are the 8 key guides we recommend to help you do more than define teamwork, build it!
Why is Teamwork Important
Build a Better Team
The Problems with Teams
Team Health Check
Team Building Exercises
Leading with Style and Focus
What’s the Problem?
Making Better Decisions