Advertisement

Information Systems Frontiers

, Volume 2, Issue 2, pp 213–232 | Cite as

Implementing Enterprise Resource Planning Systems: The Role of Learning from Failure

  • Judy E. Scott
  • Iris Vessey
Article

Abstract

ERP implementations remain problematic despite the fact that many of the issues are by now quite well known. In this paper, we take a different perspective from the critical success factors and risks approaches that are common in the information systems discipline to explain why ERP implementations fail. Specifically, we adapt Sitkin's theory of intelligent failure to ERP implementations resulting in a theory that we call “learning from failure.” We then examine from the viewpoint of this theory the details of two SAP R/3 implementations, one of which failed while the other succeeded. Although it is impossible to state, unequivocally, that the implementation that failed did so because it did not use the approach that was derived from the theory, the analysis reveals that the company that followed many of the tenets of the theory succeeded while the other did not.

enterprise systems enterprise resource planning systems ERP implementation organizational learning intelligent failure learning from failure 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Alschuler D, Dorin R. AcceleratedSAPWorks! An executive white paper, AberdeenGroup, June 1998, http://www.aberdeen.com.Google Scholar
  2. Ang K, Thong J, Yap C. IT implementation through the lens of organizational learning: A case of insuror. Eighteenth International Conference on Information Systems 1997.Google Scholar
  3. Argyris C. Strategy, Change and Defensive Routines. Boston: Pitman, 1985.Google Scholar
  4. Argyris C, Schon DA. Organizational Learning. Reading, MA: Addison-Wesley, 1978.Google Scholar
  5. Asbrand D. Peering across the abyss: Clothing and shoe companies cross the ERP chasm. Datamation Executive Diary: Part 3, January 1999.Google Scholar
  6. Attewell P. Technology diffusion and organizational learning: The case of business computing. Organization Science 1992;3:1-19.Google Scholar
  7. Bailey J. Trash haulers are taking fancy software to the dump: Allied waste, following waste management, to shed SAP's costly R/3. The Wall Street Journal June 9, 1999:B4.Google Scholar
  8. Bancroft N, Seip H, Sprengel A. Implementing SAP R/3: How to introduce a large system into a large organization. (2nd ed.) Manning Publications, 1998, Chapters 6, 7, and 11.Google Scholar
  9. Barki H, Rivard S, Talbot J. Toward an assessment of software development risk. Journal of Management Information Systems 1993;10(2):203-225.Google Scholar
  10. Block R. The Politics of Projects. Yourdon Press, Prentice-Hall, Chapter 1, 1983.Google Scholar
  11. Brown C, Vessey I. ERP Implementation Approaches: Towards a Contingency Framework. Research-in-Progress, Twentieth International Conference on Information Systems. Charlotte, 1999.Google Scholar
  12. Bulkeley WM. When things go wrong. The Wall Street Journal. November 18, 1996, R25.Google Scholar
  13. Caldwell B. Andersen sued on R/3. Information Week July 6, 1998.Google Scholar
  14. Champy J. Packaged systems: One way to force change. Computerworld December 22, 1997:61.Google Scholar
  15. Cliffe S. ERP implementation: How to avoid $100 million write-offs. Harvard Business Review January-February 1999:16-17.Google Scholar
  16. Computergram International FoxMeyer plus two sue Andersen for SAP snafus. Computergram International July 20, 1998.Google Scholar
  17. Davenport TH. Putting the enterprise into enterprise systems. Harvard Business Review July-August 1998:121-131.Google Scholar
  18. Deloitte Consulting, ERP's second wave: Maximizing the value of ERP-enabled processes, 1998.Google Scholar
  19. Dodgson M. Organizational learning: A review of some literatures. Organization Studies 1993;14(3):375-394.Google Scholar
  20. FinTimes SAP in $500m US lawsuit. Financial Times Surveys, September 2, 1998:2.Google Scholar
  21. Fiol C, Lyles M. Organizational Learning. Academy of Management Review 1985;10(4):803-813.Google Scholar
  22. Gable GG. A conversation with Tom Davenport. forthcoming: Journal of Global Information Management.Google Scholar
  23. Girard K, Farmer MA. Business software firms sued over implementation. CNET News.com November 3, 1999, http://news.cnet.com/news/0-1008-202-1428800.html.Google Scholar
  24. Hedberg B. How organizations learn and unlearn. In Nystrom PC & Starbuck WH (eds.), Handbook of Organizational Design. New York: Oxford University Press, 1981;1:3-27.Google Scholar
  25. Hoffman T. Software snafu triggers order delays, loss: Snap-On software leads to $50M dip. Computerworld News, July 6, 1998:6.Google Scholar
  26. Holland CP, Light B. A critical success factors model for ERP implementation. IEEE Software March/June, 1999:30-35.Google Scholar
  27. Huber G. Organizational learning: The contributing processes and literatures. Organization Science 1991;2(1):88-115.Google Scholar
  28. IW SAP Installation scuttled: Unisource cites internal problems for $168 M write-off. InformationWeek January 26, 1998.Google Scholar
  29. Jesitus J. Broken promises? FoxMeyer's project was a disaster.Was the company too aggressive or was it misled? Industry Week November 3, 1997:31-37.Google Scholar
  30. King J. Dell zaps SAP. Computerworld May 26, 1997:2.Google Scholar
  31. Kotter JP. Leading change: Why transformation efforts fail. Harvard Business Review 1995;73(2):59-67.Google Scholar
  32. Levitt B, March JG. Organizational Learning. In W.R. Scott & J. Blake (Eds.) Annual Review of Sociology 1988;14:319-340.Google Scholar
  33. LJX Files, The complaint in Brown v. Andersen Consulting, http://www.ljx.com/LJXfiles/bankruptcy/andersen.htmlGoogle Scholar
  34. Lyytinen K, Mathiassen L, Ropponen J. Attention shaping and software riskÐA categorical analysis of four classical risk management approaches. Information Systems Research 1998;9(3):233-255.Google Scholar
  35. Lounamaa PH, March JG. Adaptive coordination of a learning team. Management Science 1987;33:107-123.Google Scholar
  36. March JG. Exploration and Exploitation in Organizational Learning. Organization Science 1991;2(1):71-87.Google Scholar
  37. Markus ML, Benjamin RI. The magic bullet theory in IT-enabled transformation. Sloan Management Review Winter 1997; 38(2):55-68.Google Scholar
  38. Markus ML, Tanis C. The enterprise systems experience·from adoption to success. In Zmud RW (ed.), Framing the Domains of IT Research: Glimpsing the Future Through the Past. Cincinnati, OH: Pinnaflex Educational Resources, Inc., 2000.Google Scholar
  39. Nonaka I. A dynamic theory of organizational knowledge creation. Organization Science 1994;5(1):14-37.Google Scholar
  40. Osterland A. Blaming ERP, CFO Magazine, January 2000 (http://www.cfonet.com/Articles/CFO/2000/00Jablam.html)Google Scholar
  41. Pentland BT. Information systems and organizational learning: The social epistemology of organizational knowledge systems. Accounting, Management and Information Technologies 1995;5(1):1-21.Google Scholar
  42. Porter M, Millar V. How information gives you competitive advantage. Harvard Business Review 1985;63:149-160.Google Scholar
  43. Radosevich, Lynda, Quantum's leap. CIO February 15, 1997.Google Scholar
  44. Robey D, Wishart NA, Rodriguez-Diaz AG. Merging the metaphors for organizational improvement: Business process reengineering as a component of organizational learning. Accounting, Management and Information Technologies 1995;5(1):23-39.Google Scholar
  45. Ross J. Dow Corning Corporation (A): Business Processes and Information Technology, Center for Information Systems Research. Sloan School of Management, MIT. 1996a.Google Scholar
  46. Ross J. Dow Corning Corporation (B): Reengineering Global Processes. Center for Information Systems Research. Sloan School of Management, MIT. 1996b.Google Scholar
  47. Ross J. Dow Corning (C): Transforming the organization. Center for Information Systems Research. Sloan School of Management, MIT, 1999.Google Scholar
  48. Sauer C. Deciding the future for IS failures: Not the choice you might think. In Currie W and Galliers RG (eds.), Rethinking Management Information Systems: An Interdisciplinary Perspective. Oxford University Press, 1999.Google Scholar
  49. Scott JE, The FoxMeyer Drugs' bankruptcy: Was it a failure of ERP?. Proceedings of the Fifth Americas Conference on Information Systems. 1999:223-225.Google Scholar
  50. Scott JE, Vessey I. Toward a Multi-Level Theory of Risks in Enterprise Systems Implementations, Working paper, 2000.Google Scholar
  51. Senge PM. The Fifth Discipline: The Art and Practice of the Learning Organization. Doubleday, 1990.Google Scholar
  52. Sitkin SB. Learning through failure: The strategy of small losses. Research in Organizational Behavior 1992;14:231-266.Google Scholar
  53. Stedman C. Big-bang R/3 rollout forced compromises with business goals. Computerworld March 16, 1998;32(11):1, 97.Google Scholar
  54. Stein EW, Zwass V. Actualizing organizational memory with information systems. Information Systems Research 1995;6(2):85-117.Google Scholar
  55. Sumner M. Critical success factors in enterprise wide information management systems projects. Proceedings of the ACM-SIGCPR Conference 1999:297-303.Google Scholar
  56. Welti N. Successful SAP R/3 Implementation: Practical Management of ERP Projects. Addison-Wesley Longman Limited, 1999, Chapter 2.Google Scholar
  57. Willcocks LP, Griffiths C. Management and risk in major Information Technology Projects. In Willcocks LP, Feeny D, Islel G (eds.), Managing IT as a Strategic Resource. McGraw-Hill, Berkshire England, 1997:203-237.Google Scholar
  58. Williamson M. From SAP to `nuts!' Computerworld November 10, 1997;31,45:68-69.Google Scholar

Copyright information

© Kluwer Academic Publishers 2000

Authors and Affiliations

  • Judy E. Scott
    • 1
  • Iris Vessey
    • 2
  1. 1.College of Business AdministrationUniversity of ColoradoDenver
  2. 2.Department of Accounting and Information Systems, Kelley School of BusinessIndiana UniversityUSA

Personalised recommendations