When this helps
Workbook-grounded and author-clarified; proposed reconstruction. People use ‘what if?’ questions to explore how a decision, changed condition or disruptive event might unfold before outcomes can be observed. The question may concern an immediate practical change or a deliberately fantastical future. Direct experimentation may be expensive, slow, unsafe or impossible, leaving consequences and dependencies unexamined.
Proposed and author-clarified. Informal speculation often stops at the first direct consequence or treats one coherent story as the future. Premature probability estimates can impose false precision, while dramatic generated narratives can conceal assumptions, omit stakeholders and blur the difference between possibility, plausibility and prediction.
Pattern response
Proposed and author-clarified. Frame an explicit ‘what if?’ question and construct one or more contrasting developments from the changed condition. Repeatedly ask ‘then what?’ to trace direct effects, second-order consequences, stakeholder responses, feedback loops and branching possibilities. Allow practical, plausible and fantastical scenarios, but label their status and record their assumptions. Introduce evidence, likelihoods or probabilities when they help the inquiry and their basis can be stated. Keep exploratory discussion distinguishable from prediction.
- A comparative set of scenarios with explicit drivers, uncertainties and assumptions.
- Traceable implications for stakeholders, constraints, opportunities and failure conditions.
- Identification of decisions that remain robust across several plausible futures.
- A review record that distinguishes speculation, evidence and current commitment.
Workflow at a glance
- 01
Frame the scenario question
An accountable person defines boundaries, checks evidence and assumptions, and retains authority to continue, revise, pause, or reject.
MOD-001 · MOD-021 - 02
Generate contrasting developments
An accountable person defines boundaries, checks evidence and assumptions, and retains authority to continue, revise, pause, or reject.
MOD-022 · MOD-030 - 03
Trace implications and constraints
An accountable person defines boundaries, checks evidence and assumptions, and retains authority to continue, revise, pause, or reject.
MOD-017 · MOD-020 - 04
Compare and review
An accountable person defines boundaries, checks evidence and assumptions, and retains authority to continue, revise, pause, or reject.
MOD-042 · MOD-044
Human checkpoints
Participants define the focal question and decide how scenario findings will be used. Stakeholders and domain experts challenge assumptions, omissions and likelihood claims. The system expands and contrasts possibilities; it does not turn speculative fluency into evidence or authorise consequential action. People decide whether probability is useful, judge its basis and retain authority over interpretation.
Risks and misuse
Reconstructed risks
- A scenario is presented as a forecast or evidence-backed prediction.
- Unsupported numerical probabilities create an appearance of precision.
- Generated futures reproduce stereotypes or omit marginalised stakeholders.
- Narrative vividness displaces causal coherence and decision relevance.
- The exercise confirms a preferred strategy by manipulating assumptions.
- Speculative claims escape their context and circulate as findings.
Use this pattern
Begin with the recurring problem and the authorised inputs. Follow the workflow in order, keep intermediate outputs inspectable and retain the named human decisions.
- Minimum viable implementation: follow the documented four-stage procedure manually and retain a comparative set of scenarios with explicit drivers, uncertainties and assumptions, together with review decisions.
- Robust implementation: add structured templates, version history, provenance, access controls, exception handling and explicit quality gates suited to speculative scenario exploration.
- Low-code implementation: connect approved services only where inputs and outputs remain inspectable, with a human approval gate before consequential use or publication.
- Local or privacy-preserving implementation: keep sensitive or unpublished artefacts in controlled storage and prefer local processing where policy, risk or participant expectations warrant it.
- Speculative implementation: explore additional automation only within constrained permissions, with logging, stop conditions, rollback and retained human authority.
Reusable modules
Related patterns
Technical and provenance detail
Data and information flow
Proposed and author-clarified. The focal ‘what if?’ question, changed condition, present evidence, time horizon and declared uncertainties enter the workflow. Each scenario carries its assumptions, status and consequence chain. Optional likelihood judgements retain their stated basis. The final comparison separates imaginative content, plausible inference, evidence-supported claims and present implications.
Source provenance
- Pattern ID: DP-025
- Original workbook row(s): 28, 29, 30, 45.
- Original label(s): Speculative scenario generation; Useful in unit planning: if then then what is likely?; Ideating and testing without heavy lifting; Speculative Scenario Generation (DC).
- Inherited source category/theme: Design specific things ideation/brainstorming; THEME: Ideation.
- Source status: workbook-derived source; the source supplies concise labels rather than a complete pattern narrative.
- Extraction notes: Original labels, row relationships, categories, themes, rationales, and confidence assessments are preserved below.
- Editorial interventions: The problem statement, response, forces, risks, workflow, and module mapping are documented reconstructions that retain explicit provenance labels and remain open to author and practice-based validation.
- Author clarification (2026-08-20): The pattern concerns broad exploration of ‘what if?’ questions rather than academic design work alone. Scenarios may range from immediate changes to fantastical future disruptions, including concentrated control of AI or asteroid damage to satellite systems. The purpose is initially exploratory discussion of future possibilities. Plausible causal consequences and probabilities may be considered, but probability assignment is secondary and must not turn the exercise into an unsupported forecast.
Open questions
- What minimum reasoning or evidence is needed to distinguish a plausible scenario from one that is merely possible in different domains?
- How should scenario sets be tested for missing stakeholders and inherited cultural assumptions?
- When do likelihood estimates improve exploration, and when do they create false precision or close discussion prematurely?