ERP Modernization: Lessons from Projects That Succeeded and Those That Did Not

Enterprise resource planning system implementations are among the highest-risk transformation projects an organization can undertake. Hundreds of millions of dollars have been spent on enterprise resource planning projects that delivered disappointing results. Yet other organizations have completed successful enterprise resource planning modernizations that delivered the expected business outcomes on time and within budget. The difference is not usually the quality of the vendor or the sophistication of the technology. The difference is the discipline of the implementation approach. Successful enterprise resource planning projects follow four principles that unsuccessful projects neglect.

Principle One: Define Business Outcomes Before Vendor Selection

The most common failure mode in enterprise resource planning projects is selecting the vendor first and then trying to figure out what business outcomes the new system will enable. This approach is backwards. The organization should define clear business outcomes first, evaluate how different vendors support those outcomes, and then select the vendor that best fits the desired business model.

A manufacturing organization that wants to implement enterprise resource planning should start with the question: what do we want our supply chain to look like in three years? How do we want to plan demand? How do we want to manage inventory? How do we want to collaborate with suppliers? What visibility do we want into factory floor execution? Once those questions are answered, the organization can evaluate which enterprise resource planning system will best support that operating model.

Without clear business outcomes defined first, the organization will be tempted to select the system and then try to change the business model to fit the system. This often means accepting compromises that are not in the organization’s best interest. The selected system handles demand planning differently than you wanted but you will adapt your process to the system. The system enforces monthly closing cycles but you wanted weekly cycles, but you will work with the constraints of the system. Over time these small compromises accumulate and the system enables a less effective operating model than you should have designed for.

The discipline of defining business outcomes first forces the organization to think clearly about what they are trying to achieve before technology constraints limit the possibilities.

This principle applies to each major module in the enterprise resource planning system. For the financial management module, define what financial reporting you want to produce, how frequently, with what level of detail. For the supply chain module, define your demand planning approach and inventory management strategy. For the manufacturing module, define your production planning and scheduling approach. Define these outcomes in business terms, not in system terms. Then evaluate how different systems support those outcomes.

Principle Two: Involve Users Early and Throughout Implementation

Successful enterprise resource planning projects involve business users early in the design process and maintain that involvement throughout implementation. User involvement is not a nice-to-have. It is a critical success factor. Users understand the current business processes, the constraints that the processes must operate within, and the gaps between what the system is being asked to do and what the business actually needs.

Projects that isolate the implementation team from business users, that treat user input as optional, or that design the system primarily based on vendor recommendations tend to produce systems that do not match the way the business actually operates. When the system goes live, users discover that the system does not handle the edge cases that happen regularly in the business. The system assumes a process flow that does not match what actually happens. The data required to operate the system is not available in the form the system expects.

User involvement should include three mechanisms: first, key users from each business unit should be part of the core implementation team, making design decisions alongside the systems integrator; second, regular design review sessions should involve business users who are not on the core team, testing whether the design makes sense in practice; third, detailed process redesign workshops should involve the people who actually execute the processes, understanding their constraints and requirements.

The power users who emerge during implementation become the foundation for adoption and support after go-live. If those power users have been involved since the beginning and have influenced the design, they understand the system and are invested in its success. If power users are brought in late, after the design is largely complete, they are more likely to resist or struggle with adoption because they do not feel ownership of the design.

Principle Three: Manage Scope with Ruthless Discipline

Enterprise resource planning projects fail frequently because scope expands beyond what can be delivered effectively. The organization starts the project focused on specific business outcomes. As the project progresses, different parts of the organization identify additional capabilities they want included. The Chief Marketing Officer wants the enterprise resource planning system to support the company website. The Chief Information Officer wants the enterprise resource planning system to handle cloud infrastructure management. The Vice President of Human Resources wants enhanced workforce management capabilities that were not part of the original design.

Each of these additional requests is reasonable on its own merits. But added together they expand the project scope, delay the implementation, increase costs, and reduce the ability of the team to deliver the original business outcomes effectively. The single most important discipline in enterprise resource planning implementation is saying no to scope expansion.

The enterprise resource planning system is not the organization’s technology platform for everything. It is a focused system designed to support specific business outcomes. Everything else can be addressed in future phases.

Successful enterprise resource planning projects establish a change control process that is understood by all stakeholders. Any request to change scope is reviewed against the original business outcomes and the project timeline. Most requests are deferred to a future phase or addressed through alternative solutions that do not require expanding the core enterprise resource planning scope.

Deferring features is not a failure. It is the path to successful delivery. The organization that successfully delivers the core enterprise resource planning functionality on time and within budget has a much better platform for adding additional capabilities later than the organization that tries to do everything in one implementation and either fails to complete the project or completes it late and over budget.

Principle Four: Treat Implementation as Organizational Change

Many enterprise resource planning implementations treat the project as a technology deployment. Code is written, data is migrated, systems are tested, and then the system goes live. What is often missing is rigorous attention to organizational change management. The system goes live and users struggle because they have not been prepared for the change.

Successful implementations recognize that enterprise resource planning modernization is fundamentally an organizational change project. The system will change how work is performed. It will change how information is accessed. It will change how decisions are made. It will change who needs to know what information and when. Preparing the organization for these changes is as important as preparing the system.

This means:

Extensive training that goes beyond system navigation and includes training in the new business processes that the system enables

Process redesign that prepares the organization to work in the new way, not just learning to operate the new system

Communications that help people understand why the change is being made and how it will affect their work

Support structures including power users, help desk, and process consultants to assist people as they adapt to the new system

Time for stabilization after go-live, recognizing that productivity will be disrupted for some period as people learn to work in the new way

Organizations that treat the technology deployment as secondary to the organizational change management tend to achieve better adoption rates, faster time to benefit realization, and higher overall success rates. Organizations that focus primarily on the technology and minimize the change management discipline struggle with adoption and realize much slower value from the investment.

The Implementation Timeline and Phasing

Successful enterprise resource planning implementations recognize that trying to change everything at once is too risky. A phased approach allows each phase to stabilize before the next phase is introduced. This reduces risk, allows the organization to focus support resources effectively, and enables learning from each phase to inform subsequent phases.

A typical enterprise resource planning modernization might be structured as:

Phase one: Financial management and shared services, establishing the core data integrity and control structure

Phase two: Supply chain and procurement, leveraging the financial foundation from phase one

Phase three: Manufacturing and operations, now with visibility into procurement and financial impact

Phase four: Additional modules and enhanced capabilities, built on the foundation of the first three phases

This phasing allows the organization to extract value from each phase before committing to the next. It allows business users in later phases to learn from the experiences of earlier phases. It reduces the risk that a major problem in phase one will propagate through all four phases. It provides opportunities to adjust the implementation approach based on what was learned in earlier phases.

The Cost of Failure and the Value of Success

Failed enterprise resource planning implementations consume enormous amounts of capital and management attention. They delay other technology investments. They distract the organization from the core business. They create skepticism about major technology initiatives that makes future projects harder. The cost of a failed or significantly delayed enterprise resource planning project is not just the direct cost of the project itself. It is the opportunity cost of delayed business improvements and the erosion of confidence in technology leadership.

Successful enterprise resource planning implementations deliver significant value. The organization operates with better visibility into financial performance and can make decisions faster. Supply chain management becomes more efficient. Inventory is optimized. Costs are reduced. The business can respond more quickly to market changes. The value of a successful implementation compounds over time as the organization fully realizes the benefits and builds on the foundation.

The difference between success and failure is usually not the quality of the enterprise resource planning system selected. It is the discipline of the implementation approach. Organizations that define business outcomes first, that involve users throughout implementation, that manage scope with ruthless discipline, and that treat the project as organizational change achieve success. Organizations that skip any of these principles tend to struggle.

Valukoda helps growing businesses make smarter technology decisions. Whether you need strategic IT leadership, managed services, or a security program built from the ground up, we bring decades of CIO and CISO experience to your team. Schedule a conversation or call us at 888.380.7212.