De-escalating Information Technology Projects: Lessons from the Denver International Airport1
Authors:
- 1 September 2000
- journal article
- research article
- Published by MIS Quarterly in MIS Quarterly
- Vol. 24 (3) , 417-447
Abstract
Project failure in the information technology area is a costly problem, and troubled projects are not uncommon. In many cases, these projects seem to take on a life of their own, continuing to absorb valuable resources, while failing to deliver any real business value. While prior research has shown 1Sirkka Jarvenpaa was the accepting senior editor for this paper. that managers can easily become locked into a cycle of escalating commitment to a failing course of action, there has been comparatively little research on de-escalation, or the process of breaking such a cycle. Through de-escalation, troubled projects may be successfully turned around or sensibly abandoned. This study seeks to understand the process of de-escalation and to establish a model for turning around troubled projects that has both theoretical and practical significance. Through a longitudinal case study of the IT-based baggage handling system at Denver International Airport (DIA), we gathered qualitative data on the de-escalation of commitment to a failing course of action, allowing us to inductively develop a model of the de-escalation process as it unfolded at DIA. The model reveals deescalation as a four-phase process: (1) problem recognition, (2) re-examination of prior course of action, (3) search for alternative course of action, and (4) implementing an exit strategy. For each phase of the model, we identified key activities that may enable de-escalation to move forward. Implications of this model for both research and practice are discussed.Keywords
This publication has 36 references indexed in Scilit:
- Process Models in Information Systems1997
- Escalation and De-escalation of Commitment in Response to Sunk Costs: The Role of Budgeting in Mental AccountingOrganizational Behavior and Human Decision Processes, 1995
- Effects of absolute and relative sunk costs on the decision to persist with a course of actionOrganizational Behavior and Human Decision Processes, 1991
- De-escalation of commitment in oil exploration: When sunk costs and negative feedback coincide.Journal of Applied Psychology, 1990
- Understanding the “90% syndrome” in software project management: A simulation-based case studyJournal of Systems and Software, 1988
- Opportunity costs and the framing of resource allocation decisionsOrganizational Behavior and Human Decision Processes, 1986
- Continuing investment under conditions of failure: A laboratory study of the limits to escalation.Journal of Applied Psychology, 1986
- Contextual effects on escalation processes in public sector decision makingOrganizational Behavior and Human Decision Processes, 1986
- Choices, values, and frames.American Psychologist, 1984
- Factors affecting withdrawal from an escalating conflict: Quitting before it's too lateJournal of Experimental Social Psychology, 1979