How to find the hours your team is losing to busywork
A practical way to spot, measure, and reclaim the repetitive work quietly eating your team’s week, before you automate anything.
Most teams can feel that something is slow. What they rarely have is a number. “We spend ages on reporting” is a feeling. “Reporting costs us 11 hours a week across the team” is a decision you can act on.
Here is the approach we use to turn the feeling into a number, and then into time saved.
1. List the work nobody chose to do
Start with the tasks that exist only because a tool, a format, or a hand-off requires them: re-keying data between systems, formatting reports, chasing approvals, copying numbers into slides. These are rarely in anyone’s job description, yet they fill the calendar.
2. Measure the real cost, not the guess
For each task, capture three things:
- Frequency: how often it happens (daily, weekly, per customer).
- Duration: how long it actually takes, timed, not estimated.
- People: how many are involved, including the reviewers and approvers.
Multiply it out and annualise. A 30-minute daily task is over 120 hours a year, per person. The totals are usually uncomfortable, which is the point.
3. Separate judgement from mechanics
For every step, ask: does this require human judgement, or is it mechanical? Mechanical steps (extract, transform, route, summarise, format) are exactly what modern AI does reliably. Judgement stays with your team. Most processes are 70–90% mechanics wrapped around a few real decisions.
4. Rank by hours, not by excitement
The best first project is rarely the most exciting one. It’s the boring, high-volume task with the biggest annual hour count and the lowest risk. Win there, measure it, and reinvest the time into the next one.
This is the heart of a process audit: make the invisible cost visible, then remove it deliberately. If you’d like us to run that exercise with your team, book a strategy call.