I have a private metric I keep for every team I coach: how much of the week is work about work. Not work itself. Work about work.
The number has barely moved in six years. Asana Anatomy of Work 2026 puts it at 57 percent. Two months before that, Reclaim at SXSW cited 52.9 percent for people in meetings every day. The averages differ, but the shape is identical. Most of what we do during the workday is not delivering. It is arranging the conditions for delivering.
What Coordination Overhead Actually Is
Asana breaks coordination into three buckets that I keep seeing in my own teams.
- Meetings. Standups, syncs, reviews, retro, one-on-ones. Every hour spent meeting is an hour not spent building.
- Message triage. Slack, email, DM, notification review. Not urgent work, but constant low-grade attention drain.
- Status plumbing. Updating tickets, drafting status reports, chasing approvals. It gets things moving, and it never produces anything the customer can see.
The average professional reports about 11.7 hours of deep focus per week. On a 40-hour work week that is 29 percent. On a week that slips to heavy meetings, it can drop below 20 percent.
That is not a burnout story. It is a focus story. And the difference between 29 percent and 15 percent is whether you finish the week with anything actually done.
Why This Is a Team Problem, Not a Personal One
I have resisted labeling this a team problem for a long time. For years I treated focus as a personal discipline. Block your calendar. Do not check Slack. That works until you hit the wall: your teammates still expect you to answer instantly.
Coordination overhead is systemic because it is negotiated collectively. Every team has a shared assumption about how fast things should move. If nobody names that assumption, everyone inherits it silently. Fix it once at the team level and every member gets more focus time. The individual-level tricks only work on top of that.
Mechanism One: Anchor Office Hours
Not everyone works the same hours. But everyone works some overlapping hours. Publish them.
In a distributed team of five people across three time zones, a two to three hour window is realistic. Two hours for overlap plus one hour as a soft edge. Post this window in the team channel. Anyone inside that window can expect a synchronous answer. Anyone outside it should default to a written update.
The key is that anchor hours are shared. Not just your office hours, but the team s office hours. When you publish the window, you are making a promise to your teammates about when you are available, and they are making the same promise back to you.
Mechanism Two: Make Async the Default
Async is not a tool. It is a default. The tools matter less than the assumption.
Convert the daily standup into three written lines by end of the previous day. Prefer pull requests and threaded comments over ad-hoc chat. Turn the synchronous status call into an optional office hour. The goal is not to eliminate meetings. The goal is to make the synchronous channel expensive in attention, so people use it deliberately.
If the async default feels slow at first, that is the sound of your team renegotiating its expectations. It settles in about two weeks for most teams.
Mechanism Three: Fence Off a Meeting Window
If you do not control when meetings happen, meetings will happen all day, every day. Fix the schedule.
Pick one day as the coordination day. I have seen Wednesday work well because it is central, not the start or end of the week. Put every recurring meeting there. If a new meeting needs to be added, it defaults to that day unless it genuinely cannot fit.
One coordination day per week, well-designed, beats five distributed meeting days on nearly every metric. You get a clear four-day stretch of deep work, and you get a predictable place for the messy conversations.
Mechanism Four: Formalize an Interruption Protocol
Interruptions are the last piece most teams ignore. They arrive unannounced, and they are often the most attention-expensive thing of the day.
Two rules do most of the work. First, agree on what counts as urgent. Not urgent things are the ones that feel urgent. Publish a short list. Second, use a distinct channel for genuine emergencies. If the emergency channel stays quiet for three days in a row, your team does not have an emergency. It has urgency anxiety.
The upside of a formal interruption protocol is that it gives people cover to decline. Declining an interruption without a policy is rude. Declining an interruption because the policy says that channel is only for incidents is not.
Measuring Coordination Load
You cannot improve what you cannot see. The three signals I ask teams to track for two weeks are:
- Scheduled meeting hours per day. Not attendance, hours on the calendar. If this is above 3 hours, cut the meeting window first.
- Median time to first response. If your median is under 5 minutes on work hours, you are too fast. That is a tax your teammates are unknowingly charging you.
- Context switches per workday. The rough count of distinct tasks you touched. Above 12 is a red flag.
Do not obsess over these numbers. Baseline them, then move one mechanism at a time. If your focus time did not rise after two weeks, the fix is usually to tighten the async default, not to add more structure.
A Personal Focus Time Checklist
At the individual level, here is the check I run once a month.
- Are there any recurring meetings you attend without contributing to in the last 90 days? Cancel them, or hand them to someone else.
- Is there one meeting that could become an optional office hour? Convert it.
- Is your team s interruption protocol clear enough to decline a ping without guilt?
- Do you have a protected four-hour block on at least three of your five workdays? If not, your calendar is the problem, not your discipline.
- Have you reviewed your calendar in the last 60 days? If not, book one.
That list sounds boring. It is not. Every box you check puts an hour back into your week. And hours come back in compound interest.
The Real Fix
The reason coordination overhead keeps winning is that it is invisible. You can see a shipped feature. You cannot see the meeting you skipped. You cannot see the focus hour you protected.
The four mechanisms above are boring on purpose. Anchor hours, async default, meeting window, interruption protocol. None of them will trend on Twitter. All of them will compound.
Pick one. Move it this week.