Different problems call for different scenario methods. Some efforts should widen the aperture to surface the full landscape of plausible futures; others must drive quickly from uncertainty to a concrete commitment with triggers and risk budgets.
4.1 Exploratory vs. Decision‑Led—Selection Guide
Working definitions
- Exploratory scenarios widen the field. They aim to map the structure of uncertainty, surface critical drivers, and provoke new strategic questions. The output is insight and option discovery: a shared language for futures, a shortlist of pivotal uncertainties, and a first pass at signposts.
- Decision‑led scenarios narrow the field. They start with a specific choice at risk, craft three to four contrasting futures relevant to that choice, quantify operating/financial ranges, and produce an options portfolio with triggers, budgets, and owners.
Both are legitimate. The art is knowing when to explore and when to decide—and how to move from one to the other without losing speed.
When to favor EXPLORATORY
- Problem is not yet a decision. You suspect the game board is shifting, but you can’t write a one‑sentence decision question (3.1).
- Mental models diverge. The top team holds incompatible views of how the world might evolve; you need a shared map before arguing options.
- Frontier domains. Technology, regulation, or consumer behavior is early and unstable; data is thin and analogies are noisy.
- Portfolio framing. You need to identify opportunity arenas before commissioning multiple decision sprints.
- Capability build. New teams benefit from a short exploratory pass to learn the craft and create a driver library.
When to favor DECISION‑LED
- A consequential call exists. Capital, timing, or exposure must be set within this planning cycle.
- Irreversibility looms. Lock‑in or long half‑lives make “wait and see” expensive.
- Execution windows matter. Suppliers, partners, or regulators will not hold the line indefinitely.
- Governance demands a recommendation. Board, capital committee, or disclosure timelines require a decision‑grade pack.
- You can name 3–5 credible alternatives. The work is to sort them, not to invent them.
Outputs, cadence, and team: side‑by‑side
- Exploratory (2–3 weeks, compressed)
- Outputs: driver library (PESTLE + industry structure), ranked critical uncertainties, 3–5 named scenario logics at sketch level, preliminary signpost set, opportunity/option inventory.
- Team: Strategy (lead), CI/Corp Affairs, 1–2 external SMEs as needed, Facilitator; FP&A on light touch to sanity‑check orders of magnitude.
- Governance: Sponsor check‑in only; no capital approvals. Success is clarity and scope for decisions, not commitments.
- Decision‑led (4–6 weeks, sprint)
- Outputs: three to four full scenario briefs, quantified operating/financial ranges by scenario, exposure analysis vs. plan, options portfolio (no‑regrets/options/hedges/big bets), trigger & playbook register, decision memo.
- Team: Strategy (integrator), FP&A (model owner), Ops/Product, Risk (signposts), PMO, Challenger; Legal/Treasury as liaisons where relevant.
- Governance: Gate rhythm with Gate 4 commitments and risk budgets.
Selector (use in kickoff; choose the highest‑scoring mode)
Score each item 1 if true.
- We can write the decision in one sentence with a named owner and risk budget.
- There are 3–5 credible alternatives including “do nothing.”
- Irreversibility or lock‑in exceeds two planning cycles.
- A board or capital decision is due within 60 days.
- Enough data exists to quantify ranges with Finance in 2–3 weeks.
- Senior views differ mainly on parameters, not on structures.
- We can name 5–10 signposts that would differentiate futures within 12 months.
If ≥5 are true, run the decision‑led now. If ≤3 are true, start with an exploratory pass (time‑boxed) and pivot to decision‑led once 1–2–3 are satisfied.
Guardrails to prevent misuse
- Exploratory is not a research safari. Time‑box to two or three weeks, cap sources, and require every scan item to map to a driver or assumption in the log (TPL‑10). End with a Decision Funnel: the three decisions this work makes possible, with owners and proposed timing.
- Decision‑led is not a creativity workshop. Keep scenarios small and contrasting; tie every exhibit to a decision or risk budget; ban extra scenarios after Gate 2.
Bridging pattern: Explore‑to‑Decide Sprint (recommended hybrid)
A practical sequence that keeps speed without skipping discovery:
- Week 0–1 (Exploratory mini‑sprint). Build a driver library, shortlist critical uncertainties, and sketch three to five scenario logics. Deliverables: TPL‑05/06/07 and a one‑page Decision Funnel naming the top two decisions to prosecute.
- Week 2 (Decision framing). Select one decision, complete TPL‑01, lock evaluation/monitoring horizons, and choose the three to four scenarios most relevant to that call.
- Weeks 3–6 (Decision‑led sprint). Produce the MVSP (TPL‑09/10/12/14/15/03) and take commitments at Gate 4.
Common failure modes and counter‑moves
- Exploratory without a handoff. Insight accumulates; nothing changes. Counter‑move: insist on a Decision Funnel with owners and dates, approved by the Sponsor.
- Decision‑led with a fuzzy question. The team models noise. Counter‑move: stop and complete TPL‑01; if the question won’t fit in one sentence with a budget, revert to exploratory.
- Overlapping efforts. Multiple teams build different futures. Counter‑move: a single driver library and signpost set curated by Strategy/Risk, reused across sprints.
- Premature quantification. Teams force numbers for unknowables. Counter‑move: keep selected elements qualitative; focus quant on parameters that move VaS and exposure.
How success is judged
- Exploratory: Did we reduce ambiguity? Are the top 5–7 drivers explicit? Can we name concrete decisions (with owners) that this work unlocks? Did we create a reusable driver/signpost library?
- Decision‑led: Did we commit no‑regrets, buy time‑boxed options, set hedges and triggers, and reallocate resources? Are signposts live and owned? Are ranges and assumptions traceable?
A quick example
A consumer platform faces uncertain privacy regulation and ad‑tech deprecation. In Week 1, an exploratory pass surfaces three structures: “Tight Consent,” “Soft Guardrails,” and “Walled Gardens.” It ranks drivers and proposes signposts (regulatory calendars, platform policy changes, signal loss metrics). The Decision Funnel identifies two immediate calls: (a) whether to accelerate first‑party data capture, and (b) whether to build a partner clean‑room. In Weeks 2–5, a decision‑led sprint prosecutes (a): three contrasting scenarios are quantified, exposure vs. plan is shown, and leadership approves no‑regrets investments, a 12‑month option on a clean‑room pilot with an explicit premium and expiry, and triggers tied to two pending regulatory thresholds.
4.2 2×2 Archetypes vs. Morphological Approaches—When to Use Which
Not every decision benefits from the same scenario architecture. The two workhorse patterns—2×2 archetypes and morphological analysis—optimize for different problems. The 2×2 is a communication‑friendly way to create four sharply contrasting futures from two dominant uncertainties. Morphological analysis (the “Zwicky box”) is a systematic way to combine discrete states of many drivers and then prune to coherent futures. Choose the form that fits your decision geometry, not the one your team happens to know best.
What a 2×2 is good at
A 2×2 excels when two uncertainties plausibly dominate the choice and are reasonably independent. It forces contrast, is easy to remember, and travels well with boards and investors. It is ideal when you need speed and alignment, when the decision window is near, and when senior leaders require a small set of named futures to stress‑test strategy and approve triggers.
Use a 2×2 when:
- A single decision is live, with 3–5 alternatives and a 3–7 year evaluation horizon.
- Two uncertainties explain most of the spread in value‑at‑stake.
- You must communicate crisply and commit capital this cycle.
- Your organization benefits from a shared language quickly (e.g., “Tight Consent” vs. “Soft Guardrails”).
Limits of the 2×2
It can oversimplify when drivers interact strongly or when “orthogonality” is assumed but not true. Quadrants can become cartoonish extremes. Teams sometimes multiply 2×2’s (ending in scenario sprawl) or sneak in a tinted base case. If two axes don’t genuinely move the decision, a 2×2 produces elegant pictures and weak guidance.
What morphological analysis is good at
Morphology treats scenarios as combinations of driver states. You define 6–10 key drivers (e.g., regulation stance, input cost regime, ecosystem openness, channel structure), enumerate 2–4 discrete states for each, and then apply cross‑consistency checks to eliminate impossible or implausible pairings. What remains are internally coherent “configuration kernels” you can cluster into 3–4 usable scenarios. This method is powerful when interactions matter, when there are multiple feasible pathways, and when you must audit logic.
Use morphology when:
- More than two drivers materially shape the choice and their interactions could flip the answer.
- You’re designing platform or supply‑chain architectures with coupled constraints.
- You need traceable reasoning for regulators, risk committees, or joint‑venture partners.
- You want a reusable library of driver states that can support multiple decision sprints.
Limits of morphology
Left unmanaged, it explodes combinatorially and drains time. It can yield “catalog” scenarios that are analytically sound but narratively flat. Without a strong cross‑consistency step, you will include incoherent worlds. And for executive audiences, morphology often needs a final narrative pass (sometimes back into a 2×2 frame) to be memorable.
Selector—pick the method that fits the decision
Score 1 if true.
- Two uncertainties explain ≥60% of VaS spread.
- The two uncertainties are approximately independent.
- Commitments are due within 60 days (board/Capital Committee).
- You can state the decision crisply and name 3–5 alternatives.
- Driver interactions are modest or second‑order.
- You need portable narratives more than an audit trail of combinations.
If ≥4, start with a 2×2. If ≤3, run a morphological pass first, then compress to 3–4 scenarios (often displayed as a 2×2 for communication).
Hybrid pattern that works in practice
Run a short morphological pass in Week 1 to define drivers, states, and cross‑consistency, then select the two most decision‑salient uncertainties for a 2×2 display. This gives you the discipline of morphology with the clarity of a 2×2. Alternatively, if you begin with a 2×2, use morphology within each quadrant to specify variants (e.g., different supply regimes) and to design signposts that tell you which variant you’re in.
How to run a 2×2 in 48 hours (for a decision‑led sprint)
- Confirm the decision, alternatives, and VaS drivers (TPL‑01, TPL‑11).
- Rank uncertainties by impact and independence; select two that move choices.
- Define clear, discrete states for each axis (not “high/low” if that hides ambiguity).
- Name the four quadrants; write a five‑sentence logic for each.
- Apply coherence tests: plausibility, distinctiveness, decision relevance.
- Draft one‑page briefs (TPL‑09) and a first cut of signposts for each quadrant.
- Hand to FP&A to start ranges (TPL‑12) and to Strategy to begin the options canvas (TPL‑14).
How to run a fast morphological pass (1–2 days)
- Select 6–10 drivers that could change the answer; write 2–4 states for each.
- Build the grid; run a cross‑consistency assessment to eliminate impossible pairs (e.g., “strict data localization” with “frictionless cross‑border ad‑tech”).
- From what remains, extract 6–10 coherent configurations; cluster them into 3–4 scenario kernels.
- For each kernel, write implications and candidate signposts; then draft TPL‑09.
- If needed, place the 3–4 kernels onto a 2×2 defined by the two most communicable uncertainties.
Quality bar—regardless of method
- Contrast: Each scenario must change at least one strategic choice or option premium.
- Coherence: No internal contradictions; cross‑impact logic is explicit.
- Coverage: The set spans the plausible space relevant to the decision without gaps or duplicates.
- Parsimony: Three or four scenarios only; anything more dilutes attention.
- Traceability: Every assertion links to TPL‑10; every number to TPL‑12.
Illustrative application
A payments company is deciding whether to accelerate a network‑tokenization bet. Two uncertainties dominate VaS—merchant adoption pace and regulatory stance on interchange—so the team frames a 2×2 (“Rapid Adoption / Permissive” through “Slow Adoption / Restrictive”) for executive debate and options design. In parallel, a short morphological pass clarifies driver states for card network behavior, big‑tech wallet policies, fraud‑loss regimes, and issuer incentives. Cross‑consistency shows that “Restrictive regulation + Rapid adoption + Aggressive issuer subsidies” is implausible, pruning one quadrant’s extreme. The final pack keeps the 2×2 for narrative clarity but uses morphological insights to set more precise signposts and to stage option premiums (e.g., wallet integrations) by variant.
The principle is simple: when two uncertainties truly steer the ship, use a 2×2 to move fast and align. When interactions decide the game, use morphology to see the space—and then compress to a deci
