“It only takes two minutes” can be a perfectly accurate description of a task and a poor description of its cost.
At 1,000 repetitions a week, two minutes adds up to more than 33 hours of handling time. That is before checking, correction, and waiting enter the calculation. The task can remain small for every individual person while consuming a substantial amount of the team's week.
These are useful places to look when an organization feels busy but work keeps arriving late.
Follow the repetition
A vendor packet gets checked against a list. A support message gets read before it is assigned. Someone copies information from a PDF into a tracker. A logistics coordinator compares two documents to understand a shipment discrepancy.
Each action may be necessary. The question is what it takes to complete the whole case. The same information may be read several times, entered in more than one place, or checked again because the previous check is invisible.
Start by recording what actually happens. Count arrivals, handling time, corrections, and handoffs. Include the informal steps: asking a colleague, searching for the latest file, finding out whether somebody already dealt with it. Those steps are easy to omit from a process diagram and expensive to repeat.
Separate effort from waiting
A two-minute check may sit in a queue for a day. Faster checking helps, but the delay also depends on when someone notices the item, whether they have the necessary context, and who is allowed to move it forward.
Follow timestamps from arrival to completion. Then compare elapsed time with active handling time. A large gap points to coordination or capacity problems that a faster extraction step alone may leave unresolved.
Growth puts those weaknesses under pressure. As hypothetical stress tests, consider a call center moving from 200 to 600 daily cases, vendor intake increasing from 50 to 200 packets a month, or a quality team moving from five to twenty weekly audits. Each operation will have its own capacity limits. Ask what happens to the queue, review capacity, and correction work at each volume.
Count the second pass
Manual processes also vary. Different people may interpret an instruction differently, miss a detail during a busy period, or route an item to the wrong place. A mistake creates work beyond the original task: investigation, correction, communication, and sometimes another round of approval.
Track those outcomes separately. A low average handling time can conceal a long tail of difficult corrections. Conversely, time spent on a careful first pass may prevent much more work later. Removing a check without understanding its purpose can make the numbers look better briefly and the process worse.
The aim is to see where attention is producing value and where it is compensating for missing structure.
Ask what the routine is displacing
Opportunity cost becomes more concrete when it has a name. A specialist spending the afternoon assembling records has less time for root-cause analysis. A support team sorting its inbox has less time to resolve the requests inside it.
Ask the people doing the work which tasks interrupt them, which require expertise, and which are repetitive but easy to get wrong. Avoid assuming that every routine is unwelcome. Some checks provide useful context or help someone notice a larger problem.
A redesign should preserve that knowledge while reducing repeated effort. Employee feedback matters here because the time sheet alone cannot show how fragmented the work feels.
Build around a specific change
Software can help by making state visible, reducing duplicate entry, validating fields, or moving an approved result between systems. Where documents and messages need interpretation, a model can contribute extraction, classification, or a draft summary.
Choose a bounded change and measure its effect on the whole case. For a hypothetical packet review, that might mean preparing the required fields with source references, flagging missing documents, and leaving the final decision with the existing reviewer.
Keep the baseline. Compare handling time, waiting time, corrections, and backlog after the change. Ask what the team does with the recovered capacity.
The next time a recurring task is described as taking only a couple of minutes, put it on a weekly timeline. Mark every repetition and every person it interrupts. That picture is often specific enough to begin designing something better.