scenario-planning

Featured

Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold, before a large irreversible commitment, or when a market, regulatory, or technology shift could invalidate the strategy.

AI & Automation 1,356 stars 209 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Scenario planning Forecasting produces one number and false confidence. Scenario planning produces a plan that survives being wrong, which is the realistic goal. ## Separate what you know from what you are assuming List the plan's assumptions explicitly, then sort them: - **Predetermined** — things that will happen regardless. Demographics, contracted commitments, technology already deployed. Plan around them; do not spend analysis on them. - **Genuinely uncertain and load-bearing** — the plan changes materially depending on how they resolve. Almost every plan has **two or three** load-bearing uncertainties. Finding them is most of the value, and the exercise usually surfaces one nobody had articulated. ## Build scenarios from the uncertainties, not from moods The common failure is three scenarios named optimistic, base, and pessimistic — which is one scenario with the numbers scaled, and it teaches nothing. Take the two most consequential uncertainties and build the quadrants. Each scenario should be internally coherent: if demand is high *and* supply is constrained, what else follows — pricing, competitor behavior, regulatory attention? Give each a name that captures its logic. Names make scenarios usable in conversation, which is where they earn their keep. Three or four scenarios. More cannot be held in mind; two collapses into best and worst. ## Stress-test the plan against each For every scenario: does the plan still work, what breaks first, and what w...

Details

Author
cbrock84
Repository
cbrock84/headcount
Created
1 weeks ago
Last Updated
1 weeks ago
Language
Markdown
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category