Two days to complete eleven minutes of work, most of your process time is queue time, not work time

Time a process properly, with a clock rather than an estimate, and the result is usually uncomfortable. Two days from the moment something arrives to the moment it is finished, of which about eleven minutes is anybody doing anything at all.

The eleven minutes are visible. They look like work, they appear in job descriptions, and they are what gets discussed whenever somebody says the process is slow. The rest is invisible, because nothing is happening and nobody is being paid to notice.

Touch time and elapsed time are different numbers

Two measurements matter and most businesses only track one. Touch time is how long the work takes when somebody is doing it. Elapsed time is how long it takes from start to finish in the real world.

Customers experience elapsed time. Colleagues waiting downstream experience elapsed time. Touch time is an internal figure that mostly matters for staffing. When the two are wildly different, and they usually are, effort spent on touch time is effort nobody outside the team can feel.

Where the two days actually go

The gaps are boringly consistent across very different businesses.

• Waiting to be noticed. Something arrives in a shared inbox or a folder. It sits there until somebody happens to look, which might be an hour or might be Monday.
• Waiting for an approval. A request goes to somebody who is in meetings all day, and it competes with two hundred other items for a moment of attention.
• Waiting for a rhythm. The next person only processes these on Thursdays, so anything arriving Thursday afternoon waits a week.
• Waiting because nobody owns it. Two people could pick it up, so it sits politely between them and each assumes the other has it.
• Waiting for a rework loop. Something was incomplete, it went back, and the round trip cost two days on its own.

None of these are performance problems. Everybody involved is busy. The item is simply not in anyone's field of view at the moment it becomes their turn.

Why teams optimise the wrong number

Buying a faster tool for a step that already takes eleven minutes is a common and understandable move. It is measurable, it has a vendor, and it produces a number that improves. Eleven minutes becomes eight.

Elapsed time goes from two days to one day, twenty-three hours and fifty-seven minutes. Nobody notices, because the saving landed on the part that was never the constraint.

How to measure your own gaps

The exercise takes a couple of hours and needs no tooling.

1. Pick twenty recent items. Real ones from the last month, not a tidy sample chosen by hand.
2. Record four timestamps for each. When it arrived. When somebody first touched it. When it moved to the next person. When it was finished.
3. Subtract. The intervals between those stamps are your queues. The remainder is the work.
4. Rank the queues. One of them is almost always much larger than the others, and it is rarely the one people would have guessed.

Most systems already hold these timestamps somewhere, even if no report surfaces them. Email holds two of them for free.

Closing a gap is usually cheap

This is the encouraging part. Speeding up work is difficult, because the work is the work. Removing a wait is often trivial, because most waits are a message that was never sent to a person who did not know it was their turn.

A notification when something lands, addressed to a named person rather than a shared address. A visible list of items sitting past an agreed age. An acknowledgement to the customer so the delay is at least an informed one. A rule that assigns ownership on arrival instead of leaving it to whoever volunteers.

None of that is difficult to build, and none of it changes how anybody does the actual job. It changes when they find out that it is theirs.

The question worth asking

Next time a process gets described as slow, resist the urge to ask how long the work takes. Ask how long it waits, and between which two steps.

If the honest answer is two days for eleven minutes of effort, the fix is not a faster tool. It is a shorter queue.