The Change Management Skills ERP And Automation Rollout Leads Need

ERP Implementation and Automation: Change Management Skills

Published: November 18, 2026

TL;DR

A lead running an ERP or automation rollout needs four change management skills that a project plan does not cover: diagnosing resistance by role, mapping how each job changes, training staff on exceptions, and measuring adoption after go-live. Leads can build them by working beside an experienced change lead, through practitioner certification, through postgraduate study or through leadership reading. Each route has a limit, so most leads will combine two.

Why Adoption Falls Short After Go-Live

An ERP or automation project can meet every technical milestone and still leave staff working around the new system.

Consider a mid-market distributor that processes 6,000 supplier invoices a month and moves to automated capture and three-way matching. The system goes live on schedule. Two months later, accounts payable clerks still key some invoices by hand because they do not trust the extracted data, and department managers approve by email because the new queue is one more login. Invoices get paid, so no project report shows a problem. The company is paying for automation while running its old process beside it.

Project leads are usually chosen for their knowledge of the system or the process, and they are measured on budget and go-live date. Neither measure says whether people use the system. Change management then gets reduced to an announcement and a training session, delivered by someone who has never been taught how to do more.

Actionable takeaway: Add one adoption measure to the project’s definition of done, with a named owner, before the go-live date is set.

Make AP Automation Adoption Easier With Structured Exception Workflows - Artsyl

Make AP Automation Adoption Easier With Structured Exception Workflows

An AP rollout can meet its go-live date and still fail when employees keep entering invoices manually or approving them by email. InvoiceAction combines intelligent supplier invoice capture, matching, validation, and configurable approval routing to support a consistent automated process.

Help teams replace fragmented habits with clearer workflows for routine invoices and exceptions.

The Skills A Rollout Lead Needs

Diagnosing resistance by role

Staff in different roles object for different reasons, so a single message rarely answers them. In the distributor example, a clerk may worry that automated capture will remove part of the job, while a department manager objects to the extra login. A controller may hold back until she sees how the audit trail records overrides. The IT manager’s doubt is who will support the integration once the vendor leaves.

A capable lead interviews a few people from each group before the design is signed off, then logs every objection by role and plans the response the way a project risk is planned.

Recommended reading: Learn How Intelligent Process Automation Best Practices Support Successful Adoption

Mapping how each job changes

A process map shows how work moves. A change impact assessment shows what each person will do differently on the first Monday after go-live: which tasks disappear, which are new, whose approval limits move and who handles a failed match.

The lead should write this assessment by role, in enough detail for a supervisor to check it. A clerk moving from data entry to exception handling needs different judgment and probably different performance goals. If the goals stay the same, the old behavior usually stays too.

Training for exceptions

Vendor training tends to demonstrate the simple case, an invoice that matches and posts without intervention. Staff lose confidence on the first invoice that fails, such as one with a price variance or a missing purchase order.

Build training sessions from the organization’s own failed transactions. Pull a sample from the previous quarter and rehearse in the test environment who resolves each type. Staff then meet the hard cases before they arrive in a live queue.

Measuring adoption after go-live

System reports show that the software is running. A rollout lead needs figures that show how people are using it. For an accounts payable rollout, useful measures include the share of invoices processed without manual touch, the volume of approvals made outside the workflow, exception aging by team and overrides per user.

Report these by team. A company-wide average can hide one department that never moved over. A rise in overrides from a single team usually points to a specific training gap or a matching rule that does not suit that team’s suppliers, and both can be fixed once someone sees the figure.

Actionable takeaway: Capture a baseline for each measure from the old process, then review the figures weekly for the first 90 days after go-live.

Connect ERP Change Management With Reliable Document Inputs - Artsyl

Connect ERP Change Management With Reliable Document Inputs

An ERP launch can struggle if incoming documents still require manual reentry or arrive with inconsistent fields. docAlpha uses AI-powered capture, validation, and configurable workflows to prepare structured data for connected enterprise applications.

Reduce unnecessary handoffs as teams transition to new business processes.

Where Rollout Leads Can Build These Skills

Working beside an experienced change lead on a live rollout suits a first-time lead, who sees the diagnosis and the difficult sponsor conversations as they happen. Access is the limit. Many mid-market companies have no such person on staff, and the lessons come from a single project in a single organization.

A lead who needs a recognized method quickly, particularly where the organization already uses it, can take practitioner certification from Prosci or ACMP. These programs are not specific to ERP or automation, so the lead still has to adapt the method to systems work.

A postgraduate course suits a lead who expects to run several rollouts and wants a grounding in how organizations absorb new systems, though it takes longer than a practitioner certification. For a rollout lead who wants that study while still in the job, Australia’s Victoria University runs a short postgraduate course in change management through VU Online, studied fully online and one unit at a time. Its Graduate Certificate in Change Management includes a Technological Change and Innovation unit on how new technologies are aligned and implemented inside organizations, and entry requires a bachelor degree in a similar discipline or at least five years of approved work experience.

Leadership reading gives anyone a low-commitment start or a shared language for briefing a sponsor. Books give no practice and no feedback, and few of them deal with what happens when a matching rule rejects a third of a supplier’s invoices.

Actionable takeaway: Match the route to the date of the next project. If a rollout starts within months, find a change lead to work beside and add reading. If several rollouts are planned over the coming years, add formal training as well.

Recommended reading: Learn How to Prepare Teams for an Invoice Automation Rollout

How Steering Committees Can Test Readiness

The people who appoint a rollout lead can check these skills without running an assessment program. Before approving the go-live date, ask the lead for four documents: a resistance log by role, a change impact assessment, a training plan built on real exceptions and an adoption scorecard with baselines.

A missing document shows where the lead needs coaching or outside support while there is still time to arrange it. A thin one is also useful. An impact assessment that lists departments and never names a job title has usually been written without talking to the people affected.

Time matters as much as training. A lead who keeps a full operational workload during the rollout will drop the interviews and the weekly adoption review first, because nobody chases them. Set aside part of the lead’s week for this work, and keep that allocation in place for 90 days after go-live, since project teams are often reassigned as soon as the system is running.

Turn AP Rollout Success Into Everyday Processing Efficiency - Artsyl

Turn AP Rollout Success Into Everyday Processing Efficiency

Go-live is not the finish line if staff still copy invoices into the ERP and chase approvals outside the system. InvoiceAction automates supplier invoice capture, validation, matching, and routing so teams can handle regular transactions through a structured process.

Reduce repeated manual steps and make the benefits of automation visible in daily AP work.

Looking for
Document Capture demo?
Request Demo