The Hardest ERP Decision Isn’t Technology, It’s Process Ownership

When executives begin discussing a new ERP system, the conversation usually starts with technology.

Which platform should we choose?
Should we move to the cloud?
What functionality do we need?

Don’t get it wrong, these are important questions, but in most ERP projects, they are not the ones you should focus on. The real complexity appears long before implementation begins. It surfaces when the organisation has to answer a far more difficult question:

Whose process becomes the standard?

Because ERP projects are not simply technology upgrades, they are organisational decisions about how the business will operate in the future. And that is where the real challenge begins.

ERP is About Logic

Modern ERP platforms are designed around standardised processes. Gone are the days of extensive customisation and the integration of various systems. Finance, procurement, order management, manufacturing, and HR, the system expects these processes to follow defined structures and logic.

That design is intentional. Standardising (and optimising while you are at it) processes is what allows organisations to:

• scale operations
• integrate across departments
• gain reliable reporting
• automate workflows
• reduce manual workarounds

But most organisations do not begin with a single standard way of working. Over time, different departments, business units, and regions develop their own processes. Sometimes this happens because of acquisitions, or teams solve problems in their own way, or because legacy systems forced certain behaviours.

As a result, what appears to be “one company” often operates as multiple process cultures. An ERP project brings those differences into the open.

The Moment When ERP Becomes Political

This is the point where ERP discussions shift from technical to organisational.

If three business units handle procurement differently, the new system will not support all three approaches. The organisation will need to define one way forward.

That raises questions such as:

• Should the procurement process follow the model used by the largest division?
• Should finance dictate the standard because of compliance requirements?
• Should the organisation adopt the ERP platform’s best-practice model instead?

None of these decisions is purely technical. They touch on ownership, influence, and control.

A process that becomes the enterprise standard often shapes reporting structures, operational responsibilities, and performance measurement. It determines how work flows across teams.

It is therefore not unusual for process discussions to become deeply debated.

From an executive perspective, it can feel surprising: Why is a system implementation creating so much tension? The answer is simple: ERP implementations expose how the organisation actually works.

Why Business Units Resist Standardisation

Resistance during ERP projects is often misunderstood as reluctance to adopt new technology. In reality, resistance usually comes from something deeper.

Business units have often spent years refining their own processes to suit their markets, customers, or operational realities. Those processes are familiar. Teams understand them. Performance targets are built around them.

When an ERP project proposes a new standard process, leaders may worry about several things:

• Losing operational flexibility
• Disrupting established workflows
• Reducing efficiency in specialised environments
• Having processes dictated by another department

From their perspective, the current process works. Changing it introduces risk. This is why ERP transformation requires far more than technical planning. It requires organisational alignment. Without that alignment, the implementation can become a series of negotiations rather than a transformation. 

Why the Debate Starts Before Implementation

One of the biggest misconceptions about ERP projects is that the real work starts when implementation begins. In practice, the most critical conversations happen before the project even launches, and by the time implementation starts, organisations should already have clarity on several fundamental questions:

• Which processes will be standardised across the enterprise?
• Where will the organisation allow controlled variations?
• Who owns each process moving forward?
• What governance structure will manage process changes?

If these decisions are delayed until the implementation phase, the project team can quickly become trapped in endless design debates. Instead of building the system, teams spend time resolving fundamental organisational questions.

That slows progress, increases costs, and can create frustration across stakeholders.

When organisations address process ownership early, ERP implementation becomes far more predictable.

Technology Is The Easy Part

Modern ERP platforms are more capable than ever. Cloud-based systems offer regular innovation, best-practice templates, and flexible integration capabilities. Implementation tools are increasingly mature. Migration approaches are well established.

In many ways, the technology has become the least risky part of the transformation. The real challenge lies in bringing the organisation together around shared ways of working that require:

• strong executive sponsorship
• cross-functional collaboration
• clear governance structures
• a willingness to challenge legacy practices

When leadership approaches ERP purely as a technology initiative, these organisational realities can come as a surprise. But when ERP is framed correctly, as a business transformation supported by technology, the path becomes much clearer.

A Leadership Decision, Not An IT Decision

Ultimately, process standardisation cannot be delegated entirely to project teams or IT departments. These are leadership decisions, and they must determine:

• How much standardisation the organisation truly wants
• Where operational flexibility is essential
• Which processes are strategic differentiators
• Which processes should follow industry best practices

When these principles are clear, ERP implementation becomes far more straightforward. Teams can design systems that reflect agreed operating models rather than negotiating them during implementation.

The Real ERP Question

Organisations often begin ERP discussions by asking “Which system should we implement?” But the more important question is: “How do we want this organisation to operate?”

Technology will enable that vision. But the decision about process ownership will define it.

And that is why the hardest ERP decision is rarely about the platform.

It is about alignment.

It is about governance.

And ultimately, it is about how the business chooses to work together going forward.

 Ready to future-proof your business? 

 Complete your details below for a free consultation, and let’s unleash your business's growth together: