Manual work is often invisible until it disrupts performance or quality. Nobody records the twenty minutes spent rebuilding a weekly report, the half-hour of checking whether an order reached finance, or the afternoon lost to reconciling two lists that should have agreed. Each task looks small and reasonable on its own. Together they become a hidden operating cost that leadership rarely sees in any budget line.
A deliberate measurement approach exposes that hidden labour and lets leadership target the improvements that matter most. This article sets out a practical way to count manual steps, assess their effect on throughput and quality, and prioritise automation or standardisation that scales without removing the human judgement the business still needs.
Why manual work hides so well
Manual work stays hidden for structural reasons, not because people are concealing it.
- It is spread thinly. Five minutes here and ten minutes there rarely trigger concern. The cost only becomes visible when it is added up across people, weeks and transaction volumes.
- It lives between systems. Copying a customer from the CRM into the finance platform belongs to neither system, so neither system reports on it.
- It becomes part of the job. Once a workaround has been running for a year, it is described as "how we do it" rather than as a symptom.
- It is absorbed by capable people. Experienced staff compensate quietly, which keeps output steady while masking the effort required to produce it.
Asana's research into what it calls "work about work" (status updates, searching for information, switching between apps and duplicated effort) illustrates the scale of the issue. Its Anatomy of Work survey of more than 10,000 knowledge workers reports that people spend 60% of their time on work about work rather than skilled work. That is self-reported survey data from a software vendor, so it should be treated as directional rather than as a benchmark for any single business. The useful point is that the coordination and transfer work around the core job is large enough to deserve measurement in its own right.
Quantifying the hidden workload
Begin with a lightweight inventory rather than a large programme. For each recurring manual task, record:
- Frequency: how often it happens per day, week or month.
- Duration: a realistic time per occurrence, including checking and correction.
- Handoff points: where the task receives information from, and where it sends it next.
- Trigger: what tells someone to do it, such as an email, a memory, a calendar reminder or a status change.
- Failure consequence: what happens if it is late, wrong or forgotten.
Then map these tasks to outcomes such as cycle time, error rate and rework. The aim is to turn a vague sense of discomfort into a measurable backlog that can be acted on through targeted changes.
Illustrative example (hypothetical, not a client case): a services firm lists twelve recurring manual tasks across sales, operations and finance. One of them, re-keying signed orders into the billing system, takes around ten minutes and happens forty times a month. That is close to seven hours a month for one task, before counting the time spent correcting mistyped amounts. Nobody had flagged it, because each instance felt trivial.
Using evidence, not just workshops
Interviews and workshops are a good starting point, but they capture how people believe work happens. Two evidence-based techniques can sharpen the picture.
Process mining uses event log data from systems such as ERP and CRM platforms to reconstruct how a process actually runs end to end, revealing bottlenecks, variations and deviations from the intended path. Task mining works at a finer level, analysing user interaction data such as clicks, keystrokes and data entries to understand individual tasks. IBM notes that task mining raises privacy concerns because it records user actions, and that users should approve such tools and have their personal data protected through anonymisation.
Neither technique is required for a first inventory. They become worthwhile when the volume of work is high, when opinions about the process conflict, or when an automation investment needs stronger evidence than estimates.
Warning signs that manual work is larger than you think
- Staff keep personal spreadsheets or trackers beside the official systems.
- Month-end or week-end routines require the same few people every time.
- Reports are assembled by hand from exports.
- Teams regularly chase each other to confirm that something has happened. (See why chasing people for updates is a systems failure.)
- Holidays and absences cause visible slowdowns in routine work.
- Errors are fixed downstream instead of prevented at the point of entry.
From measurement to action
- Rank tasks by impact on value delivery and risk of failure. Weigh hours consumed, but also customer impact, financial exposure and how often errors occur. A low-volume task that can misstate an invoice may matter more than a high-volume task with no downstream consequence.
- Prototype small automation or standardisation efforts and validate the results quickly. Often the first fix is not automation at all, but removing an unnecessary step, standardising a form or agreeing which system owns a field. Measure the before and after against the same inventory.
- Embed ownership and accountability for each automated or streamlined step. Someone must own the new way of working, monitor that it still works, and decide when it needs to change.
A practical diagnostic
For any team, ask these questions and write the answers down:
- Which tasks would stop if one specific person were away for two weeks?
- Where is the same piece of information typed into more than one system?
- Which recurring tasks exist only because two systems do not share data?
- Which checks exist because an earlier step is unreliable?
- How many hours a month go into producing reports rather than using them?
The tasks that appear in more than one answer are usually the best candidates for early attention. Our related piece on finding the manual work nobody is measuring goes further into discovery techniques.
Trade-offs to keep in view
- Not all manual work is waste. Judgement, customer conversations and genuine exception handling should stay with people. The target is avoidable work, not human involvement.
- Measurement has a cost. A detailed time study across every team can consume more effort than it saves. Start with the areas where friction is already obvious.
- Automating a poor process preserves the problem. If a task exists because of a broken upstream step, fixing that step is usually better than automating the workaround. See before you automate, understand how the work actually moves.
- Monitoring can feel like surveillance. Be explicit that the aim is to find system problems, not to grade individuals.
Implications for leadership
Quantified manual work reframes resource planning and investment. Instead of asking for more headcount or another tool, leadership can see where capacity is being consumed and why. It also helps avoid overfitting to current tools, and instead builds capabilities that endure as processes evolve.
What better looks like
In a business that has dealt with its hidden manual work, routine information is captured once and moves to where it is needed. Status is visible without anyone chasing it. Reports are produced from systems rather than assembled by hand. Staff time goes on judgement, customers and exceptions, and the remaining manual steps are known, documented and deliberately kept. Where that picture feels distant, a structured Digital Systems Audit is one way to establish the baseline before deciding what to fix, integrate or automate.
Sources and further reading
- How Work About Work Gets in the Way of Real Work [2026] • Asana (last verified 10 October 2026)
- What Is Task Mining? - IBM (last verified 10 October 2026)
- What is Process Mining? - IBM (last verified 10 October 2026)
Related Mellorca reading
- How Manual Data Transfer Becomes an Operational Bottleneck
- Why Work Gets Lost Between Teams
- Why Your Business Feels Harder to Run Than It Should