Purpose
For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput.
Operations Operating practice
Theory of Constraints
Finds a system constraint, aligns work to it, and checks cyclically whether flow improves.
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.
Which constraint currently limits the system goal, and how will we exploit, subordinate, and elevate it?
- Participants
- 3-12
- Time
- 90–180 minutes for analysis and action plan; verify effect across several operating cycles.
The steps express the method mechanics; feedback may reopen an earlier step.
System goal
Measurable system goal
Define system boundary, customer value, and throughput measure; subordinate local metrics to the system goal.
Constraint
Evidenced constraint
Measure flow and queues; identify the one factor currently limiting total throughput.
Exploit
Exploit rules
Protect available constraint time without major investment and focus it on throughput-producing work.
Subordinate
Aligned system flow
Align release, priorities, and other areas to the constraint cadence; define buffer boundaries.
Elevate
Next improvement cycle
If exploit and subordinate are insufficient, add capacity deliberately; then identify the constraint again and avoid inertia.
At review, add evidence, update assumptions, and version the next cycle.
A good fit when
Bei einem System, das trotz Aufwand nicht schneller wird, lenkt die Methode Aufmerksamkeit auf den Engpass. Sie konzentriert Verbesserung auf die Stelle, die den Durchsatz tatsächlich begrenzt.
Ideal for
- Delivery flow
- Operations improvement
- Production and knowledge work
Not good for
- Local optimization without a system goal
- Problems without measurable flow
Outputs
Next improvement cycle
TOC improvement log with evidenced constraint, exploit, subordinate, and elevate actions, plus renewed constraint check.
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.
First step
Set the system boundary, goal, and one throughput measure before examining local utilisation.
Deep dive
How it works
Flow is viewed from the perspective of its weakest point, not from the loudest problems. This makes clear where additional capacity truly has an effect and where it just grows work in progress. After every improvement, focus shifts again to the next limiting factor.
In detail
Theory of Constraints looks at a system through its limiting factor. As long as a bottleneck sets throughput, local improvements outside that bottleneck bring little overall value. The method therefore focuses first on identifying, using, and protecting the constraint before adding capacity. When the bottleneck shifts, the cycle starts again.
Facilitation
Prepare data on lead time, WIP, queues, or capacity. Visualize the flow of work and keep asking which point limits total throughput. Avoid action lists for every area at once; focus on the constraint and the necessary coordination around it.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
Theory of Constraints: WorksheetSet subject, evidence, roles, flow, and review.markdown
Theory of Constraints: WorksheetSet subject, evidence, roles, flow, and review.
markdowntheory-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
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Delivery
Value Stream Mapping
Instead of Theory of Constraints, choose Value Stream Mapping when you want to measure an end-to-end flow with wait times and waste.
Operations
Visual Management
Makes status, exceptions, and signals recognizable at a glance so teams can react faster.
Operations
Process Mapping
Visualizes workflows with roles and handoffs so problems, media breaks, and improvement opportunities become visible.
Operations
A3 Problem Solving
Condenses problem, analysis, countermeasures, and follow-up onto one sheet and forces joint analysis.
Operations
ALPEN Method
Plans the day through tasks, effort, buffer, and control so priorities stay realistically checkable.
Operations
Gemba Walk
Goes to the place where work happens, observes the process without disrupting it, and gathers solid clues about friction.
Constraints and origin
HighWorkshop + async2-4 h Analyse, laufend
Profile
- Method form
- Operating practice
- Participants
- 3-12
- Time
- 2-4 h Analyse, laufend
- Maturity
- Canonical
- Origin
- Eliyahu M. Goldratt
Next up: Bottleneck Analysis