> ## Documentation Index
> Fetch the complete documentation index at: https://meta.niceshare.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Theory of Constraints (TOC)

> Theory of Constraints is a systems method that improves results by identifying and managing the current bottleneck. Learn origin, five focusing steps, applications, and limits.

<Info>
  **Category**: Methods<br />
  **Type**: Systems Improvement and Flow Management Method<br />
  **Origin**: Eliyahu M. Goldratt, formalized in the 1980s through OPT and *The Goal*<br />
  **Also known as**: TOC, Bottleneck Management, Constraint-Based Improvement
</Info>

<Note>
  **Quick Answer** — Theory of Constraints (TOC) is a method for improving system performance by focusing on the one constraint that currently limits total output. It was developed by Eliyahu Goldratt and popularized through *The Goal* and later TOC tools such as the Five Focusing Steps and Drum-Buffer-Rope. Its key insight is that optimizing non-constraints rarely improves total flow; leverage comes from managing the bottleneck.
</Note>

## What is Theory of Constraints (TOC)?

Theory of Constraints is a management method that treats every complex system as constraint-limited and improves performance by systematically managing that limiting point.

> TOC asks one operational question first: "What is the current bottleneck, and how do we increase total flow through it?"

Instead of spreading effort across many local improvements, TOC concentrates attention on one leverage point at a time. It pairs well with `/methods/lean-methodology`, `/methods/kanban-method`, and `/methods/pdca-cycle` when teams need end-to-end flow improvement.

### Theory of Constraints (TOC) in 3 Depths

* **Beginner**: Find the current bottleneck and stop overloading upstream steps.
* **Practitioner**: Apply the Five Focusing Steps and use buffer logic to protect bottleneck flow.
* **Advanced**: Combine TOC with policy-level diagnosis to remove structural constraints, not only physical ones.

## Origin

TOC emerged from Eliyahu Goldratt's work on production scheduling and the Optimized Production Technology (OPT) approach in the late 1970s and early 1980s. The method became widely known through Goldratt and Cox's 1984 novel *The Goal*, which translated plant-flow logic into a practical managerial narrative.

Over time, TOC expanded beyond manufacturing into project management, services, and healthcare. Core tools include the Five Focusing Steps, Drum-Buffer-Rope scheduling, and thinking processes for policy and conflict constraints.

## Key Points

TOC succeeds when teams prioritize global flow over local utilization metrics.

<Steps>
  <Step title="Identify the system constraint">
    Determine which resource, policy, or decision point currently caps throughput. Without this diagnosis, improvement work fragments into low-impact activity.
  </Step>

  <Step title="Exploit the constraint first">
    Increase effective output from the bottleneck using scheduling discipline, reduced downtime, and better work quality before adding capacity.
  </Step>

  <Step title="Subordinate non-constraints">
    Align upstream and downstream work to the bottleneck pace so inventory and queues do not grow uncontrollably.
  </Step>

  <Step title="Elevate and repeat">
    Add capacity or redesign policy only after exploitation gains are exhausted, then reassess because a new constraint will emerge.
  </Step>
</Steps>

## Applications

TOC is most useful when teams experience persistent delays, overload, or unstable delivery performance.

<CardGroup cols={2}>
  <Card title="Manufacturing Flow Control">
    Stabilize throughput by synchronizing release schedules with bottleneck capacity.
  </Card>

  <Card title="Service Operations">
    Reduce waiting time by redesigning intake and prioritization around constrained resources.
  </Card>

  <Card title="Project Portfolio Management">
    Prevent multitasking overload by protecting critical chain resources.
  </Card>

  <Card title="Healthcare Capacity Planning">
    Improve patient flow by managing diagnostic or specialist bottlenecks explicitly.
  </Card>
</CardGroup>

## Case Study

A healthcare TOC action-research case in ophthalmology reported a **64% increase in imaging throughput** within a few weeks after applying TOC focusing steps, Drum-Buffer-Rope logic, and buffer management in the service workflow.

The measurable result came from constraint-centered redesign rather than broad optimization: teams identified one limiting step, protected it from starvation and variability, and aligned surrounding activities to that pace. This case illustrates TOC's transferability beyond factory settings.

## Boundaries and Failure Modes

TOC can fail when organizations mistake every delay for "the bottleneck" and keep changing focus weekly without evidence. Another failure mode is local KPI pressure that rewards high utilization on non-constraints, causing excess work-in-progress.

Two boundary conditions matter. First, TOC requires reliable system-level metrics; weak measurement makes constraint diagnosis unstable. Second, some constraints are policy or incentive based, not physical capacity. A common misuse is adding headcount before exploiting and subordinating existing flow.

## Common Misconceptions

TOC is often simplified into bottleneck firefighting, which misses its systems logic.

<AccordionGroup>
  <Accordion title="TOC is only for factories">
    TOC has been used in services, software delivery, and healthcare where flow constraints are just as real.
  </Accordion>

  <Accordion title="Every busy resource is a constraint">
    A busy step is not necessarily the system limiter; the true constraint is what caps end-to-end throughput.
  </Accordion>

  <Accordion title="Fixing one bottleneck solves the system permanently">
    Once one constraint is elevated, another emerges. TOC is a repeating improvement cycle.
  </Accordion>
</AccordionGroup>

## Related Concepts

These methods strengthen TOC execution from diagnosis to operational follow-through.

<CardGroup cols={3}>
  <Card title="Lean Methodology" href="/methods/lean-methodology">
    Remove waste while protecting the flow around the current constraint.
  </Card>

  <Card title="Kanban Method" href="/methods/kanban-method">
    Visualize queue pressure and limit work-in-progress around constrained stages.
  </Card>

  <Card title="PDCA Cycle" href="/methods/pdca-cycle">
    Run iterative improvement loops after each constraint shift.
  </Card>

  <Card title="Root Cause Analysis" href="/methods/root-cause-analysis">
    Distinguish symptom bottlenecks from deeper policy or process causes.
  </Card>
</CardGroup>

## One-Line Takeaway

<Tip>
  TOC improves whole-system results by managing the one thing that limits flow right now, then repeating the cycle as constraints move.
</Tip>