ERP
HEAD
TO
HEAD™
Compare the leading ERP products at 1 event
ERP HEAD TO HEAD™

ERP Change Management: The Critical Role of Leaders & Managers

The success or failure of ERP projects is rarely down to the technology alone. More often, success depends on whether leaders, sponsors and managers actively support the change and help their people navigate it. Change Managers play a critical role in orchestrating this work, but lasting adoption requires visible leadership and shared ownership at every level of the organisation.

ERP Projects Create Human Change, Not Just System Change

ERP projects are often mistakenly described as technology initiatives. Organisations invest in new software, implementation partners, integrations and data migration, setting out to deliver a platform capable of supporting future growth and improvement.

However, employees rarely experience an ERP project as a technology change. What they experience is change to the way they work: new processes, new responsibilities, new controls and approvals, and new ways of collaborating with colleagues and customers. In some cases, ERP implementation is also accompanied by changes to organisational structures, reporting lines or roles.

The most successful organisations therefore recognise ERP implementation as a business transformation enabled by technology, rather than simply a technology project that happens to affect people. This distinction also explains why effective change management cannot rest with a dedicated Change Manager alone. Specialist expertise is important, but leaders, sponsors and people managers must also play an active and visible role if the change is to succeed.

Employees Need to Hear From the Right People

Most ERP projects include a range of communication activities. Project updates, newsletters, town halls, intranet posts and training materials all have an important role to play in keeping stakeholders informed and engaged.

However, not all messages carry equal weight, and not all messages should come from the project team.

Prosci’s long-running research into change management best practice consistently finds that employees prefer to hear different messages from different people. Strategic messages about why the organisation is changing are most credible when delivered by senior leaders and project sponsors, while messages about how the change affects an individual’s role and day-to-day work are most effective when delivered by their direct manager.

This makes intuitive sense. Employees want senior leaders to explain the business rationale, the objectives being pursued and the risks of doing nothing. Equally, they want someone who understands their day-to-day reality to help answer the inevitable question: "What does this mean for me?"

That does not diminish the role of the Change Manager; quite the opposite.

A well-managed ERP project requires a structured communications strategy, a detailed communications plan and ongoing stakeholder engagement. The Change Manager is responsible for orchestrating that effort, equipping leaders and managers with the information they need, and ensuring communications are timely, consistent and aligned. But the most important messages should not come exclusively from the project team.

ERP Change Management: The Critical Role of Leaders & Managers

 

Leadership Alignment Is Essential for ERP Success

Employees pay close attention to what leaders do, not just what they say.

When senior leaders are visibly aligned and consistently supportive of an ERP project, that commitment tends to cascade throughout the organisation. Managers become more engaged, employees gain confidence that the project is important, and difficult decisions are made more quickly and consistently.

The opposite is also true: some of the most challenging ERP projects I have encountered were not struggling because of technology issues, but because senior leaders had not aligned around the project’s objectives, the scale of change required or the benefits being pursued.

In these situations, mixed messages emerge. Leaders may publicly support the project while privately questioning its value, departments pursue competing priorities, and managers hesitate to allocate resources or encourage participation.

Employees notice these signals. When they do, uncertainty grows and resistance often follows.

Prosci identifies active and visible executive sponsorship as one of the most important contributors to successful organisational change. Effective sponsorship is not simply about approving budgets or attending steering committee meetings. It requires leaders to champion the change, maintain consistent messaging and visibly demonstrate their commitment throughout the project lifecycle.

People Managers Are the Critical Link Between Strategy and Adoption

While executive sponsorship rightly receives significant attention, the importance of people managers is often underestimated.

People managers sit where organisational strategy meets operational reality. They understand their teams, anticipate where concerns may emerge and are often the first people employees approach with questions.

Yet managers are sometimes engaged relatively late in ERP projects, and treated primarily as recipients of information rather than active participants in helping deliver the change.

In fact, they should be involved throughout the journey. They can provide valuable input during stakeholder analysis and change impact assessments. They can help identify operational challenges, assess readiness for change and highlight where additional support may be needed. Most importantly, they reinforce key messages, address concerns and help employees understand what the change means for them in practice.

When managers are engaged early and informed properly, they become one of the strongest enablers of successful adoption.

Some Conversations Cannot Come From the Project Team

Perhaps the clearest example of leadership responsibility arises when ERP projects involve significant organisational change.

Large ERP initiatives are often accompanied by process redesign, operating model changes or role restructuring. Employees may understandably be concerned about what those changes mean for their future.

These are often difficult conversations, and they are not conversations that should be led by the ERP Project Manager or Change Manager.

Communication with individuals about substantial changes to their roles, responsibilities or reporting structures should come through established management channels. In some situations, HR will also play an important role in supporting those discussions.

The project team and Change Manager can help equip managers, provide guidance, develop supporting materials and ensure a consistent approach. But they should not be the people delivering highly personal messages about an individual's future role within the organisation.

That responsibility belongs to leadership and line management.

Employees need openness, honesty and trust. Those conversations are most effective when they come from people who have an existing management relationship with the individuals affected.

Change Management Requires Shared Ownership

Modern ERP projects require a dedicated and structured change management approach. Stakeholder engagement, communications planning, change impact assessment, training and readiness activities do not happen by accident. They require planning, resources and specialist expertise.

Change management cannot be treated as the responsibility of a single individual or project workstream. It is shared organisational work, enabled by specialist expertise but delivered through leadership, sponsorship and line management.

The Change Manager provides structure, methodology, tools and guidance, while the project team coordinates activities and supports implementation. Lasting adoption, however, depends on leaders championing the change, sponsors maintaining alignment and managers helping employees understand what it means for them. When each group fulfils its role, the organisation is far more likely to achieve the intended business outcomes.

Ultimately, ERP success is not defined by the software going live. It is defined by people adopting new ways of working and sustaining the change long after go-live.

Edward Abrahamson is an Associate Partner with Lumenia Consulting. To discuss how Lumenia could support your ERP change management or business transformation initiative, contact Edward directly.