Session Brief: Future Reality Tree

Goal

Artifact: Future Reality Tree

Working Question

Do the planned changes plausibly lead to desired effects, and which negative branches must be protected against?

Context

Scope, occasion, known facts, relevant constraints, existing options or events, and desired meeting outcome.

Setup

• Format: Method session
• Duration: 2-4 h
• Mode: Workshop
• Participants: Facilitator; domain experts from the affected area; an owner for outcome and follow-through; a named decider for decisions.
• Owner: Facilitator
• Participation mode: Team round, shared work and alignment
• Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Future Reality Tree. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Workspace or document for a cause-and-effect tree; existing notes, data, decisions, and assumptions; markers for uncertainty, owners, and next steps.

Preparation

Prepare an empty cause-and-effect tree template. Make scope and working question visible at the top. Mark each assumption as assumption, not fact.

Agenda

1. Fix scope (10-20 min) Owner: Facilitator Action: Define occasion, goal, and boundaries of analysis. Collect non-fitting topics on a parking lot. Hint: A tighter scope creates better outcomes than a broad but fuzzy all-rounding approach. Output: Future Reality Tree

2. Collect raw material (20-40 min) Owner: Facilitator Action: Gather and surface facts, events, options, constraints, or assumptions. Hint: Keep facts and interpretations separated. Mark uncertain points instead of smoothing them over. Output: Negative Branches

3. Build structure (30-60 min) Owner: Facilitator Action: Fill in the cause-and-effect tree step by step, clarify relationships between elements, and make contradictions visible. Hint: Do not evaluate too early. Stabilize structure first, then draw conclusions. Output: Assumption List

4. Validate and consolidate (20-40 min) Owner: Facilitator Action: Mark gaps, weak assumptions, counterexamples, and critical paths. Check readability of output. Hint: If no one can explain the logic in two minutes, the artifact is not ready. Output: Improved Injections

5. Define next steps (15-20 min) Owner: Owner Action: Document decision, experiment, test, action, or follow-up with owner and date. Hint: A strong artifact with no next action remains knowledge work without impact. Output: Future Reality Tree

6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Future Reality Tree

Closeout

• Update result artifact: Future Reality Tree
• Define location, version, and review recipients.
• Define owner, next step, and review date.

Future Reality Tree: Future Reality Tree

Working Question

Do the planned changes plausibly lead to desired effects, and which negative branches must be protected against?

Context

Scope, occasion, known facts, relevant constraints, existing options or events, and desired meeting outcome.

Participants

• Owner: Facilitator
• Participants: Facilitator; domain experts from the affected area; an owner for outcome and follow-through; a named decider for decisions.

Input

Workspace or document for a cause-and-effect tree; existing notes, data, decisions, and assumptions; markers for uncertainty, owners, and next steps.

Template

Future Reality Tree Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

• Area 1:
• Area 2:
• Area 3:
• Relationships / patterns:

Output artifacts

• Future Reality Tree:
• Negative Branches:
• Assumption List:
• Improved Injections:

Open questions

• ...

Next step

Owner, date, and success signal.

Completion Check

• Future Reality Tree is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

• Review result
• Mark open questions
• Schedule review or decision