Article2007

The Trouble With Enterprise Software

160 citations0/0 files storedDialnet (Universidad de la Rioja)

No readable copy stored yet — this record is metadata only.

No open-access location is known for this record yet.

Literature note Cite in a project Citation map

ERP Systems Implementation and Impact Information Technology Governance and Strategy Information Systems Theories and Implementation

Abstract

Drawing upon a wealth of data, informed experience and expert opinion ? from Thomas Friedman to Bjarne Stroustrup, from David Gelernter to Nicholas Carr ? the author builds a case that enterprise software in large organizations has not delivered on its promise to fully integrate and intelligently control complex business processes while remaining flexible enough to adapt to changing business needs. Instead, ERP systems ? including both software applications and the data they process ? are variegated patchworks, containing 50 or more databases and hundreds of separate software programs installed over decades and interconnected by idiosyncratic, Byzantine and poorly documented customized processes. To manage this growing complexity, IT departments have grown substantially: Today?s IT departments spend 70% to 80% of their budgets just trying to keep existing systems running. The research shows, says the author, that the typical IT structure is so dense and extensive that it?s often a miracle that it works at all. Enterprise systems that were supposed to streamline and simplify business processes instead have brought high risks, uncertainty and a deeply worrying level of complexity. Rather than agility, they have produced rigidity and unexpected barriers to change, a veritable glut of information containing myriad hidden errors and a cloud of questions regarding their overall benefits. How did this happen? Rettig points to the inherent limitations in the nature of software, the costs of implementation and the vagaries of data. Indeed, she offers, enterprise software may be just too complex to deliver on its promises. She also suggests that the next new thing ? service-oriented architecture (SOA) ? is not likely to fare much better, for many of the same reasons. There are no easy fixes, cautions Rettig, save a large dose of sobriety, clear-eyed analysis and emphasis on simplicity and efficiency.

Paper brief

Loading…

Cite this work

Citation unavailable for this work.

BibTeX RIS CSL-JSON

No public copy is stored for this record, so only the metadata is cited.

Citations in this library

Citation map →

Stored only when both papers are in the corpus — 160 citations exist upstream.

References

2005The World Is Flat: A Brief History of the Twenty-First Century 2002The critical success factors for ERP implementation: an organizational fit perspective 2006Enterprise Architecture As Strategy: Creating a Foundation for Business Execution 2004Does IT Matter? Information Technology and the Corrosion of Competitive Advantage 1992Mirror worlds, or, The day software puts the universe in a shoebox. . .: how it will happen and what it will mean 1998Beyond engineering: how society shapes technology 2001A Nation Transformed by Information

Cited by

2011A comprehensive study of the relationship between enterprise resource planning selection criteria and enterprise resource planning system success 2008Expectation and reality in ERP implementation: consultant and solution provider perspective 2017Developing organizational agility in product innovation: the roles of IT capability, KM capability, and innovative climate 2014How the effects of IT and knowledge capability on organizational agility are contingent on environmental uncertainty and information intensity 2016Design and evaluation of a gamified system for ERP training

Explore the map →

Papers that cite the same references — the relational fallback while embeddings are still backfilling.

Imported from OpenAlex (CC0) — nothing here is generated.