Official skill · Strategy

Scenario planning

Builds four scenarios from two critical uncertainties around one decision, tests the decision in each, and ends with signposts, robust moves, and contingent moves. Use it when before a long, hard-to-reverse commitment such as a lease, plant, or new country.

Works in Claude, ChatGPT, and coding agents. On Team and Business, the official skill in your pod updates itself when we improve it.

When to use it

What you give it

What you get

A focal question, forces split into predetermined elements and critical uncertainties, a 2x2 of four named scenarios, the decision tested in each, signposts, and robust and contingent moves.

How it works

  1. Write the focal question One sentence naming the decision and the horizon, such as "Should we sign an eight-year lease for a second site?". A vague question ("what is the future of retail?") gives vague scenarios. Ask for the decision if the user gave only a topic.
  2. List the key factors Write the local factors that decide whether the decision succeeds: customers' demand, prices, costs, competitors, staff, suppliers. Keep them close to the business.
  3. List the driving forces For each key factor, write the wider forces behind it: social, economic, political, environmental, and technological. Use only forces the user named or that follow directly from their facts; ask about any area left empty.
  4. Separate predetermined elements from critical uncertainties A predetermined element will happen in every scenario, because it is already under way (people already born, a law already passed, a contract already signed). A critical uncertainty is both important to the decision and genuinely open. Rank the forces on importance and uncertainty, and pick the two that score highest on both.
  5. Build four scenarios from two axes Make each critical uncertainty an axis with two clear end states. The four combinations are the scenarios. Give each a short, memorable name and a paragraph describing that world at the horizon, with every predetermined element present in all four. Check that each is internally consistent and plausible; if one combination makes no sense, say so and explain the three that remain.
  6. Test the decision in each scenario For each scenario, write how the decision and the current plan fare: what goes well, what breaks, and what the company would wish it had done. A decision that works in only one scenario is a gamble; name it as one.
  7. Choose signposts For each scenario, pick 1 to 3 observable signals that would show the world is moving toward it, with where to watch and how often. Prefer signals that appear early and that someone will actually check.
  8. Sort the moves Robust moves make sense in all or most scenarios: do them now. Contingent moves make sense only in some: prepare them, and tie each to the signpost that triggers it. Name any move to avoid because it fails badly in a plausible scenario.
  9. End with the decision and next actions Answer the focal question in one paragraph, list the robust moves with owners, the signposts with who watches them, and a date to review the scenarios.

Share it with your team

Add it to an AI Skill Pod and everyone on the team, contractors included, uses the same version from their own AI. Read the best ways to share AI skills with a team

Add to my team's pod

Changelog

Sources

  1. Scenarios: Uncharted Waters Ahead - Pierre Wack, Harvard Business Review (September 1985) (read 2026-11-04)
  2. Scenarios: Shooting the Rapids - Pierre Wack, Harvard Business Review (November 1985) (read 2026-11-04)
  3. The man who saw the future - Art Kleiner, strategy+business (2003) (read 2026-11-04)
  4. Schwartz's 8-Step Process (scenario planning) - Mind Tools (read 2026-11-04)
  5. Rethinking the 2x2 scenario method: Grid or frames? - Ramirez and Wilkinson, Technological Forecasting and Social Change 86 (2014) 254-264 (read 2026-11-04)
  6. The Art of the Long View, Peter Schwartz (Doubleday/Currency, 1991) - Open Library (read 2026-11-04)