Why Bottleneck Analysis Is a Weekly Job, Not a One-Time Project
Most operations managers know they have a bottleneck. Many have even done a bottleneck analysis — once, probably as part of a lean initiative or a capital justification. They found the constraint, made some improvements, and moved on.
The problem is that bottlenecks move.
When you fix the constraint at Station 4, Station 7 becomes the new constraint. When you add capacity to Line 2, the shared material replenishment pathway becomes the bottleneck. When you hire two more assemblers, the quality inspection step becomes the limit.
Every meaningful improvement shifts the system's constraint. If you're only running bottleneck analysis when something is visibly broken, you're always chasing yesterday's problem.
A weekly bottleneck analysis — brief, structured, and data-driven — keeps you ahead of it.
Step 1: Map the Value Stream at Current Speed (15 minutes)
Start with a current-state picture of where your operation is running relative to target, station by station or process step by process step.
This doesn't need to be a formal value stream map. You need one piece of information per station: **actual output rate vs. target output rate.**
If you have real-time throughput data, pull the prior 5 days of per-station output. If you're working from shift reports, use the last week's end-of-shift counts.
What you're looking for: which station is consistently running below 90% of its target rate? That's your primary constraint candidate.
One rule: if you don't have station-level data and can only see line-level totals, your first priority is fixing the data problem. You cannot find a bottleneck you cannot see.
Step 2: Separate Downtime Losses from Speed Losses (10 minutes)
Not all underperformance at a station is the same problem.
A station running at 80% of target because it's going down for 30 minutes twice a shift has a different solution than a station running at 80% because it's running at 80% speed continuously. The first is a maintenance/reliability problem. The second is a cycle time or staffing problem.
For each station that's running below 90%, ask: **is the loss due to downtime events or chronic speed reduction?**
If your downtime log shows no events at the underperforming station, but throughput is consistently below target, you have a chronic speed loss — often caused by minor stoppages that don't get logged, operator pace variation, or a process parameter that's drifted.
If the station shows frequent downtime events, you have a reliability problem that needs a different intervention.
Step 3: Quantify the Bottleneck's True Cost (10 minutes)
Before deciding what to do about the bottleneck, quantify what it's costing you.
Formula: **Lost units per day × contribution margin per unit × working days per month**
If the bottleneck is preventing 40 units per shift and you run 2 shifts, that's 80 units per day. At $22 contribution margin per unit, that's $1,760 per day — $38,720 per month. That number tells you how much it's worth to fix.
This step is often skipped, and it matters: it determines how much to invest in the solution. A $38,000/month bottleneck loss justifies a $20,000 machine upgrade. It doesn't need to wait for the annual capital budget cycle.
Step 4: Apply the Five-Question Diagnostic (20 minutes)
For the identified bottleneck station, answer these five questions:
1. Is the station fully staffed? Understaffing at the constraint is the fastest and cheapest fix. One additional operator at the constraint can sometimes eliminate 15–20% of the loss immediately.
2. Is material always available when needed? Material starvation — the constraint waiting for upstream supply — is a scheduling problem, not a capacity problem. The fix is replenishment frequency and signal design, not equipment investment.
3. Is the equipment running at rated speed? Check whether process parameters (feed rate, cycle time settings, temperature) match engineering specifications. Equipment running at 85% of rated speed due to conservative settings is recoverable capacity.
4. Is first-pass quality at the constraint acceptable? High rework rates at the constraint station consume capacity twice — once for the failed unit and once for the rework. A 5% rework rate at a bottleneck effectively reduces its capacity by more than 5%.
5. Is there a scheduling mismatch? Sometimes the constraint isn't underperforming — the upstream process is flooding it with more work than it can handle. The station looks like a bottleneck because WIP is piling up in front of it, but the real problem is scheduling.
Step 5: Set One Constraint-Focused Action for the Coming Week (5 minutes)
The output of bottleneck analysis should be a single, specific action — not a list of recommendations.
"Investigate machine speed settings at Station 4" is not an action. "Facilities manager to pull OEM cycle time spec and compare to current PLC setting by Thursday, report back to ops lead Friday morning" is an action.
The discipline of weekly bottleneck analysis is not about generating more work — it's about focusing finite improvement capacity on the one place where it will have the greatest impact on output.
One targeted action per week, consistently executed, compounds into major throughput gains over a quarter. Scattered improvement activity on non-constraint stations produces effort without results.
Building the Habit
A weekly bottleneck analysis should take under an hour with the right data in front of you. If it's taking longer, the data infrastructure isn't good enough — and that's the real problem to solve.
The goal is a standing Monday morning meeting: 45 minutes, five steps, one clear owner for the week's constraint action. Repeat 52 times per year and your operation will look dramatically different at the end of it.
See how OpsOS tracks this in real time → [Book a Demo](https://opsos.pro/#contact)
Related: [OEE Explained for Plant Managers Who Don't Have Time for Textbooks](/blog/oee-explained-plant-managers) | [Shift Performance Reports: What You Should Be Tracking Every Single Day](/blog/shift-performance-reports)
Frequently Asked Questions
QHow often should I run a bottleneck analysis?
Bottleneck analysis should be a weekly process, not a one-time project. Every meaningful improvement shifts the system constraint to a different point. A standing weekly review — using the 5-step process — keeps you ahead of a moving bottleneck rather than chasing yesterday's problem.
QWhat is the difference between a downtime loss and a speed loss at a bottleneck station?
A downtime loss means the station is stopping and restarting — a maintenance or reliability problem. A speed loss means the station is running continuously but below its target rate — a cycle time, staffing, or process parameter problem. Each requires a different intervention.
QHow do I calculate the cost of a bottleneck?
Multiply lost units per day by your contribution margin per unit, then multiply by working days per month. This gives you the monthly cost of the constraint — which determines how much it is worth investing to eliminate it.