ERP Project Management: Why In-House Project Management Often Doesn’t Pay Off

Selecting and implementing an ERP system represents a fundamental change in how the entire company operates. It is not merely a matter of deploying a new information system, but rather involves changes to key processes—finance, production, logistics, planning, and the way people and responsibilities are managed.

Nevertheless, in practice, ERP projects are often managed primarily as technical or IT projects. The emphasis is placed on the system’s functionality and meeting the technical specifications, while the project’s business and strategic goals take a back seat.

Experience with ERP projects across both manufacturing and commercial companies shows that the success of a project is not determined by the ERP system itself, but by how the project is managed. It is the project management of the ERP project that determines whether the investment in ERP will actually pay off or end up as a costly compromise.

Where ERP projects most often go off the rails

ERP projects rarely fail because of the technology itself. The most common problems arise in the area of project management, and very similar scenarios tend to recur.

Typically, the scope of the project expands gradually without a systematic assessment of the impact on the budget and schedule. Changes are approved on an ad hoc basis, often without a clear decision from management and without assessing their value relative to the original project objectives. At the same time, responsibilities between the company and the ERP system vendor are not clearly defined, leading to ambiguities in both decision-making and implementation.

The result is a situation where the ERP project is formally complete, but:

• the costs exceed the original budget,
• the completion date will be significantly delayed,
• and the system does not support the objectives for which the ERP project was launched.

ERP Project Management as a Way to Protect a Company’s Investment

ERP project management is not merely an administrative function. It is a key tool for protecting the company’s investment and maintaining a balance between the scope, timeline, costs, and quality of the final solution.

The primary role of ERP project management is:

• connect the business, IT, and the ERP system vendor,
• manage changes and prioritize requests,
• identify and manage project risks in a timely manner,
• and systematically ensure that the project is focused on delivering tangible business benefits, not merely on technical completion.

ERP projects require specific expertise. A general understanding of project management is not enough. An ERP project manager must understand the company’s processes, how ERP systems work, data management, the role of key users, and the typical challenges that arise during ERP implementation across various industries.

Why project management by the contractor alone is not enough

ERP system vendors typically provide their own project managers, whose role is to oversee the delivery of the solution. This is a legitimate and necessary part of ERP implementation.

However, the role of the supplier’s project manager is naturally focused primarily on:

• delivery of the agreed scope,
• the technical functionality of the ERP system,
• meeting the agreed implementation deadlines.

Conversely, protecting the client’s business interests, assessing the impact of changes on project objectives, and verifying the actual benefits of the ERP project are not the project manager’s primary responsibilities. Thus, a natural conflict of interest arises in every ERP project, which—if not properly balanced—significantly increases the risk of a suboptimal outcome.

An Independent ERP Project Manager as a Key Element of Management

Independent ERP project management, provided by a consulting firm with no financial or technological ties to a specific ERP system or vendor, ensures a balanced approach to project management.

An independent ERP project manager represents the customer’s interests exclusively and ensures that the project is managed as a strategic business initiative.

In practice, this means:

• ongoing monitoring of the solution’s alignment with the original objectives of the ERP project,
• controlled approval of changes, including their impact on the budget and schedule,
• protection against uncontrolled expansion of the project scope,
• early escalation of issues while they are still resolvable.

As a result, management gains a realistic overview of the status of the ERP project and high-quality information for decision-making, rather than merely formal reports on milestone completion.

ERP Project Management as Part of the Results Guarantee

Companies often seek a “guarantee of success for their ERP project.” However, without high-quality project management, no such guarantee exists. Only a combination of experience, methodology, and independent project management makes it possible to manage risks systematically and prevent problems, rather than having to explain them after the fact.

ERP project management is not an additional cost. It is a safeguard against:

• uncontrolled cost growth,
• delays in ERP implementation,
• compromises in the quality of the solution,
• and, in extreme cases, even the need to reimplement the ERP system.

An ERP project managed by the company, not the system

If a company leaves the management of an ERP project entirely to the system vendor, it assumes risks that often do not become apparent until the system goes live.

Independent ERP project management helps keep the project under control from the initial decisions through go-live and subsequent stabilization. It ensures that the ERP system truly supports the business objectives for which it was implemented.