Theory of Constraints

Manufacturing flow and constraint management – a core visual of the Theory of Constraints

Meta Summary: A complete playbook on the Theory of Constraints (TOC) – covering foundational concepts, the five focusing steps, throughput accounting, thinking processes, implementation tools (Drum-Buffer-Rope, Critical Chain), and limitations. All information is sourced from free, publicly accessible references.

Table of Contents

• Chapter 1: Fundamentals of the Theory of Constraints
• Chapter 2: The Five Focusing Steps
• Chapter 3: Throughput Accounting and Performance Metrics
• Chapter 4: Thinking Processes and Logic Tools
• Chapter 5: Implementation Tools – Drum-Buffer-Rope and Critical Chain
• Chapter 6: Limitations and Common Criticisms
• Related Topics
• FAQ

Chapter 1: Fundamentals of the Theory of Constraints

Origins and Core Definition

The Theory of Constraints (TOC) is a management philosophy introduced by Dr. Eliyahu M. Goldratt in his 1984 novel The Goal. TOC asserts that any manageable system is limited by a small number of constraints – often just one. Improving non‑constraint parts does not significantly improve overall performance; only identifying and managing the constraint raises throughput toward the system’s goal (for a business, generating money).

TOC has been applied in manufacturing, supply chain, project management, healthcare, and software development. The core assumption: every system has at least one constraint – anything that prevents the system from achieving higher performance.

Types of Constraints

• Physical constraints: Equipment capacity, material shortages, labor skills, or physical space limits.
• Policy constraints: Outdated rules, measurement systems, or procedures that limit performance (e.g., batch size policies, compensation models).
• Market constraints: Insufficient customer demand that prevents selling more products or services.
• Paradigm constraints: Deeply held beliefs or mental models that block better solutions.
• Supplier constraints: Dependencies on vendors that create delivery or quality bottlenecks.

Source verification: The types of constraints are documented in open TOC literature (see references).

Chapter 2: The Five Focusing Steps

⬅ Back to Table of Contents

Step‑by‑Step Continuous Improvement Cycle

The five focusing steps provide a structured approach to manage and break constraints:

1. Identify the system’s constraint (the weakest link).
2. Exploit the constraint – make sure it is never idle; extract maximum output without major investment.
3. Subordinate everything else to the constraint – align non‑constraint resources to support the constraint’s pace.
4. Elevate the constraint – add more capacity (buy equipment, hire staff, change policy) to break the bottleneck.
5. Repeat – after the constraint is broken, go back to step 1; do not let inertia become the new constraint.

Illustrative example (generic, not a real case study): A small workshop has one welding robot that can process 40 units/day while other stations can handle 60 units/day. Exploit: ensure the robot never waits for materials. Subordinate: cut batch sizes upstream to prevent excess inventory. Elevate: add a second shift or a second robot. Repeat to find the next constraint.

Chapter 3: Throughput Accounting and Performance Metrics

TOC‑Specific Financial Metrics

Throughput Accounting replaces traditional cost accounting for decision‑making under TOC. It defines three primary measurements:

```

Throughput (T)
Rate at which the system generates money through sales (Revenue – Truly Variable Costs).

Inventory (I)
Money invested in things intended to be sold (raw materials, WIP, finished goods).

Operating Expense (OE)
Money spent to turn inventory into throughput (utilities, salaries, rent, depreciation).

Key derived metrics:

• Net Profit = T – OE
• Return on Investment (ROI) = (T – OE) / I
• Productivity = T / OE
• Inventory Turns = T / I

Unlike cost accounting, throughput accounting discourages building inventory to absorb overhead. It focuses local decisions on global system throughput.

```

Chapter 4: Thinking Processes and Logic Tools

⬅ Back to Table of Contents

TOC Logic Trees for Problem Solving

The Thinking Processes are a set of logic‑based tools to answer three questions: What to change? (Current Reality Tree), What to change to? (Evaporating Cloud + Future Reality Tree), and How to cause the change? (Prerequisite Tree + Transition Tree).

• Current Reality Tree (CRT): Identifies root causes (core problems) and undesirable effects using cause‑effect logic.
• Evaporating Cloud (Conflict Resolution Diagram): Surfaces hidden assumptions behind a conflict and finds a win‑win injection.
• Future Reality Tree (FRT): Tests proposed solutions by mapping positive outcomes and avoiding negative branches.
• Prerequisite Tree (PRT): Lists obstacles to implementation and intermediate objectives.
• Transition Tree (TT): Detailed action steps to achieve the objectives.

These tools are widely documented in free TOC resources (see references).

Chapter 5: Implementation Tools – Drum-Buffer-Rope and Critical Chain

Production and Project Management Schedules

Drum‑Buffer‑Rope (DBR): A production scheduling method for flow shops. The “drum” is the constraint’s pace, the “buffer” protects the constraint from disruptions, and the “rope” synchronizes material release. Simplified DBR (S‑DBR) removes the rope and uses a shipping buffer instead.

Critical Chain Project Management (CCPM): Applies TOC to project environments. It removes multi‑tasking, uses aggressive but estimated task durations with feeding buffers and a project buffer, and focuses on the critical chain (resource‑ and dependency‑constrained longest path). CCPM reduces project lead times and improves on‑time completion rates.

Implementation best practices: start with a pilot area, engage frontline operators, measure throughput weekly, and avoid shortcutting the five focusing steps.

Chapter 6: Limitations and Common Criticisms

Where TOC Has Challenges

• Single constraint assumption: TOC assumes one dominant constraint; complex systems may have interacting constraints that shift rapidly.
• Cultural resistance: Implementation requires deep organizational change and can face resistance from traditional accounting departments.
• Policy constraints are harder to identify: Unlike physical bottlenecks, policy constraints (e.g., outdated performance metrics) are invisible and require structured thinking processes to uncover.
• Not a complete substitute: TOC works best when combined with Lean and Six Sigma (e.g., using TOC to identify the constraint, then Lean to reduce waste around it).
• Risk of inertia: After elevating a constraint, organizations often fail to repeat the five steps, allowing a new constraint to appear elsewhere.

These limitations are acknowledged in peer‑reviewed and open source literature (see references).

Related Topics

• Lean Manufacturing and Just‑in‑Time (JIT)
• Six Sigma (DMAIC) and Variation Reduction
• Goldratt’s Thinking Processes (systematic problem solving)
• Throughput Accounting vs. Standard Costing
• Critical Chain Project Management (CCPM)
• Queuing Theory and Bottleneck Analysis
• Value Stream Mapping

FAQ

What is the main goal of the Theory of Constraints?

To increase throughput (the rate of generating goal units, e.g., money or completed projects) by systematically identifying and managing the system’s weakest link, while reducing inventory and operating expense.

How does TOC differ from Lean?

Lean focuses on eliminating waste (muda) and creating flow, while TOC focuses on removing constraints. TOC often uses buffers to protect the constraint, which may appear as “inventory” from a Lean perspective, but it is intentional to protect throughput. Many organizations combine both approaches.

Can TOC be applied in non‑manufacturing settings?

Yes. TOC is used in healthcare (reducing patient wait times), software development (limiting work‑in‑progress via Kanban/CCPM), project management (critical chain), sales (throughput‑based lead management), and supply chain (replenishment solutions).

What are the most common mistakes when implementing TOC?

Common pitfalls: jumping to “elevate” before fully exploiting and subordinating; not updating metrics to throughput accounting; failing to repeat the five steps after a constraint is broken; and ignoring policy constraints (e.g., incentive systems that reward local efficiencies).

References

• Wikipedia – Theory of Constraints (definition, five focusing steps, Goldratt)
• ACCA Global – Throughput accounting and the theory of constraints (five steps + metrics)
• TOCICO – About TOC (mission and fundamentals)
• PMI – Critical Chain Project Management (free article, no login required)
• Iowa State University CIRAS – TOC Thinking Processes (logic tools, open access)
• Wikipedia – Throughput accounting (T, I, OE definitions and formulas)
• Goldratt Consulting – Official approach to TOC (overview, no paywall)