Escalation and de-escalation of commitment to information systems projects: Insights from a project evaluation model

We view escalation and de-escalation of commitment as processes involving recurring instances of approach-avoidance conflict. This paper outlines an approach-avoidance process model for describing and analyzing escalation and de-escalation of commitment in information systems projects. In the model, the sequential mapping of project events is integrated with a model of approach-avoidance conflict that identifies periods of gradual evolution at two separate levels of social analysis (project and work) that are punctuated by sudden, revolutionary periods of rapid change. By conceiving the processes of commitment escalation and de-escalation as sequences of events involving approach-avoidance conflicts, researchers may develop a deeper understanding of how and why projects escalate and de-escalate. Practitioners can also utilize the model in postmortem analyses of projects which have faced escalation to diagnose the issues surrounding the escalation and devise useful de-escalation strategies for future project development. The model is developed and illustrated with a case study that exhibits both project escalation and de-escalation conditions.

[1]  M. C. Jensen,et al.  Harvard Business School; SSRN; National Bureau of Economic Research (NBER); European Corporate Governance Institute (ECGI); Harvard University - Accounting & Control Unit , 1976 .

[2]  Zahir Irani,et al.  Information systems evaluation: navigating through the problem domain , 2002, Inf. Manag..

[3]  Daniel Robey,et al.  Sequential patterns in information systems development: an application of a social process model , 1996, TOIS.

[4]  Helga Drummond,et al.  Is Escalation Always Irrational? , 1998 .

[5]  KeilMark,et al.  De-escalating information technology projects , 2000 .

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

[7]  Linda S. Lotto.  Qualitative Data Analysis: A Sourcebook of New Methods , 1986 .

[8]  Joan CheneyMann,et al.  Preventing Runaway IT Projects: Protecting Auditors from Entrapment , 2003, AMCIS.

[9]  Michael G. Bowen.  The Escalation Phenomenon Reconsidered: Decision Dilemmas or Decision Errors? , 1987 .

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

[11]  Kuldeep Kumar,et al.  Post implementation evaluation of computer-based information systems: current practices , 1990, Commun. ACM.

[12]  Torgeir Dingsøyr,et al.  Postmortem: Never Leave a Project without It , 2002, IEEE Softw..

[13]  G. Northcraft,et al.  Opportunity costs and the framing of resource allocation decisions , 1986 .

[14]  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..

[15]  Gary S. C. Pan,et al.  Escalation and de-escalation of commitment to information systems projects: an approach-avoidance perspective , 2004 .

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

[17]  Gary S. C. Pan,et al.  Why Information Systems Project Postmortems Fail: An Attribution Perspective Based on a Case Study Analysis , 2003, ICIS.

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

[19]  Mark Keil,et al.  Information Technology Project Escalation: A Process Model , 2008, Decis. Sci..

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

[21]  K. Eisenhardt.  Building theories from case study research , 1989, STUDI ORGANIZZATIVI.

[22]  A. Pettigrew.  Longitudinal Field Research on Change: Theory and Practice , 1990 .

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

[24]  Gregory Rowe,et al.  Escalation in Decision Making: The Tragedy of Taurus , 1997 .

[25]  C. Gersick.  REVOLUTIONARY CHANGE THEORIES: A MULTILEVEL EXPLORATION OF THE PUNCTUATED EQUILIBRIUM PARADIGM , 1991 .

[26]  Daniel Robey,et al.  A Dual-Motor, Constructive Process Model of Organizational Transition , 2004 .

[27]  Alison Wolf,et al.  Contemporary Sociological Theory: Expanding the Classical Tradition , 1986 .

[28]  Shan Ling Pan,et al.  De-escalation of commitment to information systems projects: a process perspective , 2004, J. Strateg. Inf. Syst..

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

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

[31]  Rajiv Sabherwal,et al.  An Empirical Taxonomy of Implementation Processes Based on Sequences of Events in Information System Development , 1993 .

[32]  A. Pettigrew.  Context and Action in the Transformation of the Firm , 1987 .

[33]  Frank F. Land,et al.  Moving IS evaluation forward: learning themes and research issues , 1999, J. Strateg. Inf. Syst..

[34]  Charles I. Stubbart,et al.  The Deceptive Allure of Stage Models of Strategic Processes , 1999 .

[35]  W. Firestone,et al.  Multisite Qualitative Policy Research: Optimizing Description and Generalizability , 1983 .

[36]  Joel Brockner,et al.  Factors affecting entrapment in waiting situations: The Rosencrantz and Guildenstern effect. , 1975 .

[37]  Joel Brockner,et al.  Factors Affecting Entry into Psychological Traps , 1980 .

[38]  B. M. Staw.  The Escalation of Commitment To a Course of Action , 1981 .

[39]  H. Klein,et al.  Information systems development as social action: Theoretical perspective and practice , 1991 .

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

[41]  Zahir Irani,et al.  The Propagation of Technology Management Taxonomies for Evaluating Investments in Information Systems , 2000, J. Manag. Inf. Syst..

[42]  Daniel Robey,et al.  A Social Process Model of User-Analyst Relationships , 1992, MIS Q..

[43]  Steve Smithson,et al.  Information systems evaluation as an organizational institution – experience from a case study , 2003, Inf. Syst. J..

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