O'Brien, Frances and Meadows, Maureen
Due to copyright restrictions, this file is not available for public download
Click here to request a copy from the OU Author.
|DOI (Digital Object Identifier) Link:||http://dx.doi.org/doi:10.1016/j.techfore.2012.06.006|
|Google Scholar:||Look up in Google Scholar|
Scenario planning is one of the tools consistently reported as being used by executives to support their business development. A scenario planning project typically consists of three phases — preparation, development and use. This paper focuses on the third phase, where the scenarios that have been developed are put to their intended use in the context of developing strategy. Significant problems have been experienced as scenario projects move into this critical phase, perhaps due to a failure to link scenario development with strategy creation and execution efforts. These issues are explored via a case study of a large UK organisation operating in the transport sector, where a scenario-based strategy development exercise was used to support the leadership development of senior managers. We propose that a scenario orientation phase is a valuable missing link in many scenario projects, which can establish a bridge between scenario development and scenario use. Scenario orientation is a process of familiarisation with the scenarios that involves understanding their nature in some detail. This can be a crucial step, particularly if there is a significant time lapse between scenario development and scenario use, or if the people using the scenarios were not involved in their development. Without a good orientation to the scenarios, participants in a scenario planning exercise may be poor at the subsequent activities that require their explicit use.
|Item Type:||Journal Article|
|Copyright Holders:||2012 Elsevier Inc.|
|Keywords:||scenario development; Scenario use; scenario orientation; strategy development|
|Academic Unit/Department:||Open University Business School|
|Depositing User:||Maureen Meadows|
|Date Deposited:||27 Sep 2012 08:49|
|Last Modified:||21 Mar 2013 10:20|
Actions (login may be required)
|Report issue / request change|