How can I see bottlenecks in my business in real time?
A bottleneck is the step where work waits longest, and it shows up as a queue that keeps growing in front of one station while the steps after it run short. To see it as it happens, you need three things: your systems recording when each job arrives, starts and finishes at each step, a limit for each step that says when a queue is too long or a job has waited too long, and a view that makes the worst step obvious in seconds rather than after a report has been read.
Last reviewed: 24 October 2026
- The bottleneck is the step with the longest queue or the oldest waiting work.
- The whole business can only move as fast as that step.
- Most businesses already record the data needed to see it.
- Limits per step turn raw data into a clear amber or red warning.
- A live picture of the queues is quicker to read than a report or a table.
What a bottleneck looks like
Work in most businesses passes through a series of steps: goods in, booking, preparation, a machine, a check, dispatch. Each step can only handle so much at once. When one step is slower than the work arriving at it, a queue builds in front of it, and the steps after it wait for work.
That step is the bottleneck, and it sets the pace for everything. Speeding up any other step does not get more work out of the door. It only makes the queue in front of the bottleneck longer.
The signs are simple once you know where to look:
- a queue that keeps growing at one step while others stay level
- the oldest job at that step has been waiting longer than anywhere else
- the steps after it are idle or short of work
- a machine or instrument that has stopped, which turns its step into a bottleneck straight away
The data you need, and probably already have
You do not need sensors or new tracking to see a bottleneck. You need the moments your systems already record:
- a job arrived
- a job moved to the next step
- a job started and finished at a step
- a machine went down or came back
A job management, ERP, lab, warehouse or order system usually records most of these, because staff already mark work as booked in, started or done. From those events you can work out, for every step, how many jobs are waiting, how long the oldest has waited, and how many were finished in the last hour.
The last piece is a limit for each step, set by someone who knows the work: for example, amber at five waiting or 45 minutes, red at ten waiting or 90 minutes. Limits turn numbers into a warning anyone can read.
Ways to see it, from least to most effort
There is no single right answer, and the simplest option is often enough:
- Walk the floor. In a small building, looking at where work is piled up still works. It does not work for a director who is off site, for remote staff, or once the business is too big to see in one go
- A daily report. A report of jobs waiting at each step is cheap to produce from most systems. It tells you where work was stuck yesterday, not where it is stuck now
- A live dashboard. A table or chart of queues by step, refreshed every minute or so. It is accurate, but someone has to read it and work out which number matters
- A live picture. A view of the building where work visibly piles up at the stuck step, which turns amber then red. It is the quickest to read, and it works on a TV on the shop floor where everyone can see it
The more people need to act on it, and the less time they have to read it, the more a picture is worth over a table.
What it looks like in practice
We built a live demo of this for a fictional testing lab, Pendle Analytical Laboratories, which you can try at workplace-demo.varsuite.co.uk. Fill in a short form and you get your own private copy.
Samples arrive, are booked in, prepared, run on an instrument, checked and certified. Each station turns amber and then red as its queue or its oldest wait passes its limits, and a panel names the station where work is most stuck, with how many are waiting and the average wait. A Focus bottleneck button takes you straight to it, and clicking a station shows its queue in order.
Press Break an instrument and you can watch the bottleneck move: the instrument's station stops, samples queue behind it, and the panel names it within moments. Fix it and the queue drains.
The lab runs on simulated data. For your business, we build the same picture of your own building, wired to the systems you already use, as described on our Live Workplace page.
What is a bottleneck in a business?
The step in your process where work waits longest because it cannot keep up with the work arriving. The whole business can only move as fast as that step.
Do I need new tracking to see bottlenecks?
Usually not. Most job, order or stock systems already record when work arrives, starts and finishes at each step, which is enough to see where it is queuing.
Is a dashboard enough?
It can be, if someone has time to read it. A live picture of the queues is quicker to understand, especially on a shared screen on the shop floor.
Can I see an example?
Yes. Our Live Workplace demo of a fictional testing lab shows stations turning amber and red as work builds up, and lets you break an instrument to watch a bottleneck form.
Get The Signal
Practical notes on AI, websites and automation for UK businesses. One useful email at a time, unsubscribe whenever.
Still want to ask it in person?
Tell us what you are building and we will give you a straight answer, and a plan, within 72 hours.