The average knowledge worker spends 43% of their time on actual work. The rest goes to coordination.
This is not a sign of poor management. It is the typical structure of knowledge work.
According to McKinsey research, email alone consumes over 11 hours per week. Workers spend 1.8 hours every day searching for information. Asana's Work Index estimates that 103 hours per year are lost to unnecessary meetings, and as much as 60% of working time goes to coordination: status updates, internal communication, and chasing information instead of doing real work.
AI solutions of recent years have addressed this problem. But only partially.
In 2023, the era of AI assistants in the enterprise began. Microsoft 365 Copilot was one of the first truly large-scale deployments.
The results have been measurable. A Forrester Total Economic Impact study commissioned by Microsoft estimated 9 hours saved per user per month. 73% of users complete tasks faster. 70% report higher productivity. In the best deployments, first-year ROI reaches 116 to 400%.
Good. Genuinely good.
But let's look more closely at what these numbers actually mean.
Copilot sped up individual tasks. It wrote a draft faster. Summarised a meeting faster. Generated a response faster. These are real savings, but they occur at the task level.
That coordination burden, that 60% of working time? Still there. Just slightly smoother. Copilot did not change whose calendar those tasks still lived in.
In March 2026, Microsoft launched Copilot Cowork in partnership with Anthropic, and it represents a categorical shift in how AI participates in work.
Copilot helps you do the coordination work. Cowork handles it for you.
That is quite a different thing.
Cowork is not a chatbot you prompt and wait for a response from. It is an execution engine: you describe what you need, it breaks the task into steps, pulls the necessary context from your environment (emails, calendar, Teams, SharePoint) and carries the task through to completion. You remain in control: you can pause, redirect, or approve each step before it proceeds.
When Cowork prepares a leadership status update, gathers the data, writes the summary and schedules the follow-up, it does not speed up that work. It removes it from your calendar. Or nearly entirely, depending on whether you want to approve each step or simply let it run.
Task-level productivity and project-level productivity are different things.The former means an individual task takes less time. The latter means the entire coordination layer shifts off people's shoulders. Until now, AI tools have operated at the first level. Cowork operates at the second.
In practice, this looks something like this:
Weekly leadership reporting. Before: two hours of compiling, multiple people involved. With Cowork: one instruction, one approval, done.
Project status updates to stakeholders. Before: a manual process that gets skipped under pressure or done hastily. With Cowork: a recurring workflow that runs without anyone needing to remember it.
New team member onboarding communications. Before: nobody remembers every step, quality varies. With Cowork: the process is encoded in a skill that repeats consistently every time.
There is one thing that needs to be said plainly.
In Copilot deployments, licences go underused in 30 to 60% of organisations within six months. Not because the technology is poor, but because the deployment was handled poorly. Without an adoption programme, active usage plateaus at 15 to 30%. With structured deployment, organisations reach 55 to 70%.
Cowork does not fix a poor deployment. It amplifies it.
Return on investment comes from adoption, not the licence. And adoption requires clarity on what is being automated and why, before anyone opens a settings menu.
Organisations that understand the difference between Copilot and Cowork today are building their competitive advantage for the next two years.
They are not just looking for a faster way to do existing tasks. They are asking which tasks can be removed from the calendar entirely, and building around that the processes, skills, and governance structures that make it sustainable.
Let's figure out together what could be removed from your calendar.
Sources