Quick reference

Memory aid

Find the bottleneck. Squeeze it dry. Support it. Expand it. Find the next one.

TL;DR

Every system has one constraint that limits throughput. Identify it, exploit it (maximize without investment), subordinate everything else, then elevate it (invest). Repeat when the constraint shifts.

What Is Theory of Constraints?

Every system has one bottleneck that limits the entire system's performance. Theory of Constraints says: find that bottleneck, get the most out of it, make everything else support it, and invest in expanding it. Then find the next bottleneck and repeat.

Tell me how you measure me, and I will tell you how I will behave.

— Eliyahu Goldratt, The Haystack Syndrome (1990)

TOC is based on the insight that a chain is only as strong as its weakest link. Improving anything other than the constraint is wasted effort — it won't improve system throughput. The Five Focusing Steps provide a systematic approach: Identify the constraint, Exploit it (get the most from it without investment), Subordinate everything else (align all resources to support the constraint), Elevate the constraint (invest to expand it), and Repeat (find the new constraint). TOC also introduces Drum-Buffer-Rope scheduling and Throughput Accounting as alternatives to traditional approaches.

The Five Focusing Steps

A circular process flow showing TOC's iterative approach to system improvement. The cycle repeats as each constraint is resolved and a new one emerges.

Identify

Find the system's constraint — the weakest link in the chain

→

Exploit

Maximize output from the constraint without new investment

→

Subordinate

Align all other processes to support the constraint

→

Elevate

Invest to increase the constraint's capacity

→

Repeat

Do not let inertia become the constraint — find the new one

Origin & context

Introduced in the business novel 'The Goal,' which became one of the best-selling business books of all time. Goldratt, a physicist, applied scientific thinking to business management.

Core Components

1

Identify the Constraint

Find the single resource, process, or policy that most limits system throughput.

Example

In a factory, the paint booth processes 40 units/hour while all other stations process 60+. The paint booth is the constraint.

2

Exploit the Constraint

Get maximum output from the constraint without spending money — ensure it's never idle, never works on defective items, never produces unneeded output.

Example

Stagger worker breaks so the paint booth runs continuously. Pre-inspect items before they reach the booth to avoid wasting constraint time on defects.

3

Subordinate Everything Else

Align all other processes to support the constraint's maximum output.

Example

Pace upstream stations to match the paint booth's rate (don't overproduce and create WIP). Schedule downstream stations based on paint booth output.

4

Elevate the Constraint

Invest to increase the constraint's capacity.

Example

Buy a second paint booth, add a shift, or upgrade to a faster system.

5

Repeat

Once the constraint is broken, find the new constraint and repeat the process.

Example

After the paint booth is expanded to 80 units/hour, the assembly station at 60 units/hour becomes the new constraint.

Goldratt's book 'The Goal' has sold millions of copies since it first appeared in 1984. It was written as a novel rather than a textbook, teaching its ideas through the story of a plant manager trying to save his factory.

When to Use Theory of Constraints

Scenario 1

Manufacturing throughput improvement

Problem it solves: Identifies and eliminates the bottleneck limiting production output.

Real-world application

A furniture manufacturer that finds its finishing department is the constraint can raise throughput without new equipment by reorganizing work so that department is never left waiting.

Scenario 2

Project management acceleration

Problem it solves: Critical Chain Project Management (CCPM) applies TOC to project scheduling.

Real-world application

A construction firm can use Critical Chain to shorten project durations by identifying the constraint resource shared across its projects and scheduling work around it.

In knowledge work, the constraint is often a policy (approval process, batch sizing, meeting overload) rather than a physical resource. Look for policy constraints — they're free to remove.

How to Apply Theory of Constraints: Step by Step

Before you start

  • →Understanding of the system's goal and how to measure throughput
  • →Process mapping to identify flow and potential constraints
  • →Authority to make cross-functional changes
Tools:Process flow diagramsThroughput measurement toolsQueue analysis
1

Identify the Constraint

Find the single resource or process step that limits overall throughput.

Tips

  • ✓Look for the step with the longest queue in front of it

Common mistakes

  • ✗Identifying multiple constraints — by definition, there can be only one at a time
2

Exploit the Constraint

Maximize the constraint's output without new investment.

Tips

  • ✓Ensure the constraint never sits idle — eliminate downtime, breaks, and rework

Common mistakes

  • ✗Jumping to Elevate (buying more capacity) before Exploiting what you have
3

Subordinate Everything Else

Align all other steps to support the constraint.

Tips

  • ✓Non-constraints should pace themselves to the constraint — faster is not better

Common mistakes

  • ✗Optimizing non-constraints, which just creates more inventory and confusion
4

Elevate the Constraint

Invest to increase the constraint's capacity.

Tips

  • ✓Only invest after Exploit and Subordinate — you may not need to

Common mistakes

  • ✗Investing before trying low-cost improvements first
5

Repeat

Find the new constraint and repeat. Don't let inertia become the constraint.

Tips

  • ✓When you break a constraint, the system changes — reassess everything

Common mistakes

  • ✗Continuing to focus on the old constraint after it's been elevated

Value & Outcomes

Primary benefit

Focuses improvement efforts on the one point that will actually increase system throughput.

Additional benefits

  • ✓Prevents wasted effort on non-constraint improvements
  • ✓Provides immediate results through exploitation before investment

What you'll learn

  • →How to identify the constraint in any system
  • →How to maximize system throughput with focused improvement

Typical outcomes

Significant throughput improvementReduced work-in-process inventoryFaster cycle times

Best Practices

📋 Preparation

  • •Map the full process flow
  • •Measure throughput at each step

🚀 Execution

  • •Always try Exploit before Elevate
  • •Subordinate non-constraints even if it means they're underutilized

🔄 Follow-Up

  • •Monitor for constraint shifts
  • •Don't let policy constraints build up again

💎 Pro Tips

  • •In most organizations, the real constraint is a management policy, not a physical resource

Limitations & Pitfalls

⚡

Focuses on one constraint at a time — may miss systemic issues

Mitigation: Combine with Lean for broader waste elimination

⚡

Assumes a linear process — less applicable to complex, networked systems

Mitigation: Adapt for knowledge work by focusing on policy constraints

Where this comes fromEliyahu M. Goldratt, in The Goal (1984).

More Management Frameworks

Other frameworks in the Stratrix library.

More from Stratrix

Ask the Analyst

Three questions a month are free.

All Access

Every Casebook, three Strategy Packs a seat each year and the Analyst, for teams that face these decisions all year.

$1,999 a year · $499 a seatWhat is included →

New analyses, by email

The defining moves in business, checked against the record, as they publish.

See Theory of Constraints in the wild.

Follow Theory of Constraints across the companies and lenses where it actually shaped the strategy — the decision, the rationale, and how it played out.