Bottleneck

A Bottleneck is the constraint in a process flow where residual capacity is smallest. Formally: given a path through your operations (lead -> qualify -> demo -> close -> onboard), each step has some capacity and some current load. The residual capacity at each step is capacity - current_load. The Bottleneck is whichever step has the minimum residual capacity that is still positive.

If your qualification step can handle 200 leads/week and runs 150, its residual capacity is 50. If your demo step can handle 40/week and runs 38, its residual capacity is 2. The demo step is the Bottleneck - it determines how much additional Throughput your entire pipeline can absorb.

This is the same idea from network flow theory applied to operations: the maximum additional flow you can push through any path equals the capacity of its tightest link. Every unit of Throughput must pass through every step, so the step with the least room to grow is the binding constraint.

Bottlenecks are the single highest-leverage point on your P&L for two reasons:

1. Every dollar spent on non-bottleneck capacity is waste. If demos cap your pipeline at 40/week, hiring a second qualifying rep (expanding a step with residual capacity of 50) adds zero Revenue. You bought capacity you cannot use because downstream cannot absorb it. The Cost Per Unit of that hire is infinite - they produce no incremental output.

2. Every dollar spent on the Bottleneck flows directly to Throughput. Adding a second demo resource from 40 to 80/week doubles your system's effective capacity - assuming no new Bottleneck emerges downstream. That spend has a measurable marginal value: the Revenue per additional demo times the Close Rate.

This connects directly to what you learned about capacity: capacity cost is superlinear. But the Bottleneck tells you which capacity to scale. Scaling the wrong step is not merely superlinear cost - it is zero return. The Bottleneck is where your Shadow Price is highest: the marginal value of one more unit of capacity at that step equals the entire system's incremental Throughput.

Step 1: Map your Value Stream as a sequence of steps. Each step has a maximum capacity (units/time) and a current load.

Step 2: Compute residual capacity at each step. residual = capacity - current_load. Only steps with residual > 0 matter (if residual = 0, you are already at the wall, not approaching it).

Step 3: The minimum residual capacity across all steps is your Bottleneck capacity. This number tells you the maximum additional Throughput the system can absorb before something breaks.

Step 4: The step where that minimum occurs is the Bottleneck. All optimization effort concentrates here.

Example pipeline:

Bottleneck: Demo (residual = 2). The system can absorb exactly 2 more units per week before it stalls.

Critical insight: Bottlenecks migrate. The moment you expand demo capacity to 80/week, qualification (residual 50) becomes the new tightest step. You chase Bottlenecks sequentially - fix one, find the next. This is why Operators re-measure after every capacity change rather than planning all expansions at once.

Use Bottleneck analysis when:

• •Throughput is flat despite spending increases. If Marketing Spend or Labor costs are rising but Revenue is not, a Bottleneck is absorbing your investment. Find which step's queue is growing.

• •You are deciding where to allocate Budget for capacity expansion. Bottleneck analysis turns a vague 'we need to hire' into a precise 'we need one more X at the Y step, which unlocks Z units of Revenue.'

• •Pipeline Velocity is declining. Slower cycle times often mean units are waiting at the Bottleneck. Measure queue depth at each step.

• •You are building a business case for Cost Reduction vs. capacity investment. Sometimes the cheapest fix is not adding capacity but reducing waste at the Bottleneck (fewer dropped demos, faster scheduling, automation). Reducing load at the Bottleneck has the same effect as increasing capacity.

Do not over-apply it when:

• •Your system has parallel paths, not a single serial chain. Real operations often have branches. You need to identify which path is constrained, not just which step.

• •Demand is far below all capacity. If every step has large residual capacity, you do not have a Bottleneck problem - you have a Demand problem.

Bottleneck analysis is a direct application of the capacity concept you already know. Capacity taught you that scaling is superlinear in cost - Bottleneck tells you where that cost is worth paying. The Shadow Price of the Bottleneck step is the system's marginal value of capacity there; all other steps have a Shadow Price of zero for incremental capacity. Downstream, Bottleneck connects to Throughput (the Bottleneck determines it), critical path (the Bottleneck is often on it), and Pipeline Velocity (units queue at the Bottleneck, slowing the whole pipeline). When you later encounter Process Bottlenecks in more complex multi-path operations, the same residual-capacity logic applies - you just evaluate each path separately and find the binding constraint on each. Understanding Bottleneck also reframes Cost Reduction: sometimes the cheapest intervention is not adding capacity but reducing waste at the constrained step, which has the same effect on Throughput.