Method guideOperations

Theory of Constraints

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

ComplexityHigh

Time2-4 h Analyse, laufend

Participants3-12

FormatWorkshop + async

MaturityCanonical

Plan Theory of Constraints

Prerequisite

What needs to be finished first

Complete firstDecision subject

Set the system boundary, goal, and one throughput measure before examining local utilisation.

Without a clear boundary, cases and signals become mixed.

Complete firstEvidence access

System goal, throughput measure, process flow, demand and capacity data, constraint log, and action board

Missing sources are marked as open assumptions.

Preparation

What needs to be ready before start

Materials

System goal, throughput measure, process flow, demand and capacity data, constraint log, and action board

People / roles

System owner · process participants before and after the constraint · data owner · action owners

Pre-read

Set the system boundary, goal, and one throughput measure before examining local utilisation.

Time needed

90–180 minutes for analysis and action plan; verify effect across several operating cycles.

Setup

Divide the workspace into System goal · Identify constraint · Exploit · Subordinate · Elevate and repeat; keep sources, assumptions, and decisions separate.

Core question

The one question this method answers

Which constraint currently limits the system goal, and how will we exploit, subordinate, and elevate it?

Flow

Phases with goal, actions, output and pitfall

The flow is examined from the perspective of its weakest point. This shows where additional capacity can create real effect and where it would only increase WIP. After each improvement, attention shifts to the next limiting factor.

Theory of Constraints · working structure

Fictional example

Fictional values demonstrate the method-specific fields.

Measurable system goal

Define system boundary, customer value, and throughput measure; subordinate local metrics to the system goal.

Goal: on-time equipment handoffs; measure: complete handoffs per Saturday with complaints below 3%.

Evidenced constraint

Measure flow and queues; identify the one factor currently limiting total throughput.

Handoff handles 8 units/hour, preparation 14, payment 18; 11 units queue before handoff.

Exploit rules

Protect available constraint time without major investment and focus it on throughput-producing work.

Units arrive fully prepared; break cover exists; questions leave the handoff station.

Aligned system flow

Align release, priorities, and other areas to the constraint cadence; define buffer boundaries.

Release at most eight ready units per hour; preparation helps when buffer falls below three.

Next improvement cycle

If exploit and subordinate are insufficient, add capacity deliberately; then identify the constraint again and avoid inertia.

A second handoff raises handoff capacity to 16/hour; preparation remains at 14 and becomes the new constraint.

All values are fictional.

Reference · original teaching example

1
System goal
Measurable system goal
Goal
Measurable system goal: Define system boundary, customer value, and throughput measure; subordinate local metrics to the system goal.
Inputs for this step
- Set the system boundary, goal, and one throughput measure before examining local utilisation.
- System goal, throughput measure, process flow, demand and capacity data, constraint log, and action board
Actions
- Define system boundary, customer value, and throughput measure; subordinate local metrics to the system goal.
Output
Measurable system goal
Define system boundary, customer value, and throughput measure; subordinate local metrics to the system goal.
Quality check
Are boundary, goal, and throughput measure explicit and agreed?
Pitfall
Each station optimises utilisation without one system goal. Agree an end-to-end goal, throughput measure, and protective measure.
Timing: 15–25 minutes
2
Constraint
Evidenced constraint
Goal
Evidenced constraint: Measure flow and queues; identify the one factor currently limiting total throughput.
Inputs for this step
- Measurable system goal
Actions
- Measure flow and queues; identify the one factor currently limiting total throughput.
Output
Evidenced constraint
Measure flow and queues; identify the one factor currently limiting total throughput.
Quality check
Do data show that more capacity at the candidate could raise system throughput?
Pitfall
The loudest complaint is labelled the constraint without flow data. Compare capacity, demand, and queue at each step and test the constraint hypothesis.
Timing: 25–40 minutes
3
Exploit
Exploit rules
Goal
Exploit rules: Protect available constraint time without major investment and focus it on throughput-producing work.
Inputs for this step
- Evidenced constraint
Actions
- Protect available constraint time without major investment and focus it on throughput-producing work.
Output
Exploit rules
Protect available constraint time without major investment and focus it on throughput-producing work.
Quality check
Do rules measurably reduce idle time, disruption, and wrong work at the constraint?
Pitfall
More work is pushed to the constraint although missing inputs still block it. Observe constraint time and remove interruptions, rework, and missing inputs first.
Timing: 20–30 minutes
4
Subordinate
Aligned system flow
Goal
Aligned system flow: Align release, priorities, and other areas to the constraint cadence; define buffer boundaries.
Inputs for this step
- Exploit rules
Actions
- Align release, priorities, and other areas to the constraint cadence; define buffer boundaries.
Output
Aligned system flow
Align release, priorities, and other areas to the constraint cadence; define buffer boundaries.
Quality check
Do upstream and downstream rules support the constraint rather than local utilisation?
Pitfall
Upstream keeps producing, increasing inventory and search work. Tie release and priorities to constraint pace and buffer.
Timing: 20–35 minutes
5
Elevate
Next improvement cycle
Goal
Next improvement cycle: If exploit and subordinate are insufficient, add capacity deliberately; then identify the constraint again and avoid inertia.
Inputs for this step
- Aligned system flow
Actions
- If exploit and subordinate are insufficient, add capacity deliberately; then identify the constraint again and avoid inertia.
Output
Next improvement cycle
If exploit and subordinate are insufficient, add capacity deliberately; then identify the constraint again and avoid inertia.
Quality check
Is elevation justified by the remaining throughput gap, and was the new constraint checked?
Pitfall
After investment the former constraint remains the focus although it moved. Measure total flow again and restart step 1 with the current constraint.
Timing: One to four operating cycles

Artifact

What comes out at the end

Sketch: what the artifact looks like

Theory of Constraints · 5 StepsFind the system-limiting bottleneck, exploit it, align the rest to it, and search again after the constraint shifts

Form

TOC improvement log with evidenced constraint, exploit, subordinate, and elevate actions, plus renewed constraint check.

Versioning / ownership

Record date, owner, evidence state, decision, and review; preserve earlier cycles.

Tool alternatives

Flow and capacity data
Constraint and buffer log
Action board with throughput review

theory-of-constraints-working-template.md

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

Theory of Constraints: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 90–180 minutes for analysis and action plan; verify effect across several operating cycles.

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

Preparation for this scope

Method setup

Materials: System goal, throughput measure, process flow, demand and capacity data, constraint log, and action board
Roles: System owner · process participants before and after the constraint · data owner · action owners
Advance information: Set the system boundary, goal, and one throughput measure before examining local utilisation.
Overall time needed: 90–180 minutes for analysis and action plan; verify effect across several operating cycles.
Setup: Divide the workspace into System goal · Identify constraint · Exploit · Subordinate · Elevate and repeat; keep sources, assumptions, and decisions separate.

Prepare for the work steps

System goal: Measurable system goal

Set the system boundary, goal, and one throughput measure before examining local utilisation.
System goal, throughput measure, process flow, demand and capacity data, constraint log, and action board

Constraint: Evidenced constraint

Measurable system goal

Exploit: Exploit rules

Evidenced constraint

Subordinate: Aligned system flow

Exploit rules

Elevate: Next improvement cycle

Aligned system flow

Theory of Constraints · working structure

Measurable system goal

Define system boundary, customer value, and throughput measure; subordinate local metrics to the system goal.

...

Evidenced constraint

Measure flow and queues; identify the one factor currently limiting total throughput.

...

Exploit rules

Protect available constraint time without major investment and focus it on throughput-producing work.

...

Aligned system flow

Align release, priorities, and other areas to the constraint cadence; define buffer boundaries.

...

Next improvement cycle

If exploit and subordinate are insufficient, add capacity deliberately; then identify the constraint again and avoid inertia.

...

The blank worksheet contains prompts only.

Reference · original teaching example

System goal: Measurable system goal

Expected artifact: Measurable system goal

Define system boundary, customer value, and throughput measure; subordinate local metrics to the system goal.

Entry:

...

Are boundary, goal, and throughput measure explicit and agreed?

Constraint: Evidenced constraint

Expected artifact: Evidenced constraint

Measure flow and queues; identify the one factor currently limiting total throughput.

Entry:

...

Do data show that more capacity at the candidate could raise system throughput?

Exploit: Exploit rules

Expected artifact: Exploit rules

Protect available constraint time without major investment and focus it on throughput-producing work.

Entry:

...

Do rules measurably reduce idle time, disruption, and wrong work at the constraint?

Subordinate: Aligned system flow

Expected artifact: Aligned system flow

Align release, priorities, and other areas to the constraint cadence; define buffer boundaries.

Entry:

...

Do upstream and downstream rules support the constraint rather than local utilisation?

Elevate: Next improvement cycle

Expected artifact: Next improvement cycle

If exploit and subordinate are insufficient, add capacity deliberately; then identify the constraint again and avoid inertia.

Entry:

...

Is elevation justified by the remaining throughput gap, and was the new constraint checked?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/theory-of-constraints/run-sheet

Example output

Concrete filled scenario, fictional example

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

theory-of-constraints-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Theory of Constraints · working structure

Measurable system goal

Goal: on-time equipment handoffs; measure: complete handoffs per Saturday with complaints below 3%.

Evidenced constraint

Handoff handles 8 units/hour, preparation 14, payment 18; 11 units queue before handoff.

Exploit rules

Units arrive fully prepared; break cover exists; questions leave the handoff station.

Aligned system flow

Release at most eight ready units per hour; preparation helps when buffer falls below three.

Next improvement cycle

A second handoff raises handoff capacity to 16/hour; preparation remains at 14 and becomes the new constraint.

Pitfalls

Recognize symptoms and steer against them

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

Measurable system goalEach station optimises utilisation without one system goal.View in phase
Evidenced constraintThe loudest complaint is labelled the constraint without flow data.View in phase
Exploit rulesMore work is pushed to the constraint although missing inputs still block it.View in phase
Aligned system flowUpstream keeps producing, increasing inventory and search work.View in phase
Next improvement cycleAfter investment the former constraint remains the focus although it moved.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop System goal: Are boundary, goal, and throughput measure explicit and agreed?

Stop Identify constraint: Do data show that more capacity at the candidate could raise system throughput?

Stop Exploit: Do rules measurably reduce idle time, disruption, and wrong work at the constraint?

Stop Subordinate: Do upstream and downstream rules support the constraint rather than local utilisation?

Stop Elevate and repeat: Is elevation justified by the remaining throughput gap, and was the new constraint checked?

Where to go next?

Operations

Bottleneck Analysis

Investigates the found bottleneck with a deeper cause and capacity analysis.

Engineering

Kanban

Limits work at the bottleneck through visible WIP limits.

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 profile More methods