Here is a week in the life of a leader I worked with recently. Monday: four meetings before lunch, two after. Tuesday: three hours of “strategy time” on the calendar — interrupted by eleven Slack messages, two escalations, and a request that could not wait but somehow also could not have come last Friday. Wednesday: an all-hands meeting that ran forty minutes over. Thursday: back-to-back from 9am to 5pm. Friday: the strategic plan she had been meaning to write sat open on her screen for twenty minutes before another meeting pulled her away. She closed the laptop at 6pm, exhausted and vaguely ashamed.
She told me she needed to get better at managing her time. I told her that her time management was fine. The problem was not her schedule. The problem was how her entire team worked together.
We had spent six posts in this series building the individual architecture: attention budgets, space, buffers, distraction management, the relationship between productivity and self-worth. All of that matters. But none of it survives contact with a team that has no shared norms around how people coordinate, communicate, and claim each other’s time. You can build the most elegant personal system in the world, and it will collapse the moment someone books a “quick sync” in the only deep-work block you protected all week.
The time problem, at a certain point, stops being individual. It becomes collective. And collective problems require collective solutions.
What Collaboration Overload Actually Is
Collaboration overload is when the coordination demands of working together — meetings, messages, requests, check-ins, approvals — consume so much of a team’s capacity that deep work and sound decision-making degrade. The organisation becomes reactive and slow while feeling busy. People are working harder and producing less, and everyone assumes the problem is personal rather than structural.
This is not a fringe phenomenon. Research consistently shows that the time employees spend on collaborative activities — email, meetings, messaging, real-time requests — has increased dramatically over the past two decades. In many organisations, collaborative demands now consume 85% or more of the working week. That leaves a sliver for the thinking, creating, and deciding that collaboration is supposed to serve.
Collaboration is not the enemy. It is essential. The problem is that most organisations have no mechanism for distinguishing between collaboration that creates value and collaboration that merely creates activity. Without that distinction, collaboration expands until it fills every available hour, and the work it was meant to support gets squeezed to the margins.
Collaboration is oxygen. Over-collaboration is carbon monoxide — odourless, invisible, and it will take you down before you realise what is happening.
Three Drivers of Collaboration Overload
Collaboration overload does not happen because people are careless. It happens because three systemic forces push in the same direction, and none of them are visible from inside the system.
Driver A: Always-On Communication
Twenty-four-hour connectivity has collapsed the boundary between “available” and “working.” When everyone carries a device that can reach anyone at any time, the implicit expectation shifts from “I will respond during working hours” to “I will respond as soon as I see this.” That shift is subtle, but its consequences are enormous. It means that no block of time is truly protected. It means that every notification is a potential interruption. It means that the cost of reaching someone has dropped to nearly zero — which means the volume of reaching has increased accordingly.
The problem is not that people have phones. The problem is that the norms around when and how to use them have never been explicitly agreed. In the absence of norms, urgency fills the vacuum. Everything becomes same-day. Everything becomes “quick question.” Everything becomes now.
Driver B: Reputation Economics
In most workplaces, responsiveness is a proxy for competence. The person who replies within minutes, who always says yes to a meeting, who drops what they are doing to help — that person is perceived as collaborative, reliable, and committed. The person who batches their email, declines meetings without a clear agenda, and protects their deep-work time is perceived as difficult, disengaged, or “not a team player.”
This creates a perverse incentive: to maintain your reputation, you must overload yourself with collaboration. You must signal availability at the expense of your actual capacity to do the work that collaboration is supposed to enable. People do not overload themselves because they lack boundaries. They overload themselves because the social economy of the workplace rewards it. Saying no has a reputational cost. Saying yes — even when it degrades your work — does not.
Driver C: Lopsided Load
Not everyone in an organisation carries the same collaboration burden. Research shows that a small percentage of people — typically the most competent and most connected — produce a disproportionately large share of value-added collaboration. They are the ones with the answers, the relationships, and the institutional knowledge. As a result, requests concentrate on them. The more capable and responsive they are, the more requests they attract, and the less time they have for the deep work that made them valuable in the first place.
This is a structural problem, not a personal one. The organisation has created a bottleneck at its most valuable nodes — and then wonders why those nodes are burning out or underperforming on strategic work. The people who carry the heaviest collaboration load are often the last to complain, because complaining itself feels like a failure to cope.
Step 1. A team member is consistently responsive, knowledgeable, and willing to help. They answer questions quickly, attend every meeting they are invited to, and rarely push back on requests. They are widely regarded as indispensable.
Step 2. Because they are competent and available, requests begin to concentrate on them. Colleagues default to asking them rather than searching for the answer themselves or approaching someone less busy. The path of least resistance runs through this person.
Step 3. Their deep-work capacity collapses. They cannot sustain the strategic or creative work that made them valuable because every hour is interrupted by coordination requests. Their calendar is full of other people’s priorities.
Step 4. They begin taking work home — not to be a hero, but because the office day no longer contains enough uninterrupted time to do their actual job. Evenings and weekends become the overflow buffer.
Step 5. Burnout risk increases. They are tired, resentful, and quietly disengaged from the strategic work that used to energise them. Their output is still high by volume, but the quality of their thinking has declined, and they know it.
Step 6. The organisation loses its leverage. The person either burns out, disengages, or leaves — and the institutional knowledge and collaborative capacity they carried walks out the door. The system that created the bottleneck never gets examined.
Step 1. A person sits on three project teams simultaneously. Each team has its own goals, timelines, and meeting cadence. On paper, this looks like efficient resource allocation. In practice, it means the person has three competing sets of priorities.
Step 2. The priorities conflict. Team A needs a deliverable by Thursday. Team B has scheduled a working session on Wednesday that will consume half the day. Team C has an urgent escalation that arrives Tuesday afternoon. There is not enough time or attention for all three.
Step 3. Cohesion suffers across all teams. The person cannot give full presence to any of them. They attend meetings distracted, contribute less than they could, and quietly triage which team gets their best thinking — a decision no one asked them to make and no one knows they are making.
Step 4. More coordination meetings appear. Because alignment keeps slipping, each team schedules additional syncs, check-ins, and status updates. The solution to fragmented attention is — ironically — more claims on that same attention.
Step 5. More time is lost. The additional meetings consume the remaining deep-work windows. The person is now spending most of their week talking about work rather than doing it.
Step 6. Execution slows across all three teams. Everyone is busy. Nothing is moving at the pace it should. The root cause — overlapping team membership without clear priority arbitration — remains invisible because it looks like a resourcing issue, not a coordination design issue.
What Not to Do
- Do not tell people to “manage their time better.” If the system generates more collaboration demand than any individual can absorb, individual time management is not the solution. It is like telling someone to swim faster in a rising flood. The water level is the problem, not the swimmer’s technique.
- Do not add another tool without changing the norms. A new project management platform, a new messaging app, a new scheduling tool — these feel like progress. But a tool layered on top of broken norms simply gives people a more sophisticated way to overload each other. The norms — when to meet, how to communicate, what counts as urgent — are the operating system. The tool is just an app running on it.
- Do not punish collaboration. The goal is not to make people stop working together. Collaboration is how complex work gets done. The goal is to redesign collaboration so that it serves the work rather than consuming it. If people feel that protecting their time means being seen as uncooperative, the system is still broken — you have just added guilt to the overload.
The instinct to solve a collective problem with individual advice is strong and almost always wrong. If everyone on the team is drowning, the answer is not better swimming lessons. The answer is examining why the water is so high.
Three Levers That Actually Work
If collaboration overload is structural, the response must be structural. Three levers — applied together — can shift a team from reactive coordination to deliberate collaboration without killing the connectedness that makes the team effective.
Lever 1: Map Collaboration Supply and Demand
Most teams have no visibility into who is carrying the collaboration load and where it is concentrated. The first step is to make it visible. This does not require sophisticated analytics. It requires honest observation.
Ask: Who appears in every meeting? Who is copied on every email thread? Who gets the most requests? Whose calendar has the least protected time? The answers will reveal a pattern — typically, a small number of people are absorbing a disproportionate share of the coordination demand, while others have more capacity than the team realises.
Once the pattern is visible, redistribute. Route requests to people with capacity rather than defaulting to the person with the most knowledge. Create documentation so that answers do not have to live inside one person’s head. Rotate meeting attendance so that the same people are not always in the room. The goal is to spread the collaboration load across the team rather than letting it concentrate on the nodes that are already overloaded.
Lever 2: Create Protected Focus Capacity
If collaboration is allowed to fill every hour, it will. Protected focus capacity means building explicit, team-wide structures that preserve time for deep work. This is not an individual choice — it is a team agreement.
Two mechanisms work reliably. First, office hours: designate specific windows when people are available for questions, coordination, and ad-hoc requests. Outside those windows, the default is “do not interrupt unless it is genuinely urgent.” This makes availability structured rather than ambient. People know when they can access each other, and they know when they cannot — and both boundaries are explicit rather than implied.
Second, async-first norms: shift the default communication mode from synchronous (meetings, real-time chat, phone calls) to asynchronous (email, shared documents, recorded updates). Synchronous communication is valuable when you need real-time dialogue. It is wasteful when you are simply transferring information. Most “quick syncs” are information transfers disguised as conversations. Moving them async recovers hours.
Lever 3: Stop Inflating Collaboration Load
Much of what passes for necessary collaboration is habit. Meetings that exist because they have always existed. Email threads that copy ten people because no one wants to be the person who left someone out. Status updates delivered in real time because no one has built a dashboard. Approval chains that require three meetings when a single email would suffice.
The question is not “Is this collaboration valuable?” — because the answer to that question is almost always yes, at least in theory. The question is: “Is this the minimum necessary collaboration to achieve the outcome?” If a meeting can be replaced by a document, replace it. If ten people are invited but only four need to be there, reduce the list. If a weekly sync exists because it was set up six months ago, ask whether it is still serving a purpose or merely occupying a calendar slot.
Collective time is the organisational operating system. If it is buggy, everyone’s performance degrades — no matter how good their individual hardware is.
Collective Time Charter (Team One-Pager)
This is a single-page agreement your team creates together. It makes implicit norms explicit. Print it out. Put it somewhere visible. Review it monthly. The power is not in the document — it is in the conversation that produces it and the shared commitment that sustains it.
- Response-time expectations. Define what “timely” means for your team. A useful default: same day, not instant. Email gets a response within the working day. Chat messages get a response within two hours during office hours. Nothing requires an immediate reply unless it meets the escalation criteria below. Write this down. Make it explicit. The absence of a stated norm is not the absence of expectations — it is the presence of unspoken ones, which are always more stressful.
- Two collaboration windows per day. Designate two periods (e.g., 10–11:30am and 2–3:30pm) when the team is available for meetings, coordination, and real-time requests. Outside these windows, the default is focused work. This does not mean you cannot contact someone outside the windows — it means you should not expect an immediate response. The windows create rhythm. Rhythm creates predictability. Predictability creates the conditions for deep work.
- Async-first default for non-urgent communication. Unless the matter requires real-time dialogue, the default is asynchronous. Updates go in shared documents. Questions go in email or a designated channel. Decisions that do not require group discussion get made by the responsible person and communicated after the fact. This single norm — async unless otherwise justified — can recover more collective hours than any other intervention.
- Escalation rule. Define what counts as genuinely urgent. Be specific. “Urgent” is not “I need this soon” — it is “A client-facing deadline will be missed in the next two hours” or “A system is down and people are affected right now.” When something meets the escalation criteria, phone call or direct message with the word “urgent” in the first line. Everything else follows the standard response norms. The clearer the escalation rule, the safer people feel ignoring non-urgent interruptions.
- Weekly review question. At the end of each week, ask one question as a team: “Where is collaboration lopsided?” Who is carrying too much? Which meetings served no purpose this week? Where did coordination consume time that should have gone to execution? This is not a performance review. It is a systems check. The question keeps the norms alive and makes adjustment normal rather than exceptional.
The charter works because it turns individual frustration into shared language. When everyone agrees on the norms, protecting your time stops being a political act and becomes a team commitment. The person who declines a meeting is not being difficult — they are following the charter.
Key Takeaways
- The modern time problem is collective, not just personal. You can have perfect individual habits and still drown if your team has no shared norms around communication, meetings, and requests. Individual time management solves individual problems. Collective time management solves the ones that actually determine whether a team executes well.
- Collaboration overload is driven by three systemic forces. Always-on communication removes boundaries. Reputation economics rewards over-availability. Lopsided load concentrates demand on the people least able to absorb more. All three must be addressed structurally, not individually.
- Redesign collaboration — do not eliminate it. The goal is minimum necessary collaboration: enough to maintain alignment, not so much that it consumes the work it is meant to support. Map the load, protect focus capacity, and stop inflating collaboration that serves habit rather than outcomes.
Once a team has shared norms — once collective time is operating on a deliberate system rather than an accidental one — the question shifts from “How do we stop meeting?” to “How do we make the meetings we keep genuinely effective?” Because meetings, done well, are not the enemy of execution. They are the engine of it. That is where we go next.
If your team is drowning in coordination and you want help redesigning how you work together — without losing the collaboration that matters — that is the work I do.
Get in TouchFrequently Asked Questions
It is when meetings, messages, and requests consume so much capacity that deep work and decision quality degrade. The organisation becomes reactive and slow while feeling busy.
Shift updates async, reduce attendees, shorten meetings, and protect focus blocks. Alignment comes from clarity and follow-through, not constant interruption.
Look for the same names in every thread and meeting. High performers and bottleneck roles often become the default router for requests. That concentration is a hidden risk to the team and to the individual carrying it.
Publish response norms and introduce office hours for coordination. When access becomes structured rather than ambient, focus reappears — and most people are relieved rather than frustrated by the boundaries.