PROFILE #0012 · Microsoft First-Party Products
Company X - Microsoft Dynamics GP
A UK furniture manufacturer selected Microsoft Dynamics GP to replace inefficient legacy systems, but stakeholder conflict, changing requirements, and a major functional mismatch led the company to abandon the ERP project before implementation was completed.
- Status
- Abandoned
- Year
- 2006
- Founded
- N/A
- Funding
- Private company
The Idea
The company was a UK manufacturer specializing in storage furniture for the healthcare industry. It designed, supplied, and installed storage furniture as well as third-party products used to equip hospital rooms.
By 2004, the company’s information systems were becoming a significant operational problem. Business processes were inefficient, employees were frustrated, and much of the company’s work was being managed through Microsoft Excel.
The company evaluated different approaches, including a best-of-breed software strategy and an integrated ERP platform. After attending IT exhibitions and reviewing several products, management selected Microsoft Dynamics GP.
A contract to implement Dynamics GP was signed in 2005. An external consultant prepared an implementation plan, and a dedicated project manager was subsequently brought in to lead the implementation.
The Rise and Fall
The implementation encountered problems almost immediately.
The project team discovered that the modules originally selected did not adequately reflect the requirements of all business functions. Some departments had been insufficiently involved during the earlier selection and planning stages, which meant that important requirements were discovered only after the project had already started.
One of the most significant issues concerned the company’s product configuration requirements.
The manufacturer produced storage cabinets with few limitations on dimensions and specifications. According to the case study, Dynamics GP did not provide the required product configurator functionality out of the box.
Several possible solutions were discussed, including developing a bespoke configuration system, using another existing system, or integrating a third-party product.
At the same time, requirements continued to change and the estimated cost of the implementation increased.
The situation also exposed disagreements among stakeholders. Some participants who had previously opposed the ERP approach used the emerging functional and cost problems to question whether the project should continue.
The implementation never progressed beyond the early configuration stage.
In April 2006, approximately six months after the project-management team became involved, the company decided to abandon the ERP adoption.
Why It Failed
The research behind this case concluded that the fundamental problems were organizational and human rather than purely technical.
Several factors contributed to the abandonment:
-
Insufficient stakeholder alignment: Important business functions were not adequately represented during the earlier planning and selection process.
-
Requirements changed after selection: Once additional departments became involved, the organization discovered that the selected modules did not fully fit its business requirements.
-
Major functional mismatch: The company’s highly configurable storage-furniture business required product-configuration capabilities that Dynamics GP did not provide sufficiently for its needs.
-
Customization pressure: Because the standard functionality did not fit the business, several modification and integration options had to be considered.
-
Rising cost: Changes in requirements and the proposed solutions increased the expected project cost and caused management to question the business case.
-
Stakeholder politics: Disagreement between groups that supported and opposed the ERP strategy was not adequately managed before and during the implementation.
The researchers concluded that the technical problems were partly consequences of earlier organizational problems. Poor stakeholder alignment contributed to incomplete requirements, which contributed to the mismatch between the selected ERP system and the company’s actual business needs.
Lesson: ERP selection should not be treated as simply choosing a software product. The organization must establish stakeholder alignment, understand its critical business processes, and validate the fit of the selected system before committing to implementation.
This case is particularly relevant to manufacturing ERP projects. A system can appear suitable during a product demonstration while still failing to support a company’s most important competitive processes.
The deeper lesson is that a functional gap discovered before implementation may be manageable; the same gap discovered after contractual commitment and project mobilization can become a reason to abandon the entire initiative.
Sources
- Owens, J. D. & Dawson, J., “Consequences Of Failing to Align Key Stakeholders in an ERP Implementation: A UK Manufacturing Case Company,” in Strategy-Technology Alignment: Deriving Business Value from ICT Projects, 2011. The study documents the UK furniture manufacturer’s Microsoft Dynamics GP implementation and its abandonment in April 2006: ResearchGate
- Owens, J. D. & Dawson, J., “The Underlying Test: Human, Organisational and Technical Considerations adjoined with Critical Success Factors when implementing ERP: A Case Study of a UK SME”: ResearchGate