Bottleneck Detection · 5 min read

How to Find the Bottleneck in Your Business

The bottleneck is the step where work piles up and waits, not the person who looks busiest. Measure how much each step finishes and how long work sits in front of it. Make that step better before you add people or tools anywhere else.

Busyness is a bad compass

Every company has someone who is slammed. That feeling does not locate the constraint. A person can be busy on work that is not the limit, including rework, status meetings, and helping downstream because upstream overproduced. The constraint is the step that sets the pace of finished output. Everything faster than that step is building a pile or waiting on one.

You are looking for a step, not a personality. "Sales is the bottleneck" is useful only if you can point at the handoff: leads waiting for a first call, proposals waiting for a price, or signed jobs waiting for a crew. Name the queue.

Measure the queue, the throughput, and the wait

For each step in the path from request to paid, write three numbers for a normal week. Throughput is how many units the step finishes. The queue is how many units are waiting at the start of the week and whether that pile is growing. Lead time is how long a typical unit sits there before the step starts, plus how long the step takes.

The bottleneck is where the queue keeps growing when demand is steady. A step can be fully occupied and still not be the constraint if the queue in front of it is stable and downstream is the one falling behind. Walk the work once. The pile is usually visible: an inbox, a whiteboard, a rack of half-finished jobs, a calendar with no open slots.

A line that runs 120, 85, 140, and 100

Suppose a small install business moves jobs through four steps. These are example counts for a day, so you can see the shape. They are not a claim about your trade.

Quote can start 120 jobs. Schedule can only place 85. Install could do 140 if the jobs were there, and invoicing can bill 100. The line finishes 85, because nothing downstream can work on a job that was never scheduled. The queue of sold-but-unscheduled work will grow. Installers looking busy with side tasks does not move that queue. Hiring another quoter makes a bigger pile in front of schedule.

If schedule jumps to 110 after a process change, the next limit might be invoicing at 100, or demand, if quote falls below the rest. Recheck after you move one step. The constraint moves. Last month's answer is a hypothesis.

Separate a spike from a standing limit

A one-week surge, a flu, or a truck that is down will grow a queue that drains when the week ends. A constraint grows the queue in ordinary weeks, or the queue never quite clears before the next wave. Look at three ordinary weeks before you buy a permanent fix for a bad Tuesday. If the pile drains on its own, staff the spike with overtime or a temp and leave the system alone.

Seasonal businesses have a constraint that moves. The limit in peak may be crews. The limit in the quiet months may be the pipeline. Write which season you are diagnosing so you do not hire peak capacity you cannot feed in March.

Exploit, then point everything at it, then spend

Change the constraint in that order. Spending is last because extra capacity on the wrong step only adds cost.

1. Exploit. Get more finished units from the step you already have. Cut the work that does not need to pass through it. Stop interrupting it. Put the best tools and the clearest priority on it.
2. Subordinate. Pace the other steps to the constraint. Quoting faster than you can schedule creates promises you will miss. Start work when the constraint can take it.
3. Elevate. Only then add hours, people, or machines at that step. Recheck the numbers after you do. The new constraint is somewhere else, and it deserves the same sequence.

What to ignore while you do this

Ignore local efficiency scores that reward a step for staying busy. A quoter at 100% utilization who feeds a scheduler at capacity is manufacturing wait. Ignore improvements downstream of a starving step. Faster invoicing does not help if the invoices are waiting on installs that are waiting on the calendar.

If you are the queue — every approval, every exception, every price — the constraint may be the owner. That still gets measured: how many decisions wait on you, and how long. Delegation and a written limit move that step the same way a second scheduler would.

Try the call

Questions operators ask