Asana’s Anatomy of Work Index: Where Teams Lose 60% of Their Day
Kinetiq Team
When 60% of your team’s day disappears before anyone touches their actual work, you do not have a people problem. You have an infrastructure problem. The Asana Anatomy of Work Index quantifies what most teams already feel: the majority of working hours are consumed by coordination, searching for information, duplicating effort, and managing the logistics of collaboration. Only a fraction of the day remains for the skilled work people were hired to do.
This is not a time management failure. It is a systems failure. And it points directly to the gap between having talented people and giving them the operational infrastructure to actually execute.
What the Research Shows
The 60% Coordination Tax
According to the Asana Anatomy of Work Index, workers spend 58 to 60 percent of their time on what the report calls “work about work.” This includes coordinating with teammates, searching for information, chasing status updates, switching between tools, attending alignment meetings, and duplicating tasks that someone else has already completed. Only 33 percent of time goes to skilled work, and a mere 7 percent is dedicated to strategic thinking.
Workers spend 58-60% of their time on “work about work,” leaving only 33% for skilled work and 7% for strategy.
The Duplication Problem
Knowledge workers waste an average of 58 minutes per day on duplicated work. That is nearly five hours per week per person spent re-creating deliverables, re-answering questions, or re-solving problems that have already been addressed elsewhere in the organization. Multiply that across a 20-person team, and you are looking at 100 hours of wasted effort every single week. Not because people are careless, but because there is no system to surface what has already been done.
The Team Size Multiplier
The coordination tax rises as team size increases. This is the part that makes the problem structural rather than individual. A five-person team can often coordinate informally through direct conversation. A fifteen-person team cannot. As headcount grows, the number of communication pathways increases exponentially, and without explicit coordination systems, every additional team member adds friction rather than capacity. The Asana data confirms what network theory predicts: without protocol, scale becomes drag.
The Strategic Starvation Effect
With only 7 percent of time going to strategy, most teams are operating in permanent reactive mode. They are so consumed by the logistics of getting things done that they never have bandwidth to decide whether they are doing the right things. This creates a compounding problem: poor strategic allocation leads to more rework, which consumes more coordination time, which leaves even less room for strategic thinking.
Why This Matters for Teams
The Asana data reframes productivity as a systems problem, not a personal discipline problem. Most organizations respond to low output by adding more people, running time management workshops, or implementing yet another project management tool. None of these interventions address the root cause: the absence of execution infrastructure.
Consider what the 60% figure actually means in practice. A knowledge worker with an eight-hour day spends approximately five hours coordinating, searching, and duplicating. They have roughly two hours and forty minutes for their actual skilled work and about thirty minutes for strategic thinking. This is the daily reality for most professionals, and it is not because they lack focus or motivation. It is because their organizations have not built the systems to eliminate unnecessary coordination overhead.
The Microsoft Work Trend Index surfaces the same tension from a different angle: 64 percent of workers report struggling with having the time and energy to do their jobs. That struggle is not about individual capacity. It is about organizational friction consuming the hours before skilled work even begins.
Similarly, SHRM’s data on meeting overload shows how collaboration debt compounds the coordination tax. Meetings become the default coordination mechanism when better systems do not exist, and each unnecessary meeting consumes time that could go to actual execution.
The Gap the Data Reveals
The Asana Anatomy of Work Index is excellent at quantifying the problem. It tells you precisely how much time is being lost and where the losses concentrate. What it does not provide is a framework for eliminating the coordination waste at its source. The report identifies the symptoms but leaves the structural diagnosis to others.
Here is what sits beneath the 60% figure. Each category of “work about work” maps to a missing system.
- Searching for information maps to missing documentation systems. When institutional knowledge lives in individual inboxes, Slack threads, and personal notes, every question requires a synchronous interruption. A searchable, maintained knowledge base eliminates the search tax.
- Coordinating with teammates maps to missing handoff protocols. When work transitions between people without explicit standards for what “done” means, both parties spend time clarifying, re-checking, and re-aligning. Clear handoff protocols cut this coordination overhead in half.
- Duplicating work maps to missing visibility systems. Duplication happens when people cannot see what others are working on. Shared dashboards, progress transparency, and progress tracking without status theater make current work visible without requiring synchronous check-ins.
- Chasing status updates maps to missing async norms. When the only way to know where a project stands is to ask someone directly, status-seeking becomes a full-time activity. Structured async updates replace the chase with a pull system.
The 60% is not a fixed cost of doing business. It is the price teams pay for missing infrastructure. And it is almost entirely recoverable.
What This Looks Like in Practice
The Asana data makes the strongest possible case for what KINETIQ calls a team operating system: the collection of execution systems, coordination protocols, and decision frameworks that allow skilled work to happen without constant overhead.
Consider four practical interventions that map directly to the Asana findings.
Priority Frameworks That Prevent Duplication
When teams lack shared priority language, multiple people often start working on the same problem without realizing it. A clear priority framework does more than sort tasks. It creates shared visibility into what matters most this week, which prevents overlapping effort and ensures that the 33 percent of time available for skilled work is aimed at the highest-value targets.
Handoff Standards That Reduce Coordination Cycles
Every unclear handoff generates at least two follow-up conversations: one to clarify what was delivered and another to confirm what happens next. Multiply this by dozens of handoffs per week, and you can account for a significant portion of the coordination tax. Standardized handoff protocols specify what completeness looks like, what context needs to transfer, and who owns the next action. This eliminates the back-and-forth that the Asana data captures as “work about work.”
Documentation Systems That Eliminate Search Time
The 58 minutes per day lost to duplicated work is largely a documentation failure. When decisions, processes, and institutional knowledge are documented in an accessible, searchable system, the duplication tax drops dramatically. This is not about creating more documents. It is about creating the right documents in the right places with the right maintenance rhythms.
Async Norms That Replace Synchronous Coordination
Much of the coordination overhead comes from the default assumption that alignment requires real-time conversation. Effective async norms, structured updates, clear written communication standards, and explicit response-time expectations, replace synchronous coordination with asynchronous information flow. The result is fewer meetings, less waiting, and more time for the skilled work that drives actual output.
The Josh Bersin HR Technology Report describes the market shift toward “performance infrastructure,” which is precisely the category of solution the Asana data demands. The organizations that will recover that 60% are not the ones buying better project management software. They are the ones building the operational systems that make coordination overhead structurally unnecessary.
Related Reading
Written by
Kinetiq Team
Contributing writer at Kinetiq, covering topics in cybersecurity, compliance, and professional development.
