A process takes eleven days end to end and involves four hours of actual work. What does that tell you and where do you look?

What is being tested

Whether you recognise that the problem is flow rather than productivity, and know where the time actually sits.

What it tells you

The ratio of touch time to cycle time is about 1.5%. Ninety-eight per cent of the elapsed time is waiting.

That means making the work faster is nearly worthless. Halving the four hours saves two hours out of eleven days. The time is in the gaps, not in the work.

This is the single most useful diagnostic in process analysis, and it consistently surprises people who assumed the answer was automation of the work itself.

Where to look

1. Handoffs. Every transfer between teams or systems is a queue. Count them — the number of handoffs predicts cycle time better than the complexity of the work does.

2. Approval and decision points. Work waiting for a human with other priorities. Frequently the single largest block, and frequently an approval that adds no information because the approver cannot meaningfully assess what they are approving.

3. Batching. Work processed in daily or weekly cycles rather than continuously. A step that runs nightly adds up to a day regardless of how fast it is.

4. Manual steps between systems. Someone rekeying data, waiting for a file, running a report. An integration requirement in disguise.

5. Rework loops. Work that comes back adds a full cycle each time, and it is a quality signal as well as a flow signal.

6. Exception paths. If 30% of cases leave the happy path and are handled manually, the average disguises two very different processes.

The architectural response

Remove handoffs before automating them. Automating a handoff is far less valuable than removing it, and organisations routinely spend heavily on the former while the latter was available.

Removing handoffs usually means changing team boundaries — giving one team the capability to complete the work end to end. That is the value-stream alignment argument, and it is an organisational change with an architectural consequence.

What a strong answer adds

Observe the process rather than interviewing about it. People describe the process as designed, not as performed, and the difference is where the eleven days live. The undocumented workaround that everyone uses is invariably the most informative finding.