The productivity crisis hiding inside most organisations is not a motivation problem. It is an architecture problem.
The Uncomfortable Finding
Ask a room full of managers whether their best people are spending their time well and the answer is almost always yes, broadly speaking. Ask those same best people the same question and the answer changes.
The legal analyst who spends two hours chasing a signature before she can file a document; the finance controller who spends forty minutes reconstructing the approval chain for an invoice because nobody logged it; the procurement manager who rewrites the same vendor briefing three times because the first two versions cannot be located – these are not exceptional days. They are Tuesdays.
According to Asana’s Anatomy of Work Index, which surveyed over 10,000 knowledge workers globally, 60 percent of the average knowledge worker’s day is spent on what researchers call work about work: chasing updates, navigating communication overhead, switching between tools, and managing the logistics of work rather than doing the work itself. Only 40 percent of the day goes to the skilled tasks the person was actually hired to perform.
| 60% | Of the average knowledge worker’s day is spent on work about work, not skilled output Asana Anatomy of Work Index, 2026 |
That is not a minor inefficiency. For a team of fifty skilled professionals, it is the equivalent of thirty people doing work that produces no direct output, every single day. The thirty people doing the actual work are carrying the load of fifty.
What Work About Work Actually Looks Like
The term can sound abstract until you map it to a typical operational day. Work about work includes: finding out who is responsible for approving something, following up because the approval has not arrived, re-sending a document that got lost in an email thread, manually entering data that already exists in another system, attending a meeting whose purpose is to discuss why a previous meeting’s decisions have not been implemented.
The Speakwise 2026 knowledge worker productivity analysis, drawing on research from the Flowtrace State of Meetings Report 2025, found that knowledge workers spend an average of 11.3 hours per week in meetings, with 64 percent of recurring meetings lacking a structured agenda. The same analysis identified 209 hours per year lost to duplicated work and 352 hours per year talking about work rather than doing it. These are not edge cases. They are structural features of how most organisations are built.
| The organisations where talented people burn out fastest are not the ones with the hardest work. They are the ones where talented people spend most of their time on the logistics of work rather than the work itself. |
Why This Persists in Otherwise Smart Organisations
The reason organisations with sophisticated, capable teams still lose more than half their productive capacity to coordination overhead is structural rather than cultural. When the tools that handle different parts of a workflow are disconnected, coordination becomes the glue that holds the workflow together. And coordination, by definition, is a person’s job rather than the system’s job.
A document that has to move from one tool to another via human action requires a human to take that action. An approval that has no automatic routing mechanism requires a person to chase it. A decision record that lives only in someone’s memory requires that person to be available every time the record is needed.
The answer to the productivity problem is therefore not asking people to work more efficiently. It is removing the structural causes of the inefficiency so that the work they do is the skilled work they were hired for.
What Changes When the Architecture Changes
When workflows are documented and automated rather than held together by individual coordination effort, the time profile of the team changes. Documents move without being chased. Approvals route without being nudged. Decision records exist independently of the people who made them.
The result is not a marginal efficiency gain. It is a fundamental shift in what skilled people spend their time on. The legal analyst files documents instead of chasing signatures. The finance controller reviews exceptions instead of reconstructing audit trails. The procurement manager develops supplier relationships instead of rewriting briefings.
Flowmono’s AI Workflow Builder is designed precisely for this structural change: routing, approvals, document management, and audit records run inside one platform without requiring human coordination to hold them together. If the 60 percent problem resonates in your organisation, explore how Flowmono approaches it.
