Operations Operating practice

Bottleneck Analysis

Bottleneck analysis measures flow, waiting time, and WIP to find the bottleneck and derive relief options.

Bottleneck analysis compares waiting time, utilisation, and work in progress to locate the tightest point in a system. The resulting view directs improvement toward the step, approval, or handoff with the greatest effect on flow.

Core question

Which step currently limits total throughput, and what evidence distinguishes the constraint from a local delay?

Plan Bottleneck Analysis Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 3-8
Time: 60–120 minutes plus measurement across representative operating cycles.

The steps form one complete method run.

Paper illustration for Bottleneck Analysis.

Flow
Flow map
Bound steps and units from input to system goal.
Measure
Capacity view
Collect demand, effective capacity, cycle time, queue, and WIP by step.
Test
Constraint evidence
Observe blocking and starving; test the constraint hypothesis by relief or load test.
Focus
Focus rules
Protect constraint time and align release and priorities; avoid local optimisation.
Repeat
Next constraint
Remeasure after effect and identify the shifted constraint.

Add new evidence at review and version decisions with the prior state.

A good fit when

Bei einem Fluss, der sich an einer Stelle staut, sucht die Methode die Kapazitätsgrenze mit dem größten Hebel. Sie erklärt, warum Mehrarbeit an anderer Stelle den Durchsatz kaum verbessert.

Ideal for

Throughput problems
Kanban and delivery processes
Operational overload

Not good for

One-off tasks
Problems without process flow
Pure root-cause analysis without flow data

Outputs

Next constraint
Bottleneck register with capacity, demand, queue, utilisation, blocking/starving, constraint test, and action.

Bottleneck Analysis · working structure

Fictional example

Fictional values show the actual method fields.

Bottleneck Analysis · working structure
Step	Demand	Capacity	Queue/WIP	Blocking/Starving	Constraint test
PreparationAdd evidence and rationale.	16/h	14/h	3	blocked before handoff	after elevation new constraint at 14/h
HandoffAdd evidence and rationale.	16/h	8/h	11	never starved	second person raises handoff capacity to 16/h; system reaches 14/h
PaymentAdd evidence and rationale.	16/h	18/h	0	often starved	no throughput effect

1. Demand
Preparation
16/h
Handoff
16/h
Payment
16/h
2. Capacity
Preparation
14/h
Handoff
8/h
Payment
18/h
3. Queue/WIP
Preparation
3
Handoff
11
Payment
0
4. Blocking/Starving
Preparation
blocked before handoff
Handoff
never starved
Payment
often starved
5. Constraint test
Preparation
after elevation new constraint at 14/h
Handoff
second person raises handoff capacity to 16/h; system reaches 14/h
Payment
no throughput effect

All values are fictional.

Reference · original teaching example

First step

Set system boundary, goal, throughput measure, and representative demand window.

Open the method guide

Good to do first

Delivery

Value Stream Mapping

Supplies the per-step flow and throughput data used to locate the constraint.

Where to go next?

Operations

Theory of Constraints

Aligns planning and work consistently around the identified constraint.

Engineering

Kanban

Limits WIP ahead of the constraint so it is not overloaded further.

Deep dive

Purpose

For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.

How it works

Wait times, utilization, and work in progress are examined together to identify the tightest point in the system. This clarifies whether the bottleneck lies in work steps, approvals, or handovers. Changes then target specifically the point where relief accelerates flow the most.

In detail

Bottleneck Analysis sees a system as a chain whose performance is set by the slowest or most constrained point. The method looks for queueing, waiting, high utilization, and growing work in progress. Once the bottleneck is identified, measures are aimed at protecting it, relieving it, or increasing capacity. After that, the team checks whether the bottleneck has moved.

Facilitation

Collect data on waiting time, throughput, utilization, and inventory. Visualize the flow and ask where work regularly gets stuck. Avoid measures at convenient but non-constraining points and verify the new system bottleneck after changes.

The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Flow Measurement Constraints

Sources

Bottleneck Analysistocico.orgTOCICO, the Theory of Constraints certification body; explains the focus on the single limiting bottleneck of a system.

Artifact templates

Bottleneck Analysis: WorksheetSet subject, evidence, roles, flow, and review.

markdown

bottleneck-analysis-working-template.md

Set subject, evidence, roles, flow, and review.

Bottleneck Analysis: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 60–120 minutes plus measurement across representative operating cycles.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: End-to-end flow, demand, capacity, queues, throughput, and WIP by step
Roles: Flow owner · process participants · data owner · constraint owner
Advance information: Set system boundary, goal, throughput measure, and representative demand window.
Overall time needed: 60–120 minutes plus measurement across representative operating cycles.
Setup: Prepare a workspace with Flow · Measure · Test · Focus · Repeat; separate example from live data.

Prepare for the work steps

Flow: Flow map

Set system boundary, goal, throughput measure, and representative demand window.
End-to-end flow, demand, capacity, queues, throughput, and WIP by step