Strategies for Dealing with Drift during Implementation of ERP Systems

Abstract

Research on the relationship between Information Technology (IT) and organizations emphasizes the complexity of adaptation processes and the potential of drifting. Drifting means that an organization encounters unexpected circumstances that show the incompleteness and possible failure of an initial technological design without organizations having yet feasible alternatives. This conceptual and empirical paper investigates the origins and nature of drifting, and strategies for dealing with drift. Three strategies have been proposed to deal with drifting: control, incremental, and drift containment. We explore the third option that seems most realistic and relevant from an organizational point of view. We empirically investigated how drift containment could be accomplished in practice in a multi-site ERP implementation project. Our results suggest three phases of dealing with drift. Organizations must first recognize when drifting occurs. Next, they must develop a dual focus. On one hand, they must differentiate between a project’s overarching objectives (which remain relatively stable). On the other hand, they attend to and resolve their operational drifting experience. The dual focus thus means that while organizations stay focused on their objectives, they address the causes of drifting. During the final phase, lessons learnt during drifting resolution must be shared and applied to accelerate accomplishment of project objectives. Implications for research and practice are elaborated.

Cite this work

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

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

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