Purpose
The Futures Wheel helps explore the consequences of a decision, a trend, or a strategic move in a structured way. It makes visible which first, second, and third-order effects could arise from an event.
Systems Thinking Mapping tool
Futures Wheel
Explores direct and indirect consequences of an event or change across multiple impact rings.
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.
Which direct and indirect consequences might this change trigger for different actors?
- Participants
- 3-10
- Time
- 60-120 min
Futures Wheel uses central event with causally linked first- to third-order consequence rings. Assessments remain justified and context-bound.
Change
Change
Specify central event, scope, timing, and assumption.
First order
First order
Collect direct consequences per stakeholder without an intermediate cause.
Further orders
Further orders
Derive second- and third-order consequences from every edge.
Implications
Implications
Prioritise uncertainty, signposts, opportunities, and risks.
Update after new evidence or a material context change and retain the previous version.
A good fit when
For strategic foresight and policy/product consequences involving several stakeholders.
Ideal for
- Foresight
- Early-Stage Strategy
- Consequence Analysis
Not good for
- Quantitative forecasting
- Backlog prioritization
- Unclear starting question
Outputs
futures wheel
futures wheel with traceable sources, assumptions, and domain decisions.
Decision and review trail
Owners, dates, and next review for futures wheel.
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.
First step
Start with the core question: Which direct and indirect consequences might this change trigger for different actors?
Good to do first
Deep dive
How it works
A central event or change is placed in the middle. Direct consequences are collected in the first ring, indirect consequences in the second and further rings. Connections show causal paths, uncertainties, and possible points of intervention.
In detail
The Futures Wheel works because it turns future thinking from a linear list into a visible network of consequences. A trend, a decision, or an event is treated as the starting point, after which direct consequences, indirect consequences, and interactions are added step by step. The method becomes strategically strong when consequences are not just collected but also marked by probability, impact, and need for action.
Facilitation
Keep the center statement concrete and checkable. Separate direct consequences from indirect consequences, otherwise the wheel quickly turns into an unsorted mind map. At the end, mark the three most important chains of consequences and derive signals, decisions, or experiments from them.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
Futures Wheel: WorksheetPlan Futures Wheel around its domain steps and the concrete decision question.markdown
Futures Wheel: WorksheetPlan Futures Wheel around its domain steps and the concrete decision question.
markdownfutures-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
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Business Strategy
Scenario Planning
Instead of Futures Wheel, choose Scenario Planning when several plausible pictures of the future with different uncertainties should be developed.
Systems Thinking
Causal Loop Diagram
Instead of Futures Wheel, choose Causal Loop Diagram when feedback loops and reinforcing or balancing loops in the system should be modeled.
Facilitation
Mind Mapping
Instead of Futures Wheel, choose Mind Mapping when ideas should be gathered freely by association and causal consequences do not play a central role.
Systems Thinking
Wardley Mapping
Maps value creation and evolution stages so strategic options, levers, and market movements become legible.
Systems Thinking
Rich Picture
Makes an unclear problem situation visible with actors, tensions, and flows before premature solutions emerge.
Systems Thinking
Stock and Flow Diagram
Models stocks, inflows and outflows, and delays to understand dynamics, bottlenecks, and capacity.
Constraints and origin
MediumWorkshop + async60-120 min
Profile
- Method form
- Mapping tool
- Participants
- 3-10
- Time
- 60-120 min
- Maturity
- Established
- Origin
- Jerome C. Glenn
Next up: Systems Mapping