methodatlas
Method guideOperations

Bottleneck Analysis

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time1-3 h
Participants3-8
FormatWorkshop + async
MaturityEstablished
Plan Bottleneck Analysis
01

Prerequisite

What needs to be finished first

Complete firstClear boundary

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

Without a boundary, cases, periods, or variables become mixed.
Complete firstEvidence access

End-to-end flow, demand, capacity, queues, throughput, and WIP by step

Missing sources remain visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

End-to-end flow, demand, capacity, queues, throughput, and WIP by step

People / roles

Flow owner · process participants · data owner · constraint owner

Pre-read

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

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.

03

Core question

The one question this method answers

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

04

Flow

Phases with goal, actions, output and pitfall

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.

Bottleneck Analysis · working structure

Fictional example

Fictional values show the actual method fields.

Bottleneck Analysis · working structure
StepDemandCapacityQueue/WIPBlocking/StarvingConstraint test
PreparationAdd evidence and rationale.16/h14/h3blocked before handoffafter elevation new constraint at 14/h
HandoffAdd evidence and rationale.16/h8/h11never starvedsecond person raises handoff capacity to 16/h; system reaches 14/h
PaymentAdd evidence and rationale.16/h18/h0often starvedno throughput effect

  1. 1. Demand

    Preparation
    16/h
    Handoff
    16/h
    Payment
    16/h

  2. 2. Capacity

    Preparation
    14/h
    Handoff
    8/h
    Payment
    18/h

  3. 3. Queue/WIP

    Preparation
    3
    Handoff
    11
    Payment
    0

  4. 4. Blocking/Starving

    Preparation
    blocked before handoff
    Handoff
    never starved
    Payment
    often starved

  5. 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

  1. 1

    Flow

    Flow map

    Goal

    Flow map: Bound steps and units from input to system goal.

    Inputs for this step

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

    Actions

    • Bound steps and units from input to system goal.

    Output

    Flow map

    Bound steps and units from input to system goal.

    Quality check

    Are the same unit and boundary used across steps?

    Pitfall

    Local activities are compared without end-to-end boundary. Set system goal and flow unit first.

    Timing: 15–20 minutes

  2. 2

    Measure

    Capacity view

    Goal

    Capacity view: Collect demand, effective capacity, cycle time, queue, and WIP by step.

    Inputs for this step

    • Flow map

    Actions

    • Collect demand, effective capacity, cycle time, queue, and WIP by step.

    Output

    Capacity view

    Collect demand, effective capacity, cycle time, queue, and WIP by step.

    Quality check

    Are effective rather than theoretical capacities comparable?

    Pitfall

    Vendor ratings replace actual capacity. Include downtime, changeovers, and availability.

    Timing: 30–45 minutes

  3. 3

    Test

    Constraint evidence

    Goal

    Constraint evidence: Observe blocking and starving; test the constraint hypothesis by relief or load test.

    Inputs for this step

    • Capacity view

    Actions

    • Observe blocking and starving; test the constraint hypothesis by relief or load test.

    Output

    Constraint evidence

    Observe blocking and starving; test the constraint hypothesis by relief or load test.

    Quality check

    Would added candidate capacity raise total throughput?

    Pitfall

    Longest task is automatically called bottleneck. Measure system throughput during targeted relief.

    Timing: 20–30 minutes

  4. 4

    Focus

    Focus rules

    Goal

    Focus rules: Protect constraint time and align release and priorities; avoid local optimisation.

    Inputs for this step

    • Constraint evidence

    Actions

    • Protect constraint time and align release and priorities; avoid local optimisation.

    Output

    Focus rules

    Protect constraint time and align release and priorities; avoid local optimisation.

    Quality check

    Do rules improve total throughput rather than local utilisation?

    Pitfall

    More WIP is pushed before the constraint. Tie release to constraint pace and buffer.

    Timing: 20–30 minutes

  5. 5

    Repeat

    Next constraint

    Goal

    Next constraint: Remeasure after effect and identify the shifted constraint.

    Inputs for this step

    • Focus rules

    Actions

    • Remeasure after effect and identify the shifted constraint.

    Output

    Next constraint

    Remeasure after effect and identify the shifted constraint.

    Quality check

    Was the whole flow reassessed after change?

    Pitfall

    Former bottleneck remains the permanent focus. Update capacity view and restart analysis.

    Timing: One to three cycles

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Bottleneck-Analyse · Engpass-ZyklusProzessfluss, Queue, Flow-Metriken und Fokusmaßnahmen sichtbar machen
Bottleneck Analysis FlowDie Skizze zeigt einen Prozessfluss, wachsende Queue, den Engpass, Flow-Metriken, Fokusmaßnahmen und erneute Messung.Den langsamsten Schritt finden und gezielt entlastenWIP, Wartezeit und Durchsatz zeigen, welcher Prozessschritt den Flow begrenzt.Eingang32/TagTriageWIP 8DiagnoseWIP 24Fix10/TagVerifikation12/TagEngpassQueue wächstnach Änderung neu messenWartezeit11 hDurchsatz11/TagAuslastunghochFokusmaßnahmenschützenentlastenKapazität erhöhen
Form

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

Versioning / ownership

Record date, owner, source state, and review date; preserve prior versions.

Tool alternatives
  • Flow and capacity table
  • Queue and WIP observation
  • Constraint test log

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

Measure: Capacity view

  • Flow map

Test: Constraint evidence

  • Capacity view

Focus: Focus rules

  • Constraint evidence

Repeat: Next constraint

  • Focus rules

Bottleneck Analysis · working structure

StepDemandCapacityQueue/WIPBlocking/StarvingConstraint test
Preparation
Handoff
Payment
  • Preparation: Add evidence and rationale.
  • Handoff: Add evidence and rationale.
  • Payment: Add evidence and rationale.

The blank worksheet contains prompts only.

Reference · original teaching example

Flow: Flow map

Expected artifact: Flow map

Bound steps and units from input to system goal.

Entry:

...

  • Are the same unit and boundary used across steps?

Measure: Capacity view

Expected artifact: Capacity view

Collect demand, effective capacity, cycle time, queue, and WIP by step.

Entry:

...

  • Are effective rather than theoretical capacities comparable?

Test: Constraint evidence

Expected artifact: Constraint evidence

Observe blocking and starving; test the constraint hypothesis by relief or load test.

Entry:

...

  • Would added candidate capacity raise total throughput?

Focus: Focus rules

Expected artifact: Focus rules

Protect constraint time and align release and priorities; avoid local optimisation.

Entry:

...

  • Do rules improve total throughput rather than local utilisation?

Repeat: Next constraint

Expected artifact: Next constraint

Remeasure after effect and identify the shifted constraint.

Entry:

...

  • Was the whole flow reassessed after change?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/bottleneck-analysis/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

bottleneck-analysis-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Bottleneck Analysis · working structure

StepDemandCapacityQueue/WIPBlocking/StarvingConstraint test
Preparation16/h14/h3blocked before handoffafter elevation new constraint at 14/h
Handoff16/h8/h11never starvedsecond person raises handoff capacity to 16/h; system reaches 14/h
Payment16/h18/h0often starvedno throughput effect
07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Flow mapLocal activities are compared without end-to-end boundary.View in phase
  2. Capacity viewVendor ratings replace actual capacity.View in phase
  3. Constraint evidenceLongest task is automatically called bottleneck.View in phase
  4. Focus rulesMore WIP is pushed before the constraint.View in phase
  5. Next constraintFormer bottleneck remains the permanent focus.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Flow: Are the same unit and boundary used across steps?
Stop Measure: Are effective rather than theoretical capacities comparable?
Stop Test: Would added candidate capacity raise total throughput?
Stop Focus: Do rules improve total throughput rather than local utilisation?
Stop Repeat: Was the whole flow reassessed after change?

Method after Lean Community. The method comes from lean management, the Toyota Production System, or adjacent lean practice. Curated with 1 sources.

Sources: Bottleneck Analysis

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration for Theory of Constraints.
Operations
Theory of Constraints

Aligns planning and work consistently around the identified constraint.

Paper illustration of a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.
Engineering
Kanban

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

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods