
shell-method-scenario-planning
by Kingly-Agency
SKILL.md
name: shell-method-scenario-planning description: Navigate strategic uncertainty through multiple plausible future scenarios rather than single-point forecasting. Developed at Royal Dutch Shell, this framework replaces single-point predictions with 2-4 rich narratives representing genuinely different futures defined by critical uncertainties.
Shell Method (Scenario Planning)
Purpose
The Shell Method is a scenario planning framework for navigating long-term strategic uncertainty. Rather than predicting "the" future, create 2-4 rich narratives representing genuinely different future states. This approach enables identification of robust strategies that work across multiple futures and contingent strategies for specific scenarios.
Historical validation: Successfully predicted the 1973 oil crisis, enabling Shell to rise from 7th to 2nd largest oil company while competitors operated on business-as-usual assumptions.
When to Use This Skill
This skill should be used when:
- Facing strategic uncertainty at 5-30 year horizons - When long-term planning is needed and experts disagree about critical factors
- Single forecasts prove unreliable - When business-as-usual assumptions are being challenged by emerging uncertainties
- High-stakes decisions with irreversible commitments - When major investments or strategic pivots require stress-testing against multiple futures
- Experts fundamentally disagree - When domain experts provide conflicting predictions or data conflicts emerge
- Industry disruption is possible - When technological, regulatory, or market shifts could fundamentally reshape the competitive landscape
- Need shared organizational mental models - When coordinated response is required without central command during uncertainty
Semantic triggers: "scenario planning", "strategic foresight", "multiple futures", "uncertainty mapping", "long-term strategy", "what-if analysis for strategy"
Core Approach
Central distinction: Separate "predetermined elements" (high-confidence trends like demographics, infrastructure, enacted laws) from "critical uncertainties" (high-impact unknowns where experts disagree).
Key insight: Map uncertainties on a 2×2 matrix and develop narrative scenarios for each quadrant to identify:
- No-regret moves: Strategies that work across all futures
- Contingent moves: Actions triggered by specific scenario indicators
Process
Step 1: Identify Focal Question
Define the strategic decision and planning horizon:
- Set planning horizon - Typically 5-30 years for strategic uncertainty
- List critical unknowns - Technologies, regulations, competitors, customer behavior
- Frame as focal question - "What should our strategy be given [uncertainty]?"
Questions to answer:
- What strategic decision are we facing?
- What do we need to know but don't?
- What uncertainties could make or break our strategy?
Example: Shell 1971: "How should we position ourselves given potential energy supply disruptions and price volatility over the next 10 years?"
Step 2: Research Elements and Uncertainties
Separate what is known from what is genuinely uncertain:
- Identify predetermined elements - Trends with high confidence (demographics, infrastructure momentum, laws already passed)
- Identify critical uncertainties - High-impact factors where experts disagree or data conflicts
- Interview domain experts - Analyze data, identify divergent viewpoints
- Test for genuine uncertainty - If experts agree, it's predetermined; if they disagree, it's uncertain
Deliverables:
- List of predetermined elements ("We know...")
- List of critical uncertainties ("We don't know...")
Example: Shell 1971 - Predetermined: Oil production has physical limits, demand growing. Uncertain: When will supply/demand cross? How will governments respond?
Step 3: Select Two Critical Uncertainties
Choose two independent uncertainties for a 2×2 matrix:
- Rank uncertainties - By strategic impact and unpredictability
- Select two independent factors - Not correlated with each other
- Define clear endpoints - For each axis (e.g., "Loose regulation" vs "Tight regulation")
- Validate quadrants - Ensure four distinct, meaningful future states
Quality checks:
- Are these uncertainties genuinely unpredictable (not just unknown)?
- Are the two axes independent of each other?
- Do the four quadrants represent meaningfully different futures?
Output: 2×2 matrix with four quadrants representing distinct future states
Example: Shell - Axis 1: Oil prices (low vs high), Axis 2: Government intervention (minimal vs heavy)
Step 4: Develop Rich Narratives
Create detailed stories for how each quadrant future unfolds:
- Write 3-5 page narrative for each quadrant
- Include causal chains - Triggering events, stakeholder responses, second-order effects
- Give memorable names - e.g., "Wild West", "Regulated Utility", "Climate Crisis"
- Use storytelling techniques - Make vivid, coherent, plausible
- Ensure internal consistency - Each scenario must pass logical scrutiny
Story elements:
- What event could trigger this future?
- How would key stakeholders respond?
- What second-order effects cascade from initial changes?
- What does daily life/business look like in this future?
Output: 2-4 detailed scenario narratives (3-5 pages each) with memorable names
Example: Shell 1973 Type A scenario: Technical extraction limits → supply shortage → price spike → economic shock → geopolitical realignment
Step 5: Test Strategy Against Scenarios
Evaluate current and alternative strategies across all scenarios:
- Identify current strategy assumptions - What future is the current plan betting on?
- Stress-test across scenarios - How does current strategy perform in each quadrant?
- Identify vulnerabilities - Which scenarios break the current strategy?
- Design strategy variants - Create alternatives optimized for different scenarios
Analysis questions:
- Does our current strategy only work in one scenario?
- Which scenarios would cause strategic failure?
- What early indicators would signal which scenario is unfolding?
Output: Strategy vulnerability analysis across scenarios
Step 6: Develop Robust and Contingent Strategies
Design strategies that account for multiple futures:
- Identify no-regret moves - Actions that improve outcomes across ALL scenarios
- Design contingent strategies - Moves triggered when specific scenarios unfold
- Define leading indicators - Metrics that signal which scenario is materializing
- Establish decision triggers - Conditions that activate contingent strategies
- Monitor for scenario shifts - Ongoing surveillance for early warning signals
Strategy types:
- Robust/no-regret: Invest in adaptive capacity, diversification, scenario monitoring systems
- Contingent: Pre-plan responses but delay execution until scenario clarity emerges
Deliverables:
- List of no-regret moves (execute now)
- List of contingent strategies (execute if scenario X unfolds)
- Dashboard of leading indicators
- Decision triggers for strategy pivots
Example: Shell post-1973 - No-regret: Build scenario planning capability. Contingent: If supply constraints emerge, pre-position for scarcity market.
Practical Techniques
Technique 1: Type A vs Type B Scenarios
Purpose: Distinguish between psychological reframing and genuine uncertainty exploration.
Process:
- Type A scenarios - Uncomfortable but plausible futures that challenge business-as-usual mental models
- Type B scenarios - Variations on current trends (less transformative)
- Focus on Type A - These provide the most strategic value by breaking groupthink
Example: Shell's Type A (supply crisis) vs Type B (steady growth continuation)
Technique 2: Predetermined Elements Filter
Purpose: Avoid treating known trends as uncertainties.
Process:
- List all factors affecting the focal question
- Test each: "Do credible experts disagree fundamentally?"
- If NO → Predetermined element (incorporate into all scenarios)
- If YES → Critical uncertainty (becomes scenario differentiator)
Benefit: Reduces scenario complexity by removing false uncertainties
Technique 3: Early Warning Indicator System
Purpose: Detect which scenario is materializing as the future unfolds.
Process:
- For each scenario, identify unique leading indicators
- Monitor these indicators monthly/quarterly
- When multiple indicators align, activate contingent strategy
- Update scenarios annually as predetermined elements increase
Example: Monitoring oil inventory levels, OPEC statements, alternative energy investment as signals
Common Pitfalls
Avoid these anti-patterns:
- Probability assignment - Do NOT assign probabilities to scenarios; maintains openness to surprises
- Best/worst/baseline framing - Creates confirmation bias toward baseline; use neutral names
- Too many scenarios - 2-4 is optimal; more creates analysis paralysis
- Single-variable scenarios - Need at least two independent uncertainties for richness
- Insufficient narrative detail - Thin scenarios don't change mental models; aim for 3-5 pages each
- No strategy implications - Scenarios without strategic testing are just stories; must drive decisions
Integration
Complements:
- Pre-mortem analysis (test strategy failures in each scenario)
- OODA loop (rapid adaptation when scenario signals emerge)
- Red team/blue team exercises (stress-test scenario narratives)
- Strategic roadmapping (timeline no-regret vs contingent moves)
Conflicts with:
- Single-point forecasting methodologies
- Deterministic planning approaches
- Short-term optimization frameworks
Leads to:
- Dynamic strategy portfolios
- Adaptive capacity building
- Resilience-oriented decision-making
Time Estimates
Full process: 3-6 months for comprehensive organizational scenario planning Rapid sprint: 1-2 weeks for simplified scenario exploration Annual refresh: 1-2 weeks to update scenarios and indicators
Complexity: High - Requires cross-functional input, expert interviews, and organizational buy-in
Reference
Authors: Pierre Wack, Ted Newland, Peter Schwartz (Royal Dutch Shell, 1960s-1990s)
Category: Strategic foresight, decision-making under uncertainty
Historical context: Developed at Royal Dutch Shell to navigate oil industry volatility, gained legendary status after predicting 1973 oil crisis.
スコア
総合スコア
リポジトリの品質指標に基づく評価
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
レビュー
レビュー機能は近日公開予定です