Escalation and de-escalation of commitment: A commitment transformation analysis of an e-government project

Information Systems Journal

Volumn 16, Issue 1, 2006, Pages 3-21

  Pan, Gary ^a   Pan, Shan L ^b   Newman, Michael ^c,d   Flynn, Donal ^e  

^a UNIVERSITY OF MELBOURNE   (Australia)

^b NATIONAL UNIVERSITY OF SINGAPORE   (Singapore)

^c UNIVERSITY OF MANCHESTER   (United Kingdom)

^d UNIVERSITY OF AGDER   (Norway)

^e UNIVERSITY OF MANCHESTER   (United Kingdom)

Author keywords

De escalation of commitment; E government project; Escalation of commitment; Lewin's change theory

Indexed keywords

EID: 33645118167     PISSN: 13501917     EISSN: 13652575     Source Type: Journal    
DOI: 10.1111/j.1365-2575.2006.00209.x     Document Type: Article

References (43)

1. Abdel-Hamid, T. & Madnick, S. (1991) Software Project Dynamics: an Integrated Approach. Prentice Hall, Englewood Cliffs, NJ, USA.
2. Barki, H., Rivard, S. & Talbot, J. (1993) Toward an assessment of software development risk. Journal of Management Information System, 10, 203-225.
3. Beer, M., Eisenstat, R. & Spector, B. (1990) The Critical Path to Corporate Renewal. Harvard Business School, Boston, MA, USA.
4. Beer, M. & Nohria, N. (2000) Breaking the Code of Change. HBS Press, Boston, MA, USA.
5. Brockner, J. (1992) The escalation of commitment to a failing course of action: toward theoretical progress. Academy of Management Review, 17, 39-61.
6. Drummond, H. (1995) De-escalation in decision making: a case of a disastrous partnership. Journal of Management Studies, 32, 265-281.
7. Drummond, H. (1996) The politics of risk: trials and tribulations of the Taurus project. Journal of Information Technology, 11, 347-357.
8. Ewusi-Mensah, K. & Przasnyski, Z. (1991) On information systems project abandonment: an exploratory study of organisational practices. MIS Quarterly, 15, 67-85.
9. Ford, J. & Backoff, R. (1988) Organizational change in and out of dualities and paradox. In: Paradox and Transformation, Quinn, E. & Cameron, K. (eds), pp. 81-121. Ballinger, Cambridge, MA, USA.
10. Ford, J. & Ford, L. (1994) Logics of identity, contradiction, and attraction in change. Academy Management Review, 19, 756-785.
11. Garland, H., Sandefur, C. & Rogers, A. (1990) De-escalation of commitment in oil exploration. When sunk costs and negative feedback coincide. Journal of Applied Psychology, 75, 721-727.
12. Grimley, D., Prochaska, J., Velicer, W., Biais, L. & DiClemente, C. (1994) The transtheoretical model of change. In: Changing the Self: Philosophies, Techniques, and Experiences, Brinthaupt, M. (ed.), pp. 201-207. State University, NY Press, New York, NY, USA.
13. Hendry, C. (1996) Understanding and creating whole organizational change through learning theory. Human Relations, 49, 621-641.
14. Heng, C., Tan, B. & Wei, K. (2003) De-escalation of commitment in software projects: who matters? what matters? Information and Management, 41, 99-110.
15. Huber, G. & Glick, W. (1993) Organizational Change and Redesign. Oxford University Press, New York, NY, USA.
16. Keil, M. (1995) Pulling the plug: software project management and the problem of project escalation. MIS Quarterly, 19, 421-447.
17. Keil, M., Mixon, R., Saarinen, T. & Tuunainen, V. (1995) Understanding running away information technology projects: results from an international research program based on escalation theory. Journal of Management Information Systems, 11, 67-87.
18. Keil, M. & Robey, D. (1999) Turning around troubled software projects: an exploratory study of the de-escalation of commitment to failing courses of action. Journal of Management Information Systems, 15, 63-87.
19. Keil, M. & Robey, D. (2001) Blowing the whistle on troubled software projects. Communications of the ACM, 44, 87-93.
20. Klein, H. & Myers, M. (1999) A set of principles for conducting and evaluating interpretive field studies in information systems. MIS Quarterly, 23, 67-94.
21. Lewin, K. (1951) Field Theory in Social Science. Harper & Row, New York, NY, USA.
22. Mähring, M., Holmström, J., Keil, M. & Montealegre, R. (2004) Trojan actor-networks and swift translation: bringing actor-network theory to IT project escalation studies. Information Technology and People, 17, 210-238.
23. 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, Atlanta, Georgia, 18-19 October.
24. Marshak, R. (1993) Lewin meets Confucius: a review of the OD model of change. Journal of Applied Behaviour Science, 29, 393-415.
25. Montealegre, R. & Keil, M. (2000) De-escalating information technology projects: lessons from the Denver international airport. MIS Quarterly, 24, 417-447.
26. Newman, M. & Sabherwal, R. (1996) Determinants of commitment to information systems development: a longitudinal investigation. MIS Quarterly, 20, 23-54.
27. Pan, G., Pan, S., Newman, M. & Flynn, D. (2004) Unfreezing-changing- refreezing of actors' commitment: the transition from escalation to de-escalation of commitment to information technology projects. ECIS 2004: The 12th European Conference on Information Systems, Turku, Finland, June.
28. Prochaska, J., DiClemente, C. & Norcross, J. (1992) In search of how people change: applications to addictive behaviours. American Psychology, 47, 1102-1114.
29. Ross, J. & Staw, B. (1986) Expo 86: an escalation prototype. Administrative Science Quarterly, 31, 274-297.
30. Ross, J. & Staw, B. (1993) Organizational escalation and exit: lessons from the Shoreham Nuclear Power Plant. Academy of Management Journal, 36, 701-732.
31. Royer, I. (2003) Why bad projects are so hard to kill? Harvard Business Review, February, 49-56.
32. Sabherwal, R., Sein, M. & Marakas, G. (2002) Escalating commitment to information system projects: findings from two simulated experiments. Information and Management, 2032, 1-18.
33. Sauer, C., Liu, L. & Johnston, K. (1999) Enterprise-level project management capabilities: a comparison of the construction and IT services Industries. International Conference on Information Systems (ICIS), Charlotte, NC, USA.
34. Schein, E. (1988) Organizational Psychology. Prentice Hall, Eaglewood Cliffs, NJ, USA.
35. Schein, E. (1996) Kurt Lewin's change theory in the field and in the classroom: notes toward a model of managed learning. System Practice, 9, 27-47.
36. Shepherd, D. (2003) Learning from business failure: propositions for grief recovery for the self-employed. Academy of Management Review, 28, 318-328.
37. Spreitzer, G. & Quinn, R. (1996) Empowering middle managers to be transformational leaders. Journal of Applied Behavioural Science, 32, 237-261.
38. Standish Group Inc. (2003) CHAOS: a recipe for success. [WWW document]. URL http://www.standishgroup.com (accessed 25 May 2004).
39. Staw, B. & Ross, J. (1987) Behaviour in escalation situations: antecedents, prototypes, and solutions. In: Research in Organizational Behaviour, Cummings, T. & Staw, B. (eds), pp. 39-78. JAI Press Inc., Greenwich, CT, USA.
40. Teger, A. (1980) Too Much Invested to Quit. Pergamon, New York, NY, USA.
41. Wastell, D., Kawalek, P. & Newman, M. (2003) Plus Ca change: defensive translations and resistance to IT-enabled change in local government. Proceedings of European Conference of Information Systems, Naples, Italy.
42. Weick, K. & Quinn, R. (1999) Organizational change and development. Annual Review Psychology, 50, 361-386.
43. Zmud, R. (1980) Management of large software efforts. MIS Quarterly, 4, 45-55.