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

European Journal of Operational Research

Volumn 173, Issue 3, 2006, Pages 1139-1160

  Pan, Shan Ling ^a   Pan, Gary S C ^b   Newman, Michael ^c   Flynn, Donal ^d  

^a NATIONAL UNIVERSITY OF SINGAPORE   (Singapore)

^b UNIVERSITY OF MELBOURNE   (Australia)

^c UNIVERSITY OF MANCHESTER   (United Kingdom)

^d UNIVERSITY OF MANCHESTER   (United Kingdom)

Author keywords

Approach avoidance theory; Case study; Escalation and de escalation of commitment to information system projects; Project evaluation model

Indexed keywords

MATHEMATICAL MODELS; PROJECT MANAGEMENT; SOCIAL ASPECTS;

APPROACH-AVOIDANCE THEORY; CASE STUDY; ESCALATION AND DE-ESCALATION OF COMMITMENT TO INFORMATION SYSTEM PROJECTS; PROJECT EVALUATION MODEL;

MANAGEMENT INFORMATION SYSTEMS;

EID: 33744968621     PISSN: 03772217     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.ejor.2005.07.009     Document Type: Article

References (46)

1. Abdel-Hamid T., and Madnick S. The elusive silver lining: How we fail to learn from software development failures. Sloan Management Review 32 1 (1990) 39-49
2. Birk A., Dingsoyr T., and Stalhane T. Post-mortem: Never leave a project without it. IEEE Software May/June (2002) 43-45
3. Bowen M. The escalation phenomenon reconsidered: Decision dilemmas or decision errors. Academy of Management Review 12 1 (1987) 52-66
4. Brockner J., Shaw M., and Rubin J. Factors affecting withdrawals from an escalating conflict: Quitting before it's too late. Journal of Experimental Social Psychology 15 (1979) 492-503
5. Brockner J., and Rubin J. Entrapment in Escalating Conflicts: A Social Psychological Analysis (1985), Springer-Verlag, New York
6. Conlon D., and Garland H. The role of project completion information in resource allocation decisions. Academy of Management Journal 36 2 (1993) 402-413
7. Cule P., and Robey D. A dual-motor, constructive process model of organizational transition. Organizational Studies 25 2 (2004) 229-260
8. Drummond H. Escalation in Decision-Making: The Tragedy of Taurus (1996), Oxford University Press, UK
9. Drummond H. Is escalation always irrational?. Organizational Studies 19 6 (1998) 911-929
10. Eisenhardt K. Building theories from case study research. Academy of Management Review 14 4 (1989) 532-550
11. Farbey B., Land F., and Targett D. Moving IS evaluation forward: Learning themes and research issues. Journal of Strategic Information Systems 8 (1999) 189-207
12. Garland H., Sandefur C., and Rogers A. De-escalation of commitment in oil exploration: When sunk costs and negative feedback coincide. Journal of Applied Psychology 75 6 (1990) 721-727
13. Gersick C. Revolutionary change theories: A multilevel exploration of the punctuated equilibrium paradigm. Academy of Management Review 16 1 (1991) 10-36
14. Herriott R., and Firestone W. Multisite qualitative policy research: optimizing description and generalizability. Educational Researcher 12 (1983) 14-19
15. Hirschheim R., Klein H., and Newman M. Information systems development as social action: Theoretical perspective and practice. Omega 19 (1991) 587-608
16. Irani Z. Information systems evaluation: Navigating through the problem domain. Information and Management 40 (2002) 11-24
17. Irani Z., and Love P. The propagation of technology management taxonomies for evaluating investments in information systems. Journal of Management Information Systems 17 3 (2001) 161-177
18. Jensen M., and Meckling W. Theory of the firm: Managerial behavior, agency costs and ownership structure. Journal of Financial Economics 3 (1976) 305-360
19. Keil M. Pulling the plug: Software project management and the problem of project escalation. MIS Quarterly 19 4 (1995) 421-447
20. Keil M., and Robey D. Turning around troubled software projects: An exploratory study of the deescalation of commitment to failing courses of action. Journal of Management Information Systems 15 4 (1999) 63-87
21. Keil M., and Robey D. Blowing the whistle on troubled software projects. Communications of the ACM 44 4 (2001) 87-93
22. Keil M., Mann J., and Rai A. Why software projects escalate: An empirical analysis and test of four theoretical models. MIS Quarterly 24 4 (2000) 631-664
23. Klein H., and Myers M. A set of principles for conducting and evaluating interpretive field studies in information systems. MIS Quarterly 23 1 (1999) 67-94
24. Kumar K. post-implementation evaluation of computer-based information systems. Communications of the ACM 33 2 (1990) 203-212
25. Lyytinen, K., Newman, M., submitted for publication. Punctuated equilibrium, process models and information systems evolution: toward a social-technical process analysis.
26. Mähring, M., Keil, M., 2003. Information technology project escalation: A process model. Proceedings of the Eighth Annual Informs Conference on Information Systems and Technology, October 18-19, Atlanta, Georgia.
27. Mann, J., 2003. "Preventing Runaway IT Projects: Protecting Auditors from Entrapment," The Proceedings of Americas Conference on Information Systems, 4-5 August, Tampa, Florida.
28. Miles M., and Huberman A. Qualitative Data Analysis: A Sourcebook of New Methods (1994), Sage, Beverly Hills, CA
29. Montealegre R., and Keil M. De-escalating information technology projects: Lessons from the Denver International Airport. MIS Quarterly 24 3 (2000) 417-447
30. Newman M., and Robey D. A social process model of user-analyst relationships. MIS Quarterly 16 2 (1992) 249-266
31. Newman M., and Sabherwal R. Determinants of commitment to information systems development: A longitudinal investigation. MIS Quarterly 20 1 (1996) 23-54
32. Northcraft B., and Neale M. Opportunity costs and the framing of resource allocation decision. Organizational Behavior and Human Decision Processes 37 (1986) 348-356
33. Pan, G., 2004. Escalation and de-escalation of commitment to information systems project: An approach-avoidance perspective. An unpublished Ph.D. thesis, University of Manchester, UK.
34. Pan, G., Flynn, D., 2003. Why information systems project post-mortems fail: An attribution perspective based on a case-study analysis. In: The Proceedings of International Conference on Information Systems, 16-19 December, Seattle, US.
35. Pan, G., Pan, S., Flynn, D., in press. De-escalation of commitment to information systems projects: A process perspective. Journal of Strategic Information Systems.
36. Pettigrew A. Context and action in the transformation of the firm. Journal of Management Studies 24 (1987) 649-670
37. Pettigrew A. Longitudinal field research on change: Theory and practice. Organization Science 1 3 (1990) 267-292
38. Royer, I., 2002. Escalation in organizations: The Role of collective belief. Working Paper, Universite Paris, Dauphine, Presented at the Academy of Management Meeting, Denver, CO.
39. Rubin J., and Brockner J. Factors affecting entrapment in waiting situations: The Rosencrantz and Guildenstern effect. Journal of Personality and Social Psychology 31 (1975) 1054-1063
40. Rubin J., Brockner J., Small-Weill S., and Nathanson S. Factors affecting entry into psychological traps. Journal of Conflict Resolution 25 (1980) 405-426
41. Serafeimidis V., and Smithson S. Information systems evaluation as an organizational institution-experience from a case study. Information Systems Journal 13 (2003) 251-274
42. Staw B. The escalation of commitment to a course of action. Academy of Management Review 6 4 (1981) 577-587
43. Staw B., and Ross J. Understanding escalation situations: Antecedents, prototypes, and solutions. In: Staw B.M., and Cummings L.L. (Eds). Research in Organizational Behavior 9 (1987), JAI Press, Greenwich, CT 39-78
44. Stubbart C., and Smalley R. The Deceptive Allure of Stage Models of Strategic Processes. Journal of Management Inquiry 8 3 (1999) 273-287
45. Wallace R., and Wolf A. Contemporary Sociological Theory: Expanding the Classical Tradition. fifth ed. (1999), Pearson Education, Essex, UK
46. Whyte G. Escalating Commitment to a Course of Action: A Reinterpretation. Academy of Management Review 11 2 (1986) 311-321