methodatlas
Method guideSystems Thinking

Theory of Constraints Thinking Process

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityHigh
Time0.5-3 Tage
Participants4-10
FormatWorkshop
MaturityCanonical
Plan Theory of Constraints Thinking Process
01

Prerequisite

What needs to be finished first

Complete firstClear boundary

Set system boundary and collect 5–10 concrete undesirable effects with evidence.

Without a boundary, cases, periods, or variables become mixed.
Complete firstEvidence access

UDEs, Current Reality Tree, Evaporating Cloud, Future Reality Tree, negative branches, and implementation trees

Missing sources remain visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

UDEs, Current Reality Tree, Evaporating Cloud, Future Reality Tree, negative branches, and implementation trees

People / roles

TP facilitator · problem owner · domain perspectives · injection owner

Pre-read

Set system boundary and collect 5–10 concrete undesirable effects with evidence.

Time needed

Several workshops over one to four weeks.

Setup

Prepare a workspace with UDEs · Conflict · Injection · Future · Implement; separate example from live data.

03

Core question

The one question this method answers

What to change, what to change to, and how to cause change when undesirable effects are causally connected?

04

Flow

Phases with goal, actions, output and pitfall

Undesirable Effects are gathered first and condensed into a Current Reality Tree. The team then uses Conflict, Future Reality, and Prerequisite logic until a viable breakthrough path becomes visible. The method closes with concrete implementation assumptions and friction points.

Theory of Constraints Thinking Process · working structure

Fictional example

Fictional values show the actual method fields.

Current Reality Tree

Collect concrete undesirable effects and connect them causally in a Current Reality Tree.

Long wait, overload, express conflicts; shared core: unstructured capacity promises.

Core cloud

Model core conflict as an Evaporating Cloud with needs and assumptions.

Need B fast commitment; Need C stable warehouse; D express anytime vs D′ capacity-bound slots.

Injection

Challenge assumptions and formulate an injection that dissolves conflict.

Capacity-visible express windows instead of anytime promise.

Future Reality Tree

Develop injection into desired effects in an FRT and test negative branches.

Visible capacity → realistic slots → fewer peaks; NBR: emergencies lose access → reserved emergency window.

Implementation tree

Translate obstacles, intermediate objectives, and actions into prerequisite/transition logic.

Obstacle no live capacity → hourly feed → Data owner, pilot 4 Nov.

All values are fictional.

Reference · original teaching example

  1. 1

    UDEs

    Current Reality Tree

    Goal

    CRT: Collect concrete undesirable effects and connect them causally in a Current Reality Tree.

    Inputs for this step

    • Set system boundary and collect 5–10 concrete undesirable effects with evidence.
    • UDEs, Current Reality Tree, Evaporating Cloud, Future Reality Tree, negative branches, and implementation trees

    Actions

    • Collect concrete undesirable effects and connect them causally in a Current Reality Tree.

    Output

    Current Reality Tree

    Collect concrete undesirable effects and connect them causally in a Current Reality Tree.

    Quality check

    Are UDEs observable and causal links logically checked?

    Pitfall

    Vague problems are linked with arrows. Operationalise UDEs and read every link as if-then.

    Timing: 90–180 minutes

  2. 2

    Conflict

    Core cloud

    Goal

    Core cloud: Model core conflict as an Evaporating Cloud with needs and assumptions.

    Inputs for this step

    • CRT

    Actions

    • Model core conflict as an Evaporating Cloud with needs and assumptions.

    Output

    Core cloud

    Model core conflict as an Evaporating Cloud with needs and assumptions.

    Quality check

    Are goal, needs, and prerequisites logically distinct?

    Pitfall

    Positions replace needs. Ask which necessary need lies beneath each demand.

    Timing: 60–120 minutes

  3. 3

    Injection

    Injection

    Goal

    Injection: Challenge assumptions and formulate an injection that dissolves conflict.

    Inputs for this step

    • Core cloud

    Actions

    • Challenge assumptions and formulate an injection that dissolves conflict.

    Output

    Injection

    Challenge assumptions and formulate an injection that dissolves conflict.

    Quality check

    Does it break a named assumption without sacrificing goal or need?

    Pitfall

    A compromise halves both demands. Choose an assumption and explain the win-win mechanism.

    Timing: 45–90 minutes

  4. 4

    Future

    Future Reality Tree

    Goal

    FRT: Develop injection into desired effects in an FRT and test negative branches.

    Inputs for this step

    • Injection

    Actions

    • Develop injection into desired effects in an FRT and test negative branches.

    Output

    Future Reality Tree

    Develop injection into desired effects in an FRT and test negative branches.

    Quality check

    Are effects causal, sufficient, and checked for side effects?

    Pitfall

    A wish list replaces causal logic. Test every arrow and treat negative branches with additions.

    Timing: 90–180 minutes

  5. 5

    Implement

    Implementation tree

    Goal

    Implementation tree: Translate obstacles, intermediate objectives, and actions into prerequisite/transition logic.

    Inputs for this step

    • FRT

    Actions

    • Translate obstacles, intermediate objectives, and actions into prerequisite/transition logic.

    Output

    Implementation tree

    Translate obstacles, intermediate objectives, and actions into prerequisite/transition logic.

    Quality check

    Does each obstacle have an objective, owner, and evidence?

    Pitfall

    Work ends with the FRT. Make obstacles explicit and sequence reviewed steps.

    Timing: 90–180 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

TOC Thinking Process · Logic TreesConnect undesirable effects, core conflicts, future logic, and implementation obstacles into a robust change path
TOC Thinking ProcessThe visual shows the TOC guiding questions what to change, what to change to, and how to cause the change with Current Reality Tree, Evaporating Cloud, Future Reality Tree, and Prerequisite Tree.Move from undesirable effects to a viable change pathThe TOC Thinking Process connects problem logic, conflict resolution, future logic, and implementation obstacles in one sequence.UDEUDEUDEcheck logic, not only collect ideascore conflict becomes change logicimplementation obstacles become visible earlyWhat to change?understand UDEs and core causeWhat to change to?resolve conflict and test future logicHow to cause change?derive obstacles and actionsCurrent Reality Treecondense undesirable effects into coreproblemEvaporating Cloudmake core conflict and assumptionsvisibleFuture Reality Treetest injections and desired effectsPrerequisite Treetranslate obstacles into nextactions
Form

TOC TP logic package containing CRT, core conflict, injection, FRT, and implementation logic.

Versioning / ownership

Record date, owner, source state, and review date; preserve prior versions.

Tool alternatives
  • Current Reality Tree
  • Evaporating Cloud
  • Future Reality/Prerequisite/Transition Trees

theory-of-constraints-thinking-process-working-template.md

Set subject, evidence, roles, flow, and review.

Theory of Constraints Thinking Process: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Whole initiative Time: Several workshops over one to four weeks.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: UDEs, Current Reality Tree, Evaporating Cloud, Future Reality Tree, negative branches, and implementation trees
  • Roles: TP facilitator · problem owner · domain perspectives · injection owner
  • Advance information: Set system boundary and collect 5–10 concrete undesirable effects with evidence.
  • Overall time needed: Several workshops over one to four weeks.
  • Setup: Prepare a workspace with UDEs · Conflict · Injection · Future · Implement; separate example from live data.

Prepare for the work steps

UDEs: Current Reality Tree

  • Set system boundary and collect 5–10 concrete undesirable effects with evidence.
  • UDEs, Current Reality Tree, Evaporating Cloud, Future Reality Tree, negative branches, and implementation trees

Conflict: Core cloud

  • CRT

Injection: Injection

  • Core cloud

Future: Future Reality Tree

  • Injection

Implement: Implementation tree

  • FRT

Theory of Constraints Thinking Process · working structure

Current Reality Tree

Collect concrete undesirable effects and connect them causally in a Current Reality Tree.

...

Core cloud

Model core conflict as an Evaporating Cloud with needs and assumptions.

...

Injection

Challenge assumptions and formulate an injection that dissolves conflict.

...

Future Reality Tree

Develop injection into desired effects in an FRT and test negative branches.

...

Implementation tree

Translate obstacles, intermediate objectives, and actions into prerequisite/transition logic.

...

The blank worksheet contains prompts only.

Reference · original teaching example

UDEs: Current Reality Tree

Expected artifact: Current Reality Tree

Collect concrete undesirable effects and connect them causally in a Current Reality Tree.

Entry:

...

  • Are UDEs observable and causal links logically checked?

Conflict: Core cloud

Expected artifact: Core cloud

Model core conflict as an Evaporating Cloud with needs and assumptions.

Entry:

...

  • Are goal, needs, and prerequisites logically distinct?

Injection: Injection

Expected artifact: Injection

Challenge assumptions and formulate an injection that dissolves conflict.

Entry:

...

  • Does it break a named assumption without sacrificing goal or need?

Future: Future Reality Tree

Expected artifact: Future Reality Tree

Develop injection into desired effects in an FRT and test negative branches.

Entry:

...

  • Are effects causal, sufficient, and checked for side effects?

Implement: Implementation tree

Expected artifact: Implementation tree

Translate obstacles, intermediate objectives, and actions into prerequisite/transition logic.

Entry:

...

  • Does each obstacle have an objective, owner, and evidence?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/theory-of-constraints-thinking-process/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

theory-of-constraints-thinking-process-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Theory of Constraints Thinking Process · working structure

Current Reality Tree

Long wait, overload, express conflicts; shared core: unstructured capacity promises.

Core cloud

Need B fast commitment; Need C stable warehouse; D express anytime vs D′ capacity-bound slots.

Injection

Capacity-visible express windows instead of anytime promise.

Future Reality Tree

Visible capacity → realistic slots → fewer peaks; NBR: emergencies lose access → reserved emergency window.

Implementation tree

Obstacle no live capacity → hourly feed → Data owner, pilot 4 Nov.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Current Reality TreeVague problems are linked with arrows.View in phase
  2. Core cloudPositions replace needs.View in phase
  3. InjectionA compromise halves both demands.View in phase
  4. Future Reality TreeA wish list replaces causal logic.View in phase
  5. Implementation treeWork ends with the FRT.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop UDEs: Are UDEs observable and causal links logically checked?
Stop Conflict: Are goal, needs, and prerequisites logically distinct?
Stop Injection: Does it break a named assumption without sacrificing goal or need?
Stop Future: Are effects causal, sufficient, and checked for side effects?
Stop Implement: Does each obstacle have an objective, owner, and evidence?

Method after Eliyahu M. Goldratt. Curated with 1 sources.

Sources: Theory of Constraints Thinking Process

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log

Turns the transition tree's obstacles and intermediate goals into a running action and risk log.

Paper illustration for Communication Plan
Delivery
Communication Plan

Communicates the planned system change specifically to affected stakeholders.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods