Collaboration Overload: Recognizing It and Protecting Focus Time
How to spot collaboration overload on your team and set shared norms for messages, meetings and focus time, drawing on published research.
Collaboration Center · Last reviewed October 23, 2026 · 6 min read
Collaboration is supposed to make work better, and usually it does. But past a certain point, the meetings, messages, reviews and quick questions crowd out the work they were meant to support. People spend their days coordinating and do their own focused work early in the morning or late at night.
This pattern has a name: collaboration overload. In a 2016 Harvard Business Review article, Rob Cross, Reb Rebele and Adam Grant wrote that, according to data they had collected over two decades, "the time spent by managers and employees in collaborative activities has ballooned by 50% or more." A 2017 HBR article by Leslie Perlow, Constance Noonan Hadley and Eunice Eun cited research showing that executives spend "an average of nearly 23 hours a week" in meetings, "up from less than 10 hours in the 1960s."
The fix is not less collaboration across the board. It is more deliberate collaboration, with team norms that protect time for focused work. This guide focuses on what teams and leaders can change together.
Signs your team is overloaded
Overload builds gradually, so it helps to look for concrete signals:
- Calendars with few or no open blocks of an hour or more during the workday.
- Real work regularly pushed to evenings and weekends.
- An unspoken expectation that every message gets a reply within minutes.
- People copied on threads and invited to meetings "just in case."
- Decisions that cannot be made without a meeting, even small ones.
- A handful of especially helpful or knowledgeable people who are pulled into almost everything and fall behind on their own work.
If several of these sound familiar, the problem is probably systemic rather than a matter of individual time management.
Why it happens
Each individual request is usually reasonable. A quick call, one more reviewer, a channel for a new project: none looks costly on its own. The cost appears only in aggregate, and it is mostly invisible, because nobody sees the hour of focused work that did not happen.
Tools make asking almost free. Sending a message or a calendar invite costs the sender seconds, while the cost to the recipient's attention is harder to see. Status meetings often exist because work is not visible any other way. And helpful people rarely say no, so demand flows toward them.
What interruptions cost
Interruptions affect more than speed. In a lab experiment reported in the paper "The Cost of Interrupted Work: More Speed and Stress," Gloria Mark of the University of California, Irvine, with Daniela Gudith and Ulrich Klocke of Humboldt University, interrupted 48 participants, mostly university students, while they answered work-style emails. Surprisingly, people completed interrupted tasks in less time with no difference in quality. But the authors wrote that people compensate by working faster, and "this comes at a price: experiencing more stress, higher frustration, time pressure and effort."
It is a single lab study, so it should not be stretched too far. Still, it matches what many teams report: people can absorb constant interruptions and keep output up, but they pay for it in strain that does not show up in any status report.
Set team norms for communication
Overload is easiest to reduce at the team level, because a single person who stops answering instantly just looks unresponsive. Agree together on norms such as:
- Channel by urgency. Decide which channel is for urgent matters (perhaps a phone call), which is for same-day questions (chat), and which is for things that can wait (email, comments on a document or the project board).
- Response-time expectations. For example, chat replies within a few hours, email within a business day. Write it down so nobody has to guess.
- Asynchronous status. Replace spoken status rounds with written updates on a shared board or document, and use meetings for decisions and problems.
- Fewer, clearer requests. Ask people to include the decision needed, the deadline and the context in one message instead of sending "got a minute?"
- Copy with intent. Copy someone only if they need to act or decide; otherwise share a summary later.
Make meetings earn their place
Before scheduling a meeting, check whether it has a clear purpose, an agenda and a decision or outcome. Then:
- Invite only the people needed for the decision, and send notes to everyone else.
- Default to shorter meetings and leave a few minutes between them.
- Mark attendance as optional for people who only need the outcome.
- Review recurring meetings each quarter and cancel any that no longer have a purpose.
Some organizations go further with meeting-free days. In a 2022 MIT Sloan Management Review article, Benjamin Laker and colleagues reported on a survey of "76 companies, with more than 1,000 employees each and operations in more than 50 countries, that had introduced from one to five no-meeting days per week." They wrote that "the best results were achieved at companies that had three meeting-free days per week." Keep in mind that these were companies that chose to try the practice, not a controlled experiment, so treat the findings as encouraging rather than conclusive. A smaller step, such as one shared meeting-free afternoon, is an easy experiment for most teams.
Protect focus time together
Focus time works best when the whole team respects it. Consider:
- Shared focus blocks that appear on everyone's calendar, during which non-urgent messages wait.
- A visible status that signals heads-down work, with an agreed way to reach someone in a genuine emergency.
- Rotating "on call" duty for incoming questions, so not everyone is interrupted at once.
For example, imagine a five-person marketing team that declares Tuesday and Thursday mornings meeting-free and agrees that chat during those hours is answered by noon. After a month, the team reviews whether projects moved faster and whether anything urgent was missed, then adjusts.
What leaders can do
Leaders set the pace more than any policy. Model the norms: decline meetings you are not needed in, avoid sending messages late at night that imply an expectation to reply, and praise finished work rather than visible busyness.
Look out especially for the people everyone relies on. If the same few names appear on every project and every meeting invite, redistribute the load, document their knowledge so others can answer questions, and make it acceptable for them to say "not this week."
If overload has turned into persistent stress, sleep problems or a sense of being unable to cope, team norms are not a substitute for professional care. Talk with a doctor or a licensed mental health professional, and in a crisis in the US, call or text 988.
Key takeaways
- Collaborative demands have grown substantially, according to research reported in Harvard Business Review, and overload builds quietly.
- Watch for full calendars, after-hours work, instant-reply expectations and a few overloaded helpers.
- A lab study by Mark, Gudith and Klocke found interrupted work got done faster but with more stress and frustration.
- Agree on channels, response times and asynchronous status as a team, not person by person.
- Make meetings earn their place, try protected focus time, and have leaders model the norms.
Sources
- Rob Cross, Reb Rebele and Adam Grant, Collaborative Overload, Harvard Business Review (January–February 2016)
- Leslie A. Perlow, Constance Noonan Hadley and Eunice Eun, Stop the Meeting Madness, Harvard Business Review (July–August 2017)
- Gloria Mark, Daniela Gudith and Ulrich Klocke, The Cost of Interrupted Work: More Speed and Stress (Proceedings of ACM CHI 2008)
- Benjamin Laker, Vijay Pereira, Pawan Budhwar and Ashish Malik, The Surprising Impact of Meeting-Free Days, MIT Sloan Management Review (January 18, 2022)
Spotted something out of date? Let us know.