Cited by 1,023ERP Systems Implementation and ImpactInformation Systems Theories and ImplementationInformation Technology Governance and Strategy

The DOI matches its Crossref record; 58 of the 64 references it cites were found in a registry or an index; none of the 3 sources its claims cite is checked for support yet.

Learning to Implement Enterprise Systems: An Exploratory Study of the Dialectics of Change

Open access
Robey, Daniel, Ross, Jeanne W., Boudreau, Marie-Claude·2002·Journal of Management Information Systems

Abstract

This paper reports on a comparative case study of 13 industrial firms that implemented an enterprise resource planning (ERP) system. It compares firms based on their dialectic learning process. All firms had to overcome knowledge barriers of two types: those associated with the configuration of the ERP package, and those associated with the assimilation of new work processes. We found that both strong core teams and carefully managed consulting relationships addressed configuration knowledge barriers. User training that included both technical and business processes, along with a phased implementation approach, helped firms to overcome assimilation knowledge barriers. However, all firms in this study experienced ongoing concerns with assimilation knowledge barriers, and we observed two different approaches to address them. In a piecemeal approach, firms concentrated on the technology first and deferred consideration of process changes. In a concerted approach, both the technology and process changes were undertaken together. Although most respondents clearly stated a preference for either piecemeal or concerted change, all firms engaged in practices that reflected a combination of these approaches.

Overview

AI snapshot

Written from the paper’s full text.

TL;DR

This comparative case study examines 13 North American manufacturing firms that implemented enterprise resource planning systems, using a dialectic learning lens to analyze how they overcame knowledge barriers. It distinguishes configuration and assimilation barriers, and contrasts piecemeal with concerted implementation approaches.

Key findings

  • Firms faced two main knowledge barriers: configuring the ERP package and assimilating new work processes. More successful firms managed consultants carefully and transferred external knowledge; less successful firms either ignored consultant advice or became overdependent, with one firm paying 60% of project cost to consultants.
  • Training budgets ranged from 1% to 20% of total project budget. More successful firms supplemented system training with education on new processes and change management, while incremental implementation helped users assimilate new work processes.
  • Eight firms used a piecemeal approach, implementing ERP before or separately from process reengineering, while five used a concerted approach, redesigning processes alongside ERP. Both groups ultimately had to change systems and processes together, and the distinction was clearer in stated philosophy than in practice; no evidence showed concerted approaches led to greater success.
  • Outcomes were mixed: positive impacts included supply chain efficiency, improved financial accounting, greater data visibility, and process-centered thinking; negative impacts included data inaccuracy, lost reporting capabilities, user resistance, strained customer relationships, and loss of skilled people. Most respondents said it was too early to tell ultimate benefits.

Methods

  • Comparative case study of 13 North American manufacturing firms or divisions that had completed a major ERP implementation from SAP, Oracle, Baan, or PeopleSoft. The original sample had 16 sites, but 3 had insufficient data; firms initially had to exceed $500 million in revenue, though this criterion was later relaxed.
  • One author interviewed 16 sites as part of a larger ERP study. The analysis used a dialectic process perspective, focusing on obstacles encountered during implementation and the mechanisms used to overcome them.
  • Firms were categorized by relative success in overcoming configuration and assimilation knowledge barriers, and by whether they followed piecemeal or concerted change processes.

Limitations

  • The paper states that many firms were still in post-implementation adjustment, most said it was too early to tell ultimate benefits, and the authors could not gauge ultimate success. It also notes that interviews with senior executives gave no direct access to situated learning, and that the study does not address whether ERP is an effective match for organizations or verify concerns about lost functionality.
  • Evident from the text: the sample is limited to 13 North American manufacturing firms or divisions, partly selected through sponsor and consulting contacts, which constrains generalizability. The data are retrospective interview accounts, and outcomes were unstable at the time of study, making causal or long-term conclusions difficult.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.1080/07421222.2002.11045713

Cites

58 of 58 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Verification

Claims the paper makes

50 Own result · 33 Own interpretation · 24 No basis given · 2 No full text of the sources · 2 Own method · 1 Sources not found · 1 Not checked yet

Show all 74 claims

  • It may state two separate claims as one. 30
  • Probably not a substantial claim. 12
  • The quote only partly states this claim. 2
39 of 39
  • The paper relies on this without support.

    ERP software packages are prepackaged and allow customization only through configuration tables that reflect business rules.

    “First, the software was prepackaged, allowmg for customizahon only through tables that the firm could configure m order to reflect its business rules.”
  • The paper relies on this without support.

    Replacing legacy systems with ERP disrupts processes built on those systems and replaces them with more standardized, crossfunctional processes.

    “Second, as firms replaced existing legacy systems with an ERP, they disrupted the processes that were built on those systems and replaced them with more standardized, crossftanctional processes.”
  • The paper relies on this without support.

    ERP tends to be associated with integrated, process-centered models of organization.

    “ERP tends to be associated with integrated, process-centered models of organization”
  • The paper relies on this without support.

    ERP systems typically require organizations to replace large portions of what they know, not only about technical infrastructures but also about business processes.

    “ERP systems typically require orgamzations to replace large portions of what they know, not only about technical mfrastructures but also about business processes.”
  • The paper relies on this without support.

    ERP technology is so new and complex that it is difficult for a company to embark on an ERP implementation without external knowledge.

    “Because HRP technology is so new and complex, it is difficult for a company to embark on such an endeavor without external knowledge.”
5 of 5

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Show all 64 references

Research works printed but not linked: 4

  1. [20]20. Koh, C, Soh, C, and Markus, M.L. "A Process Theory Approach to Analyzing ERP Implementation and Impacts: The Case of Revel Asia," Journal of Information Technology Cases and Applications, (2:1), 2000, 4-23.
  2. [24]24. Markus, M.L., Tanis, C, and van Fenema, "MultiSite ERP Implementations," Communications of the ACM, (43:4) 2000, 42^6.
  3. [26]26. Miles, M.B. and Huberman, A.M., Qualitative Data Analysis: An Expended Source Book, Second Edition, Sage, Thousand Oaks, CA, 1994.
  4. [50]50. Willcocks, L.P. and Sykes, R., "The Role of the CIO and IT Function in HRP," Communications of the ACM, (43:4), 2000, 32

Cited by

Sorted by citations

Items 501–600 of 1,018

Metadata

Authors
Robey, D., Ross, J. W., & Boudreau, M.-C.
Venue
Journal of Management Information Systems
Published
2002-07
Volume
19
Issue
1
Pages
17-46
ISSN
  • 0742-1222 (ISSN-L)
  • 1557-928X
OpenAlex
W2098925541
Cited by
1,023
References
64
Citations by year
2026: 5 · 2025: 6 · 2024: 11 · 2023: 16 · 2022: 18 · 2021: 15 · 2020: 20 · 2019: 36 · 2018: 25 · 2017: 37 · 2016: 45 · 2015: 65 · 2014: 62 · 2013: 80 · 2012: 59
FWCI
83.70
Type
journal article
Language
en
Open access
Locations
  • Journal of Management Information Systems (publishedVersion)
  • DSpace@MIT (Massachusetts Institute of Technology) (submittedVersion, cc-by-nc)
Topics
  • Social Sciences › Business, Management and Accounting › Management Information Systems › ERP Systems Implementation and Impact
  • Social Sciences › Business, Management and Accounting › Management Information Systems › Information Systems Theories and Implementation
  • Social Sciences › Business, Management and Accounting › Management Information Systems › Information Technology Governance and Strategy
Keywords
enterprise resource planning, ERP implementation, organizational learning, knowledge barriers, ERP configuration, workflow changes, consulting relationships, user training, phased implementation, industrial enterprises

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

A language model drew the claims from the paper on 2026-10-10, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).

A second model labelled each claim on 2026-10-10 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review