methodatlas
Method guideSystems Thinking

Future Reality Tree

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

ComplexityHigh
Time2-4 h
Participants3-8
FormatWorkshop
MaturityEstablished
Plan Future Reality Tree
01

Prerequisite

What needs to be finished first

Complete firstClear boundary

Provide one clear injection and affected UDEs; set system boundary and horizon.

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

Injection, UDEs, desired effects, FRT logic, Categories of Legitimate Reservation, and negative-branch log

Missing sources remain visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

Injection, UDEs, desired effects, FRT logic, Categories of Legitimate Reservation, and negative-branch log

People / roles

TP facilitator · injection owner · domain perspectives · affected side-effect perspectives

Pre-read

Provide one clear injection and affected UDEs; set system boundary and horizon.

Time needed

120–240 minutes plus domain review.

Setup

Prepare a workspace with Outcomes · Injection · Logic · Side effects · Protect; separate example from live data.

03

Core question

The one question this method answers

Will the proposed injection causally produce desired effects, and which negative branches need protection before implementation?

04

Flow

Phases with goal, actions, output and pitfall

Klare Verbesserungen werden als Ausgangspunkt für Wirkungsketten in die Zukunft genutzt. Zwischenzustände, mögliche Nebenwirkungen und notwendige Verstärkungen ergänzen den Pfad, bis er als überprüfbare Logik von Intervention zu Ergebnis lesbar ist.

Future Reality Tree · working structure

Fictional example

Fictional values show the actual method fields.

Desired effects

Translate UDEs into concrete Desired Effects with observable success.

DE1 p80 wait <12; DE2 warehouse load without peaks; DE3 emergencies retain access.

Starting injection

Enter injection as a mechanism with validity boundary.

Capacity-visible express windows without a separate emergency rule.

Causal tree

Build intermediate effects from injection to DEs with required conditions.

Visible capacity + slot rule → realistic booking → fewer peaks → DE1/DE2.

Negative branches

Develop negative branches from affected perspectives and assess probability/severity.

Reserved windows → fewer free express places → emergency risk, unless emergency slot exists.

Reviewed FRT

Add injections and recheck the complete tree for sufficiency and conflicts.

Emergency slot plus release rule preserves DE3; owner and measure set before pilot.

All values are fictional.

Reference · original teaching example

  1. 1

    Outcomes

    Desired effects

    Goal

    Desired effects: Translate UDEs into concrete Desired Effects with observable success.

    Inputs for this step

    • Provide one clear injection and affected UDEs; set system boundary and horizon.
    • Injection, UDEs, desired effects, FRT logic, Categories of Legitimate Reservation, and negative-branch log

    Actions

    • Translate UDEs into concrete Desired Effects with observable success.

    Output

    Desired effects

    Translate UDEs into concrete Desired Effects with observable success.

    Quality check

    Is each DE a positive observable future rather than absence?

    Pitfall

    No more problems is untestable. Phrase a positive effect with measure.

    Timing: 20–30 minutes

  2. 2

    Injection

    Starting injection

    Goal

    Starting injection: Enter injection as a mechanism with validity boundary.

    Inputs for this step

    • Desired effects

    Actions

    • Enter injection as a mechanism with validity boundary.

    Output

    Starting injection

    Enter injection as a mechanism with validity boundary.

    Quality check

    Is it clear which cause or assumption changes?

    Pitfall

    A generic initiative replaces the mechanism. Name concrete mechanism and affected assumption.

    Timing: 15–25 minutes

  3. 3

    Logic

    Causal tree

    Goal

    Causal tree: Build intermediate effects from injection to DEs with required conditions.

    Inputs for this step

    • Starting injection

    Actions

    • Build intermediate effects from injection to DEs with required conditions.

    Output

    Causal tree

    Build intermediate effects from injection to DEs with required conditions.

    Quality check

    Does every arrow pass if-then and expose missing conditions?

    Pitfall

    Large logical jumps remain unexplained. Add intermediate steps or AND conditions.

    Timing: 60–120 minutes

  4. 4

    Side effects

    Negative branches

    Goal

    Negative branches: Develop negative branches from affected perspectives and assess probability/severity.

    Inputs for this step

    • Causal tree

    Actions

    • Develop negative branches from affected perspectives and assess probability/severity.

    Output

    Negative branches

    Develop negative branches from affected perspectives and assess probability/severity.

    Quality check

    Are plausible side effects modelled causally?

    Pitfall

    Critique is dismissed as resistance. Develop the branch to an undesirable effect.

    Timing: 30–60 minutes

  5. 5

    Protect

    Reviewed FRT

    Goal

    Reviewed FRT: Add injections and recheck the complete tree for sufficiency and conflicts.

    Inputs for this step

    • Negative branches

    Actions

    • Add injections and recheck the complete tree for sufficiency and conflicts.

    Output

    Reviewed FRT

    Add injections and recheck the complete tree for sufficiency and conflicts.

    Quality check

    Do additions treat side effects without destroying main effect?

    Pitfall

    Side effect is merely noted. Insert preventive injection and reread full path.

    Timing: 30–45 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Future Reality Tree · TOCCheck planned injections forward against desired effects, assumptions, and possible negative side effects
Future Reality TreeThe visual shows injections, expected intermediate effects, desired future effects, and a negative branch for checking side effects.Check solution assumptions forward for impact and side effectsA Future Reality Tree shows why planned injections should lead to desired effects and where the solution still needs safeguards.becauseif both worktestable assumptioncheck forward instead of only asserting solutionside effectsimprove the solutionInjection Anew rule or capabilityInjection Bbreak conflict assumptionIntermediate effectprerequisite is metDesired effectmeasurable improvementFuture statestable desired realityNegative Branchcheck side effect early
Form

Future Reality Tree with injection, intermediate effects, DEs, checked sufficiency, and treated negative branches.

Versioning / ownership

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

Tool alternatives
  • FRT canvas
  • Logic checks/CLR
  • Negative-branch register

future-reality-tree-working-template.md

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

Future Reality Tree: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 120–240 minutes plus domain review.

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

Preparation for this scope

Method setup

  • Materials: Injection, UDEs, desired effects, FRT logic, Categories of Legitimate Reservation, and negative-branch log
  • Roles: TP facilitator · injection owner · domain perspectives · affected side-effect perspectives
  • Advance information: Provide one clear injection and affected UDEs; set system boundary and horizon.
  • Overall time needed: 120–240 minutes plus domain review.
  • Setup: Prepare a workspace with Outcomes · Injection · Logic · Side effects · Protect; separate example from live data.

Prepare for the work steps

Outcomes: Desired effects

  • Provide one clear injection and affected UDEs; set system boundary and horizon.
  • Injection, UDEs, desired effects, FRT logic, Categories of Legitimate Reservation, and negative-branch log

Injection: Starting injection

  • Desired effects

Logic: Causal tree

  • Starting injection

Side effects: Negative branches

  • Causal tree

Protect: Reviewed FRT

  • Negative branches

Future Reality Tree · working structure

Desired effects

Translate UDEs into concrete Desired Effects with observable success.

...

Starting injection

Enter injection as a mechanism with validity boundary.

...

Causal tree

Build intermediate effects from injection to DEs with required conditions.

...

Negative branches

Develop negative branches from affected perspectives and assess probability/severity.

...

Reviewed FRT

Add injections and recheck the complete tree for sufficiency and conflicts.

...

The blank worksheet contains prompts only.

Reference · original teaching example

Outcomes: Desired effects

Expected artifact: Desired effects

Translate UDEs into concrete Desired Effects with observable success.

Entry:

...

  • Is each DE a positive observable future rather than absence?

Injection: Starting injection

Expected artifact: Starting injection

Enter injection as a mechanism with validity boundary.

Entry:

...

  • Is it clear which cause or assumption changes?

Logic: Causal tree

Expected artifact: Causal tree

Build intermediate effects from injection to DEs with required conditions.

Entry:

...

  • Does every arrow pass if-then and expose missing conditions?

Side effects: Negative branches

Expected artifact: Negative branches

Develop negative branches from affected perspectives and assess probability/severity.

Entry:

...

  • Are plausible side effects modelled causally?

Protect: Reviewed FRT

Expected artifact: Reviewed FRT

Add injections and recheck the complete tree for sufficiency and conflicts.

Entry:

...

  • Do additions treat side effects without destroying main effect?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/future-reality-tree/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.

future-reality-tree-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Future Reality Tree · working structure

Desired effects

DE1 p80 wait <12; DE2 warehouse load without peaks; DE3 emergencies retain access.

Starting injection

Capacity-visible express windows without a separate emergency rule.

Causal tree

Visible capacity + slot rule → realistic booking → fewer peaks → DE1/DE2.

Negative branches

Reserved windows → fewer free express places → emergency risk, unless emergency slot exists.

Reviewed FRT

Emergency slot plus release rule preserves DE3; owner and measure set before pilot.

07

Pitfalls

Recognize symptoms and steer against them

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

  1. Desired effectsNo more problems is untestable.View in phase
  2. Starting injectionA generic initiative replaces the mechanism.View in phase
  3. Causal treeLarge logical jumps remain unexplained.View in phase
  4. Negative branchesCritique is dismissed as resistance.View in phase
  5. Reviewed FRTSide effect is merely noted.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Outcomes: Is each DE a positive observable future rather than absence?
Stop Injection: Is it clear which cause or assumption changes?
Stop Logic: Does every arrow pass if-then and expose missing conditions?
Stop Side effects: Are plausible side effects modelled causally?
Stop Protect: Do additions treat side effects without destroying main effect?

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

Sources: Future Reality Tree

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 validated additional injections and negative branches into an implementation and risk log.

Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping

Links the validated change path to an implementable intervention program.

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