Welcome to the InfoSci Platform
Reference Hub4
Analyzing Different Strategies to Enterprise System Adoption: Reengineering-Led vs. Quick-Deployment

Analyzing Different Strategies to Enterprise System Adoption: Reengineering-Led vs. Quick-Deployment

Sue Newell, Jay G. Cooprider, Gary David, Linda F. Edelman, Traci A. Logan
Copyright: © 2005 |Volume: 1 |Issue: 2 |Pages: 16
ISSN: 1548-1115|EISSN: 1548-1123|ISSN: 1548-1115|EISBN13: 9781615202850|EISSN: 1548-1123|DOI: 10.4018/jeis.2005040101
Cite Article Cite Article

MLA

Newell, Sue, et al. "Analyzing Different Strategies to Enterprise System Adoption: Reengineering-Led vs. Quick-Deployment." IJEIS vol.1, no.2 2005: pp.1-16. http://doi.org/10.4018/jeis.2005040101

APA

Newell, S., Cooprider, J. G., David, G., Edelman, L. F., & Logan, T. A. (2005). Analyzing Different Strategies to Enterprise System Adoption: Reengineering-Led vs. Quick-Deployment. International Journal of Enterprise Information Systems (IJEIS), 1(2), 1-16. http://doi.org/10.4018/jeis.2005040101

Chicago

Newell, Sue, et al. "Analyzing Different Strategies to Enterprise System Adoption: Reengineering-Led vs. Quick-Deployment," International Journal of Enterprise Information Systems (IJEIS) 1, no.2: 1-16. http://doi.org/10.4018/jeis.2005040101

Export Reference

Mendeley
Favorite Full-Issue Download

Abstract

The literature on enterprise system (ES) adoption suggests that companies use different strategies for implementation — some opting to radically reengineer business processes up-front, while others employ a quick-deployment strategy on the assumption that organizational change will follow. In this article we explore how these two different strategies play out in practice and also consider the factors that influence which approach is taken. We use exploratory data from interviews with consultants who have been involved in multiple ES implementations in external companies, as well as interviews with project members involved in an internal ES implementation. Analysis of the data suggests that some level of reengineering is an inevitable outcome of ES implementation. However, attempts to reengineer up-front is difficult and can be problematic. Much of this stems from how the ES is actually used versus its envisioned (or planned) use. The implications for post-implementation exploitation opportunities are explored.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.