The next ERP challenge is not implementation. It is continuous change

For years, enterprise software projects followed a relatively predictable model: implement the system, stabilise it and operate it for several years before considering the next major upgrade.

That model is changing.

Cloud platforms, artificial intelligence, automation and evolving business requirements mean organisations are no longer managing an ERP project every five or ten years. They are managing ongoing changes to their technology, processes, data and ways of working.

This makes change management increasingly important.

Change management is the structured approach organisations use to prepare for, implement and embed change across people, processes and technology. In an ERP environment, it helps ensure that changing or upgrading the technology does not happen in isolation. The business understands why change is happening, what it means for different teams and how new ways of working will be adopted.

For organisations using platforms such as IFS Cloud, this is becoming a continuous discipline rather than something reserved for major implementation projects.

 

ERP change management is becoming continuous

 

Traditionally, ERP change management was closely associated with major projects such as implementing a new system or moving from one ERP platform to another.

Cloud ERP changes that dynamic.

New functionality can arrive more frequently. AI capabilities continue to develop. Integrations need to evolve as the wider technology landscape changes. Reporting requirements grow, while organisations themselves restructure processes, enter new markets and respond to changing customer expectations.

Each of these developments can create changes for the people using the system.

The question for leadership teams therefore changes from:

“How do we successfully implement our ERP system?”

to:

“How do we manage continuous ERP change while keeping our people, processes and technology aligned?”

That requires more than technical delivery.

 

What does ERP change management involve?

 

Successful change management connects the technology programme with the people who will ultimately use it.

While every organisation is different, ERP change can broadly be considered across five stages:

 

Stage	What it means	Key considerations
1. Understand	Establish why change is needed and what it will affect.	Business objectives, current challenges, processes, systems and stakeholders.
2. Prepare	Define how the organisation will approach and communicate the change.	Governance, responsibilities, communications, training and change readiness.
3. Deliver	Implement the technology and associated process changes.	Configuration, integration, data, testing, user involvement and project control.
4. Adopt	Help users move confidently into new ways of working.	Training, support, communication, user feedback and knowledge transfer.
5. Improve	Review performance and identify the next opportunities for improvement.	New functionality, automation, optimisation, upgrades and continuous improvement.

 

A simple way to think about the process is:

Understand → Prepare → Deliver → Adopt → Improve → Repeat

The final step is particularly important. In a cloud environment, improvement feeds back into the next cycle of change.

Change management therefore becomes a capability the organisation develops, rather than a task completed once.

 

Why structured change management matters

 

Technology alone does not create business improvement.

An organisation can successfully deploy a new ERP platform while still struggling to realise its potential if users continue following old processes, data remains inconsistent or new functionality is not adopted.

A structured approach to ERP change management can help organisations:

The objective is not simply to manage a technology project successfully. It is to create an organisation that can absorb and benefit from change more effectively.

 

AI makes change management more important

 

AI is accelerating this shift.

Across asset-intensive and service-led industries, businesses are exploring how AI can support maintenance, scheduling, finance, forecasting, customer service and operational decision-making.

But AI does not operate independently of the organisation around it.

Its effectiveness depends heavily on the foundations beneath it.

If operational data is inconsistent, processes are fragmented and integrations are unreliable, introducing more intelligence does not automatically solve those problems. It may simply make existing weaknesses more visible.

This is why conversations about AI, ERP and change management increasingly need to happen together.

Before asking what an AI capability can do, organisations should also consider whether their data, processes, people and technology landscape are ready to support it.

 

The cost of standing still is changing

 

There was once a reasonable argument for leaving a stable ERP environment alone.

If the system worked, why change it?

That logic becomes harder to maintain when technology and business requirements evolve continuously.

Older processes, customisations and reporting approaches can gradually increase complexity. Teams create manual workarounds. Integrations become harder to maintain. Testing takes longer. Knowledge becomes concentrated among a small number of employees.

None of these issues necessarily creates an immediate crisis.

Instead, technology debt often builds quietly until the organisation needs to move quickly. Something that should have been a manageable change can then become a much larger programme.

Continuous improvement provides an alternative.

Rather than allowing years of complexity to accumulate, organisations can regularly review what should be simplified, automated, retired or improved.

 

Evergreen ERP requires operational discipline

 

Continuous change should not mean continuous disruption.

It needs structure.

Organisations need clear ownership of their ERP environment, defined processes for evaluating new functionality and an effective way of determining what should be adopted now, later or not at all.

Testing becomes particularly important.

When systems evolve regularly, regression testing cannot become a major manual exercise every time something changes. Testing needs to be repeatable, scalable and, where appropriate, automated.

The same principle applies to integrations.

ERP rarely operates alone. It sits within an ecosystem of applications, data platforms, customer systems, suppliers and specialist technologies. As that ecosystem changes, organisations need an integration strategy capable of evolving with it.

 

Data becomes a strategic asset

 

One of the most important consequences of continuous ERP change is that data quality can no longer be viewed purely as an IT issue.

It is an operational issue.

Finance needs confidence in its numbers. Maintenance teams need accurate asset information. Field service teams need reliable customer, job and resource data. Leadership needs a consistent view of performance.

AI increases the importance of this further.

Organisations with strong data foundations will be better positioned to take advantage of intelligent automation as those capabilities develop.

That means reducing unnecessary duplication, improving governance and creating clearer ownership of information across the business.

The goal should be straightforward: when somebody makes a decision using enterprise data, they should be able to trust it.

 

Change management should continue after go-live

 

Go-live is an important milestone, but it should not represent the end of change management.

This is also where the role of the ERP partner is evolving.

Traditional ERP engagements have often concentrated heavily on implementation or upgrade delivery. Organisations increasingly need support across the complete lifecycle of their platform.

At Platned, our approach extends beyond implementing technology. We work with organisations throughout their IFS journey, helping them manage change, reduce complexity and continue improving their environment.

This can include:

The difference is the focus on the complete lifecycle.

Rather than treating implementation, adoption, support, upgrades and optimisation as disconnected activities, they become part of one continuous improvement journey.

 

What does this mean for customers?

 

For customers, this approach creates several practical benefits.

There is greater clarity around what is changing and why. Risks can be identified earlier. Testing becomes more repeatable. Knowledge is less dependent on individual employees. New functionality can be assessed in a controlled way, while improvements can be introduced without waiting for another major transformation programme.

Most importantly, the ERP platform can continue evolving alongside the organisation.

That is particularly valuable with IFS Cloud, where the opportunity is not simply to move onto a modern platform, but to continually improve how that platform supports the business.

 

Success should not be measured at go-live

 

A better measure of ERP success is what happens one, two or five years after implementation.

Has the organisation continued to simplify its processes?

Has it adopted useful new capabilities?

Is testing becoming easier?

Are integrations manageable?

Can teams trust their data?

Are users confident with the system?

Can the business respond quickly when requirements change?

And, increasingly, is the organisation ready to take advantage of AI as those capabilities mature?

These questions reveal far more about the long-term value of an ERP investment than whether the original project simply went live on time.

 

Building an organisation ready for change

 

Nobody can predict exactly how enterprise technology will develop over the next five years.

What we can predict is that organisations will continue to face change.

AI will develop. Automation will increase. Business models will evolve. Regulations will change. Customers will expect more. Organisations will continue searching for ways to become more productive.

The answer is not to predict every technology that might become important.

It is to build an enterprise platform, change management capability and operating model capable of adapting when those changes arrive.

For organisations running or considering IFS Cloud, that means thinking beyond implementation from the beginning.

Build strong data foundations. Simplify where possible. Automate testing. Create sustainable integrations. Establish clear governance. Support users through change. Keep improving.

Because long-term advantage may not come from simply having the newest technology.

It may come from being better prepared to adopt, manage and make use of what comes next.