Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
future_fabulators:scenario_methods [2014-02-13 04:47] – maja | future_fabulators:scenario_methods [2014-02-14 11:03] – [Scenario Methods] maja | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== Scenario Methods ==== | + | ===== Scenario Methods |
- | This page is an evolving, non-exhaustive collection of different steps that can be used in scenario building, different methods that we (could) use and links to interesting people/ | + | This page is an evolving, non-exhaustive collection of different steps that can be used in scenario building, different methods that we (could) use and links to interesting people/ |
+ | An overview of the whole process written for novice scenario builders can be found in [[http:// | ||
- | === Preparation beforehand === | + | There are many descriptions of scenario planning methods, with the biggest difference being whether the scenarios are designed to be exploratory (multiple alternative scenarios for different possible futures), or normative (designing a desired scenario, then figuring out what needs to be done in order to get there). When working with normative scenarios the most important task is ' |
+ | |||
+ | Joseph Coates wrote "Today the question of what scenarios are is unclear except with regard to one point-they have become extremely popular. Many people see scenarios as forecasts of some future condition while others disavow that their scenarios are forecasts. Yet looking at scenarios that do not come labeled as forecasts or non-forecasts. It is difficult to tell them apart. The purpose of the scenario is at a meta level, since the scenario usually does not speak for itself in terms of its purpose." | ||
+ | |||
+ | < | ||
+ | |||
+ | The scenario building exercise (step 1-6) in the [[prehearsal pocket guide]] is based on the method by Peter Schwartz in The Art of the Long View. On [[http:// | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | Michel Godet writes in [[http:// | ||
+ | simple tools that may be appropriated. However, these simple tools are inspired by intellectual rigor that enables one to ask the right questions. Of course, these tools do not come with a guarantee. The natural talent, | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | Anna Maria Orru and David Relan wrote [[:/ | ||
+ | |||
+ | More methods are described in the Futures Research Methodologies [[http:// | ||
+ | |||
+ | |||
+ | |||
+ | Below we explore different elements of scenario building, ask questions that emerged from our practice and investigate methods that might be used to improve the process. | ||
+ | |||
+ | |||
+ | |||
+ | ==== Preparation beforehand | ||
//What can we/ | //What can we/ | ||
Line 29: | Line 57: | ||
* ... | * ... | ||
- | === Key question === | + | ==== Key question |
//How to craft good questions?// | //How to craft good questions?// | ||
Line 44: | Line 72: | ||
- | === Plotting the present situation === | + | ==== Plotting the present situation |
//What are different ways to map-out the present situation surrounding the key question?// | //What are different ways to map-out the present situation surrounding the key question?// | ||
Line 62: | Line 90: | ||
* on the other hand, in more open-ended workshops (say in the beginning of projects) talking about what's fixed created some discomfort (or perhaps it was just unclear what we meant by fixed) | * on the other hand, in more open-ended workshops (say in the beginning of projects) talking about what's fixed created some discomfort (or perhaps it was just unclear what we meant by fixed) | ||
- | === Key factors === | + | ==== Key factors |
- | //How to best visualise and cluster the relationships between key factors// | + | //What are different ways to visualise and cluster the relationships between key factors// |
+ | |||
+ | * Affinity diagram | ||
+ | * [[http:// | ||
* " | * " | ||
Line 72: | Line 103: | ||
* success criteria (what will make my question succeed or fail) | * success criteria (what will make my question succeed or fail) | ||
- | === Change Drivers === | + | ==== Change Drivers |
* how much analysis is appropriate for the types of scenarios and prehearsals we’re making? | * how much analysis is appropriate for the types of scenarios and prehearsals we’re making? | ||
Line 88: | Line 119: | ||
* how effective are these methods and how can we usefully evalute them? | * how effective are these methods and how can we usefully evalute them? | ||
- | === Ranking critical uncertainties === | + | ==== Ranking critical uncertainties |
* what are different ways in which this is done by others? | * what are different ways in which this is done by others? | ||
- | === Scenarios === | + | * [[http:// |
+ | |||
+ | ==== Scenarios | ||
//When to use one, two, three or more axes// | //When to use one, two, three or more axes// | ||
Line 99: | Line 132: | ||
* __Branch analysis method__: The ‘branch analysis’ method is suited to developing scenarios around specific turning-points that are known in advance (e.g. elections, a referendum or peace process). This approach works best for a shorter time horizon: generally up to five years.[[http:// | * __Branch analysis method__: The ‘branch analysis’ method is suited to developing scenarios around specific turning-points that are known in advance (e.g. elections, a referendum or peace process). This approach works best for a shorter time horizon: generally up to five years.[[http:// | ||
* __Cone of plausibility__ method: offers a more deterministic model of the way in which drivers lead to outcomes, by explicitly listing assumptions and how these might change. Of the three techniques, this approach is most suitable for shorter-term time horizons (e.g. a few months to 2-3 years), but can be used to explore longer-term time horizons. It also suits contexts with a limited number of important drivers.[[http:// | * __Cone of plausibility__ method: offers a more deterministic model of the way in which drivers lead to outcomes, by explicitly listing assumptions and how these might change. Of the three techniques, this approach is most suitable for shorter-term time horizons (e.g. a few months to 2-3 years), but can be used to explore longer-term time horizons. It also suits contexts with a limited number of important drivers.[[http:// | ||
- | | + | |
- | * [[http:// | + | * [[http:// |
- | * [[http:// | + | |
- | * [[http:// | + | |
* [[http:// | * [[http:// | ||
Line 109: | Line 141: | ||
- | === From scenarios to story-worlds === | + | ==== From scenarios to story-worlds |
* what techniques can we use to flesh out the scenarios into interesting stories | * what techniques can we use to flesh out the scenarios into interesting stories | ||
Line 115: | Line 147: | ||
* how to create rich characters and meaningful plots? | * how to create rich characters and meaningful plots? | ||
- | === Scenario testing | + | ==== Retrocasting ==== |
- | + | ||
+ | "The best kinds of stories are about how you get from here to there, not just what there looks like." --Jamais Cascio | ||
+ | |||
+ | Searching for present signals, asking the question "how to get from here to there" | ||
+ | Backcasting starts with defining a desirable future and then works backwards to identify policies and programs that will connect the future to the present. | ||
+ | |||
+ | However with retrocasting/ | ||
+ | |||
+ | |||
+ | //What tools can we use to structure scenario testing?// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | Another interesting possibility is to abstract principles from a scenario and retrocast from them. In [[http:// | ||
+ | |||
+ | < | ||
- | (signals, how to get from here to there) | ||
- | * how is this done by others? | ||
* what are important things to focus on? | * what are important things to focus on? | ||
- | === Visualising === | + | ==== Visualising |
* which methods could we use to visualise possible futures? | * which methods could we use to visualise possible futures? | ||
- | === Prototyping === | + | ==== Prototyping |
* which methods could we use to prototype possible futures? | * which methods could we use to prototype possible futures? | ||
- | === Prehearsals === | + | ==== Prehearsals |
* how to design them? | * how to design them? | ||
Line 136: | Line 184: | ||
* how to evaluate them? | * how to evaluate them? | ||
- | === Follow-up === | + | ==== Follow-up |
* How can we follow-up what happens to the groups after we finish the workshops (especially to understand what happens to commitments to actions and preferred possible futures)? | * How can we follow-up what happens to the groups after we finish the workshops (especially to understand what happens to commitments to actions and preferred possible futures)? | ||
* How much do we need to be involved in the follow-up? | * How much do we need to be involved in the follow-up? | ||
+ |