Theory of Constraints (TOC)

A cyclical process for ongoing improvement:

• 1. IDENTIFY the system's constraint.
• 2. EXPLOIT the constraint (make quick improvements using existing resources).
• 3. SUBORDINATE everything else to the above decision (align the whole system to support the constraint's maximum output).
• 4. ELEVATE the constraint (if more capacity is still needed, make major changes, often requiring capital expenditure).
• 5. PREVENT INERTIA (return to Step 1; do not let the constraint become a policy).

Example: If a specific machine is the bottleneck, non-bottleneck machines should not produce more than the bottleneck can process, preventing excess work-in-progress inventory.

A simplified management accounting methodology that replaces traditional cost accounting for decision-making. It focuses on three core metrics:

• Throughput (T): The rate at which the system generates money through sales (not just production).
• Investment (I): All the money tied up in the system to purchase things it intends to sell (inventory, equipment).
• Operating Expense (OE): All the money the system spends turning Investment into Throughput.

Decisions are evaluated based on their impact on T, I, and OE, with the primary goal being to increase Throughput while reducing Investment and Operating Expense.

The logistical application of TOC for production scheduling, particularly in manufacturing. It synchronizes the flow of materials to the constraint:

• Drum: The constraint or bottleneck resource that sets the pace for the entire system.
• Buffer: A time-based inventory buffer placed directly in front of the constraint to protect it from upstream disruptions (starvation).
• Rope: A communication mechanism from the constraint back to the release of raw materials, ensuring that work is released only at the rate the constraint can consume it.

This method prevents the accumulation of excess work-in-progress and reduces lead times.

A suite of logic-based cause-and-effect tools used to analyze complex systems and verbalize common-sense solutions. Key tools include:

• Current Reality Tree (CRT): Identifies the root cause of multiple undesirable effects.
• Evaporating Cloud (Conflict Resolution Diagram): Surfaces and challenges the hidden assumptions behind a core conflict to find a win-win solution.
• Future Reality Tree (FRT): Verifies that a proposed injection (solution) will logically lead to desired effects without creating new negative branches.
• Prerequisite Tree (PRT): Identifies the obstacles blocking the implementation of an injection and the intermediate objectives to overcome them.

A logical structure analysis used to classify production environments based on their dominant product flow, which dictates where to strategically place the constraint and control points:

• V-Plant: One raw material diverges into many unique final products. The constraint is typically at the raw material release.
• A-Plant: Many raw materials converge into one unique final product (like an airplane). The constraint is typically at the final assembly.
• T-Plant: Many similar final products are assembled from a limited number of common components. The constraint is typically in the fabrication of the common parts.
• I-Plant: A straight-line, continuous flow process (like a chemical plant). The constraint is a fixed physical step in the line.

The foundational premise of TOC is that the goal of a for-profit organization is to make money now and in the future. All other objectives, like efficiency, quality, or market share, are merely necessary conditions for achieving the goal, not the goal itself.

This principle forces a singular focus on metrics that directly impact financial performance:

• Net Profit (absolute measure)
• Return on Investment (relative measure)
• Cash Flow (survival measure)

Any proposed action or local optimization that does not positively impact these global metrics is considered a misalignment.

The core prescriptive process of TOC for continuous improvement:

• 1. Identify the system's constraint (the bottleneck).
• 2. Exploit the constraint by making quick, low-cost improvements to maximize its throughput.
• 3. Subordinate everything else to the decision made in step two; non-constraints must pace themselves to the constraint.
• 4. Elevate the constraint by adding capacity if it remains the limiting factor.
• 5. Prevent Inertia by returning to step one if the constraint has been broken.

A scheduling and execution mechanism derived from TOC for manufacturing environments:

• Drum: The constraint's production schedule, which sets the beat for the entire system.
• Buffer: A time-based inventory shield placed before the constraint to protect it from upstream disruptions.
• Rope: A communication signal that limits the release of raw materials into the system to match the constraint's consumption rate, preventing excess work-in-progress.

A management accounting methodology that replaces traditional cost accounting to align financial decisions with TOC principles. It focuses on three core metrics:

• Throughput (T): The rate at which the system generates money through sales.
• Investment (I): All the money tied up in the system to purchase things it intends to sell.
• Operating Expense (OE): All the money the system spends turning Investment into Throughput. Decisions are evaluated based on their impact on T, I, and OE, not local cost allocations.

Constraints are not always physical bottlenecks. They can be:

• Physical: A specific machine, resource, or material shortage with finite capacity.
• Policy: A formal or informal rule, procedure, or metric that limits performance (e.g., a batch-size rule or a local efficiency KPI).
• Market: Insufficient customer demand to consume the system's capacity.
• Paradigm: A deeply held belief or mindset that prevents the organization from seeing a better way. Policy constraints are the most common and often the hardest to identify.

An application of TOC to project management that addresses task duration inflation and multi-tasking:

• Replaces individual task safety buffers with a single project buffer at the end of the critical chain.
• Uses feeding buffers to protect the critical chain from non-critical path delays.
• Prioritizes tasks based on the health of the project buffer, not arbitrary deadlines, enabling aggressive but achievable schedules.

The real-time monitoring and control system used in DBR and CCPM. Buffers are divided into three zones:

• Green Zone: No action required; the system is operating as planned.
• Yellow Zone: Plan for potential intervention; investigate the cause of the penetration.
• Red Zone: Immediate action is required to expedite work and prevent the buffer from being fully consumed. This provides a priority signal for management attention, focusing efforts where they are most needed.