De-escalation of commitment to information systems projects: a process perspective

Escalation of commitment is a common and costly problem among information system projects. Although the potential of de-escalation of commitment to failing courses of action has been much heralded, many de-escalation efforts may result in failure due to constituencies biasing facts in the direction of previously accepted beliefs and therefore preventing an organization from de-escalating commitment to a project. Here, we examine actors’ commitment transformation during the de-escalation of commitment to an e-procurement project in a local government organization in the UK. Our findings suggest that the commitment transformation process can be enacted successfully through the deployment of behaviour disconfirmation, continuous commitment, provision of psychological safety, development, and the alignment and integration of new attitudes and behaviours. The research and practical implications of these findings are discussed, and future research areas are explored.

[1]  Mark Keil,et al.  Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models , 2000, MIS Q..

[2]  Barry M. Staw,et al.  ORGANIZATIONAL ESCALATION AND EXIT: LESSONS FROM THE SHOREHAM NUCLEAR POWER PLANT , 1993 .

[3]  Mark Keil,et al.  Blowing the whistle on troubled software projects , 2001, CACM.

[4]  Michael D. Myers,et al.  A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems , 1999, MIS Q..

[5]  Bernard C. Y. Tan,et al.  Willingness to Continue with Software Projects: Effects of Feedback Direction and Optimism under High and Low Accountability Conditions , 2003, J. Assoc. Inf. Syst..

[6]  T. Newcomb,et al.  Readings in Social Psychology , 1948, Teachers College Record.

[7]  Mark Keil,et al.  Keeping Mum as the Project Goes Under: Toward an Explanatory Model , 2001, J. Manag. Inf. Syst..

[8]  K. Weick,et al.  Organizational change and development. , 1999, Annual review of psychology.

[9]  Helga Drummond,et al.  Book Review , 1999 .

[10]  Dennis Duchon,et al.  An Empirical Test of Staw and Ross's Prescriptions for the Management of Escalation of Commitment Behavior in Organizations* , 1989 .

[11]  Chip Heath,et al.  Escalation and De-escalation of Commitment in Response to Sunk Costs: The Role of Budgeting in Mental Accounting , 1995 .

[12]  Rajiv Sabherwal,et al.  Determinants of Commitment to Information Systems Development: A Longitudinal Investigation , 1996, MIS Q..

[13]  Timo Saarinen,et al.  Understanding Runaway Information Technology Projects: Results from an International Research Program Based on Escalation Theory , 1994, J. Manag. Inf. Syst..

[14]  P. Harrison,et al.  IMPACT OF 'ADVERSE SELECTION' ON MANAGERS' PROJECT EVALUATION DECISIONS , 1993 .

[15]  Glen Whyte,et al.  Escalating Commitment to a Course of Action: A Reinterpretation , 1986 .

[16]  Ramiro Montealegre,et al.  De-escalating Information Technology Projects: Lessons from the Denver International Airport , 2000, MIS Q..

[17]  Tony Moynihan,et al.  Coping with client-based 'people-problems': the theories-of-action of experienced IS/software project managers , 2002, Inf. Manag..

[18]  Donald E. Conlon,et al.  The Role of Project Completion Information in Resource Allocation Decisions , 1993 .

[19]  Mark Keil,et al.  Pulling the Plug: Software Project Management and the Problem of Project Escalation , 1995, MIS Q..

[20]  Bruce E. McCain.  Continuing Investment Under Conditions of Failure: A Laboratory Study of the Limits to Escalation , 1986 .

[21]  E. Schein.  Kurt Lewin's change theory in the field and in the classroom: Notes toward a model of managed learning , 1996 .

[22]  Mark Keil,et al.  The reluctance to report bad news on troubled software projects: a theoretical model , 2003, Inf. Syst. J..

[23]  Mark J. Martinko,et al.  The Decision to Blow the Whistle: A Social Information Processing Framework , 2003 .

[24]  Mark Keil,et al.  The challenge of accurate software project status reporting: a two-stage model incorporating status errors and reporting bias , 2002, IEEE Trans. Engineering Management.

[25]  Mark Keil,et al.  Turning Around Troubled Software Projects: An Exploratory Study of the Deescalation of Commitment to Failing Courses of Action , 1999, J. Manag. Inf. Syst..

[26]  Edward J. Conlon,et al.  Diffusibility of Blame: Effects on Persistence in a Project , 1987 .

[27]  Ramiro Montealegre,et al.  Reporting bad news about software projects: impact of organizational climate and information asymmetry in an individualistic and a collectivistic culture , 2003, IEEE Trans. Engineering Management.

[28]  I. Royer.  Why bad projects are so hard to kill. , 2003, Harvard business review.

[29]  Cheng-Suang Heng,et al.  De-escalation of commitment in software projects: Who matters? What matters? , 2003, Inf. Manag..

[30]  Joel Brockner,et al.  Factors affecting withdrawal from an escalating conflict: Quitting before it's too late , 1979 .

[31]  K. Lewin,et al.  Group decision and social change. , 1999 .

[32]  Keith M. Howe,et al.  On Optimal Asset Abandonment and Replacement , 1983 .

[33]  Dan Lovallo,et al.  Delusions of Success , 2003 .

[34]  A. C. Rogers,et al.  De-escalation of commitment in oil exploration : when sunk costs and negative feedback coincide , 1990 .

[35]  H. Drummond.  DE-ESCALATION IN DECISION MAKING: A CASE OF A DISASTROUS PARTNERSHIP* , 1995 .

[36]  Bernard C. Y. Tan,et al.  A Cross-Cultural Study on Escalation of Commitment Behavior in Software Projects , 2000, MIS Q..

[37]  Marcia P. Miceli,et al.  Potential Predictors of Whistle-Blowing: A Prosocial Behavior Perspective , 1985 .

[38]  Itamar Simonson,et al.  Deescalation Strategies: A Comparison of Techniques for Reducing Commitment to Losing Courses of Action , 1992 .

[39]  Eugene J. Kutcher,et al.  When success breeds failure: history, hysteresis, and delayed exit decisions. , 2003, The Journal of applied psychology.

[40]  D. Kahneman,et al.  Delusions of success. How optimism undermines executives' decisions. , 2003, Harvard business review.

[41]  Geoff Walsham,et al.  Interpreting Information Systems in Organizations , 1993 .

[42]  Charles H. Schwenk.  Information, Cognitive Biases, and Commitment to a Course of Action , 1986 .

[43]  Kweku Ewusi-Mensah,et al.  Critical issues in abandoned information systems development projects , 1997, CACM.

[44]  Russell A. Eisenstat,et al.  The Critical Path to Corporate Renewal , 1990 .