How to identify bottlenecks in a process
To identify bottlenecks in a process, look at where work waits, not at who works slowly. A bottleneck is the one step where work piles up, like the narrow neck of a bottle that decides how fast the water comes out. It sets the pace of the whole process, however fast everything else runs.
Signs that you have one
- Work piles up in front of one person or one step, while the people after it have little to do.
- "Waiting for" is the most common status in your lists.
- People chase each other by phone or chat to get things moving.
- Deadlines slip although nobody felt overloaded.
Working time and waiting time
The usual mistake is to look for the slowest worker or the longest task. In most offices the work itself is short and the waiting is long.
An example with invented figures. A quote takes about an hour of real work: understanding the request, writing the quote, checking the price and sending it. Yet the customer often receives it most of a week later. The dates show why. Prices are approved by one manager, who does this on Fridays. A quote written on Monday waits four days at that one step.
Typing faster would change nothing. Approving prices twice a week would cut the wait roughly in half. That is what a bottleneck looks like: a step with a queue in front of it, and often a step that is quick in itself.
Five steps to find it
- Pick one process with a clear start and end. "From request to quote sent", not "sales".
- List the steps as they really happen. Ask the people who do them. The process on paper and the real one usually differ.
- Collect dates for twenty to thirty recent cases. For each step, when did the case arrive and when did it move on? Emails and approvals carry these dates.
- Work out the wait before each step. Look at the usual case and at the worst one. A step that is normally quick but sometimes takes two weeks is a bottleneck too.
- Go to the step with the longest wait and ask why. The dates tell you where. Only the people there can tell you the reason.
Four causes you will meet most often
- Only one person can do it. Holidays, illness and a full calendar stop everything.
- Work is collected and done in one go. "Approvals on Friday", "invoices at month end". Each case waits for the next round.
- Information is missing. The case arrives incomplete, goes back and joins the queue again.
- Nobody owns the handover. One side has finished and the other side has not noticed yet.
What to do once you have found it
Fix the bottleneck and nothing else. Speeding up any other step only makes the queue in front of the bottleneck longer. Common remedies are simple:
- a deputy who may also do the step,
- doing the step more often,
- a required field at the start, so that cases arrive complete,
- a time limit after which the case moves on.
Then look again. Once one bottleneck is gone, another step becomes the slowest. That is normal and a sign of progress. Stop when the remaining wait no longer bothers customers or the team.
Doing this by hand works well for one process. Software that draws the same picture from the dates in your data is called process mining, which has its own article.
How Worknano handles this
Worknano Process Mining reads the dates and times stored in your records and rebuilds the path of each case from start to finish. It shows how long cases take between stages, on average and in the worst case. It shows where work waits longest and who owns that stage. It then proposes an automation that would fix the bottleneck, which you approve. The next run shows whether the figure improved. In Dashboards, a click on a part of a chart opens the records behind it.
- Process Mining: how work really flows
- Dashboards: from a number to the records behind it
- Workflows: turning the fix into an automation
Create a free workspace and see where your work waits longest.