Complete firstBounded subject
The scope and purpose of Futures Wheel are stated as a concrete question.
Without scope, futures wheel becomes arbitrary.
Method guideSystems Thinking
Futures Wheel
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityMedium
Time60-120 min
Participants3-10
FormatWorkshop + async
MaturityEstablished
01
Prerequisite
What needs to be finished first
Complete firstAccess to relevant perspectives
Precise change or trend, stakeholder and system knowledge, horizon and scenario boundary and domain decision makers are available.
Without these perspectives, central claims in futures wheel remain unsupported.
02
Preparation
What needs to be ready before start
Materials
Precise change or trend, stakeholder and system knowledge, horizon and scenario boundary, shared workspace, source links, and decision log.
People / roles
Foresight facilitator · diverse domain/stakeholder experts
Pre-read
Collect Precise change or trend, stakeholder and system knowledge, horizon and scenario boundary in advance and mark open assumptions.
Time needed
60–120 minutes
Setup
Prepare central event with causally linked first- to third-order consequence rings visibly and calibrate assessment terms before starting.
03
Core question
The one question this method answers
Which direct and indirect consequences might this change trigger for different actors?
04
Flow
Phases with goal, actions, output and pitfall
A futures wheel places a clear change in the centre, collects first-order consequences, and derives second- and third-order consequences. Links receive direction, horizon, and assumption.
Futures Wheel
Fictional causal chains
Two concrete causal chains from the central change to third order; every consequence names parent, mechanism, and uncertainty.
| Consequence node | Node | Parent node | Order | Consequence | Mechanism | Uncertainty/signpost |
|---|---|---|---|---|---|---|
| Consequence 1Test one real consequence with its causal parent. | A1: Logging cost | Provenance duty from 2028 | 1 | Logging and storage effort rises. | Every AI answer needs source and model evidence. | Medium; monitor draft technical standards. |
| Consequence 2Test one real consequence with its causal parent. | A2: Shared service | A1: Logging cost | 2 | Small providers pool provenance infrastructure. | Fixed cost exceeds own scale advantage. | High; first managed services are a signpost. |
| Consequence 3Test one real consequence with its causal parent. | A3: Market concentration | A2: Shared service | 3 | A few provenance providers become critical dependencies. | Shared demand concentrates data and switching cost. | High; monitor provider shares and portability standards. |
| Consequence 4Test one real consequence with its causal parent. | B1: Answers blocked | Provenance duty from 2028 | 1 | Unsupported AI answers are stopped before release. | A compliance gate checks the complete source chain. | Medium; monitor enforcement guidance. |
| Consequence 5Test one real consequence with its causal parent. | B2: Longer response time | B1: Answers blocked | 2 | Users wait more often for verified answers. | Retrieval and source checks add processing steps. | Medium; measure P95 latency in pilot. |
| Consequence 6Test one real consequence with its causal parent. | B3: Auditability decides | B2: Longer response time | 3 | Buyers accept latency only for visibly higher trust. | Procurement weighs traceable provenance against speed. | High; monitor tender criteria and win/loss data. |
1. Node
- Consequence 1
- A1: Logging cost
- Consequence 2
- A2: Shared service
- Consequence 3
- A3: Market concentration
- Consequence 4
- B1: Answers blocked
- Consequence 5
- B2: Longer response time
- Consequence 6
- B3: Auditability decides
2. Parent node
- Consequence 1
- Provenance duty from 2028
- Consequence 2
- A1: Logging cost
- Consequence 3
- A2: Shared service
- Consequence 4
- Provenance duty from 2028
- Consequence 5
- B1: Answers blocked
- Consequence 6
- B2: Longer response time
3. Order
- Consequence 1
- 1
- Consequence 2
- 2
- Consequence 3
- 3
- Consequence 4
- 1
- Consequence 5
- 2
- Consequence 6
- 3
4. Consequence
- Consequence 1
- Logging and storage effort rises.
- Consequence 2
- Small providers pool provenance infrastructure.
- Consequence 3
- A few provenance providers become critical dependencies.
- Consequence 4
- Unsupported AI answers are stopped before release.
- Consequence 5
- Users wait more often for verified answers.
- Consequence 6
- Buyers accept latency only for visibly higher trust.
5. Mechanism
- Consequence 1
- Every AI answer needs source and model evidence.
- Consequence 2
- Fixed cost exceeds own scale advantage.
- Consequence 3
- Shared demand concentrates data and switching cost.
- Consequence 4
- A compliance gate checks the complete source chain.
- Consequence 5
- Retrieval and source checks add processing steps.
- Consequence 6
- Procurement weighs traceable provenance against speed.
6. Uncertainty/signpost
- Consequence 1
- Medium; monitor draft technical standards.
- Consequence 2
- High; first managed services are a signpost.
- Consequence 3
- High; monitor provider shares and portability standards.
- Consequence 4
- Medium; monitor enforcement guidance.
- Consequence 5
- Medium; measure P95 latency in pilot.
- Consequence 6
- High; monitor tender criteria and win/loss data.
Order means distance from the central change, not importance.
- 1
Change
Change
Goal
Produce central change so the core question “Which direct and indirect consequences might this change trigger for different actors?” can be answered with stronger support.
Inputs for this step
- Precise change or trend
- stakeholder and system knowledge
- horizon and scenario boundary
Actions
- Specify central event, scope, timing, and assumption.
- Record source, rationale, and open uncertainty directly in central change.
Output
central change
central change · source · uncertainty · next decision
Quality check
Is the change unambiguous and timed?
Pitfall
Consequences are collected without causal parent, mechanism, or horizon. State every consequence as cause, actor, effect, and horizon and add counter-effects.
Timing: 10–20 minutes
- 2
First order
First order
Goal
Produce first ring so the core question “Which direct and indirect consequences might this change trigger for different actors?” can be answered with stronger support.
Inputs for this step
- central change
- stakeholder and system knowledge
- horizon and scenario boundary
Actions
- Collect direct consequences per stakeholder without an intermediate cause.
- Record source, rationale, and open uncertainty directly in first ring.
Output
first ring
first ring · source · uncertainty · next decision
Quality check
Is every consequence directly derived?
Pitfall
Consequences are collected without causal parent, mechanism, or horizon. State every consequence as cause, actor, effect, and horizon and add counter-effects.
Timing: 10–20 minutes
- 3
Further orders
Further orders
Goal
Produce outer rings so the core question “Which direct and indirect consequences might this change trigger for different actors?” can be answered with stronger support.
Inputs for this step
- first ring
- stakeholder and system knowledge
- horizon and scenario boundary
Actions
- Derive second- and third-order consequences from every edge.
- Record source, rationale, and open uncertainty directly in outer rings.
Output
outer rings
outer rings · source · uncertainty · next decision
Quality check
Does every causal chain remain visible?
Pitfall
Consequences are collected without causal parent, mechanism, or horizon. State every consequence as cause, actor, effect, and horizon and add counter-effects.
Timing: 10–20 minutes
- 4
Implications
Implications
Goal
Produce implication set so the core question “Which direct and indirect consequences might this change trigger for different actors?” can be answered with stronger support.
Inputs for this step
- outer rings
- stakeholder and system knowledge
- horizon and scenario boundary
Actions
- Prioritise uncertainty, signposts, opportunities, and risks.
- Record source, rationale, and open uncertainty directly in implication set.
Output
implication set
implication set · source · uncertainty · next decision
Quality check
Does every priority have a signpost?
Pitfall
Consequences are collected without causal parent, mechanism, or horizon. State every consequence as cause, actor, effect, and horizon and add counter-effects.
Timing: 10–20 minutes
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Versioned futures wheel with date, sources, owners, and next review.
Versioning / ownership
Retain date, source, assumption state, and decision for every version of futures wheel.
Tool alternatives
- futures wheel as board or document
- Source and evidence register
- Decision and action log
futures-wheel-working-template.md
Plan Futures Wheel around its domain steps and the concrete decision question.
Futures Wheel: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Establish and review the practice Time: 60–120 minutes
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Precise change or trend, stakeholder and system knowledge, horizon and scenario boundary, shared workspace, source links, and decision log.
- Roles: Foresight facilitator · diverse domain/stakeholder experts
- Advance information: Collect Precise change or trend, stakeholder and system knowledge, horizon and scenario boundary in advance and mark open assumptions.
- Overall time needed: 60–120 minutes
- Setup: Prepare central event with causally linked first- to third-order consequence rings visibly and calibrate assessment terms before starting.
Prepare for the work steps
Change: Change
- Precise change or trend
- stakeholder and system knowledge
- horizon and scenario boundary
First order: First order
- central change
- stakeholder and system knowledge
- horizon and scenario boundary
Further orders: Further orders
- first ring
- stakeholder and system knowledge
- horizon and scenario boundary
Implications: Implications
- outer rings
- stakeholder and system knowledge
- horizon and scenario boundary
Futures Wheel
| Consequence node | Record Node | Record Parent node | Record Order | Record Consequence | Record Mechanism | Record Uncertainty/signpost |
|---|---|---|---|---|---|---|
| Consequence 1 | ||||||
| Consequence 2 | ||||||
| Consequence 3 | ||||||
| Consequence 4 | ||||||
| Consequence 5 | ||||||
| Consequence 6 |
- Consequence 1: Test one real consequence with its causal parent.
- Consequence 2: Test one real consequence with its causal parent.
- Consequence 3: Test one real consequence with its causal parent.
- Consequence 4: Test one real consequence with its causal parent.
- Consequence 5: Test one real consequence with its causal parent.
- Consequence 6: Test one real consequence with its causal parent.
Do not record a consequence without parent node and justified mechanism.
The Millennium Project: Futures Research Methodology
Change: Change
Expected artifact: central change
central change · source · uncertainty · next decision
Entry:
...
- Is the change unambiguous and timed?
First order: First order
Expected artifact: first ring
first ring · source · uncertainty · next decision
Entry:
...
- Is every consequence directly derived?
Further orders: Further orders
Expected artifact: outer rings
outer rings · source · uncertainty · next decision
Entry:
...
- Does every causal chain remain visible?
Implications: Implications
Expected artifact: implication set
implication set · source · uncertainty · next decision
Entry:
...
- Does every priority have a signpost?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/futures-wheel/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.
futures-wheel-beispiel.md
Concrete filled scenario, fictional example
Change: provenance duty from 2028. First order: logging costs rise; unsupported answers are blocked. Second order: smaller providers use shared provenance services; users wait longer. Third order: auditability becomes a buying criterion and new insurance products emerge. Every edge names assumption and 1/3/5-year horizon.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- ChangeConsequences are collected without causal parent, mechanism, or horizon.View in phase
- First orderConsequences are collected without causal parent, mechanism, or horizon.View in phase
- Further ordersConsequences are collected without causal parent, mechanism, or horizon.View in phase
- ImplicationsConsequences are collected without causal parent, mechanism, or horizon.View in phase
Trap
Change
Symptom
Consequences are collected without causal parent, mechanism, or horizon.
What to do
State every consequence as cause, actor, effect, and horizon and add counter-effects.
Trap
First order
Symptom
Consequences are collected without causal parent, mechanism, or horizon.
What to do
State every consequence as cause, actor, effect, and horizon and add counter-effects.
Trap
Further orders
Symptom
Consequences are collected without causal parent, mechanism, or horizon.
What to do
State every consequence as cause, actor, effect, and horizon and add counter-effects.
Trap
Implications
Symptom
Consequences are collected without causal parent, mechanism, or horizon.
What to do
State every consequence as cause, actor, effect, and horizon and add counter-effects.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
futures wheel answers the core question with traceable evidence or explicitly marked uncertainty.
Owners, next actions, and review dates are named for open points.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.