Skip to content
Tutorials Center
My learning

Topics

Lesson 22 of 36 ยท Implementation and Change

Change Management and Training for ERP and CRM

Learn how to prepare people for a new ERP or CRM: stakeholder analysis, communication, resistance, role-based training, super users and adoption metrics, with Python tools.

An ERP or CRM system changes how people work every day: what they type, who approves their work, which numbers they are measured on. If the people do not adopt the system, the software delivers nothing, however good the design is. Change management is the discipline of preparing, equipping and supporting people through that change; training is one of its most visible tools.

This lesson covers stakeholder analysis, communication, handling resistance, designing role-based training and measuring adoption. The product is not available on this site, so the tools are small Python stand-ins that model the ideas.

Why users resist

Resistance is rarely stubbornness. Typical reasons:

  • Loss of control or status: "I used to be the only one who knew how the stock list worked."
  • Fear of competence loss: "I was fast in the old system."
  • More work now, benefit later: sales reps must enter data that mainly helps managers.
  • Unclear reason: nobody explained why the old way is no longer good enough.
  • Past bad experience: a failed project three years ago.

Treat resistance as information. Ask what is behind it before trying to overcome it.

A simple change model

Many change frameworks exist (Kotter's eight steps, ADKAR, Prosci). They agree on a sequence. Using ADKAR as the example, each person must go through five stages:

Understand and want

Awareness Why is the change needed?
Desire What is in it for me?

Most projects over-invest in the later stages.

1 / 2

A person who lacks awareness will not benefit from a perfect training course. Diagnose the stage where each group is stuck, then act on that stage.

Stakeholder analysis

List every group affected by the project and assess two things: how much the change impacts them, and how much influence they have over its success. The classic grid gives four strategies: high impact and high influence (partner closely), high impact and low influence (support and inform), low impact and high influence (keep satisfied), low impact and low influence (monitor).

Python Stakeholder grid (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Sort by attitude and you see where effort should go first: groups strongly affected and sceptical, such as the sales representatives here.

Communication plan

Communication starts at kickoff, long before go-live. A good plan states who needs what message, through which channel, how often, and who sends it. People believe their direct manager more than a company-wide email, so arm managers with talking points. Be honest about what will get harder as well as what will improve. Early on, share the reason and the timeline; mid-project, share demos and progress; before go-live, share dates, what changes for each role and where to get help; after go-live, share early wins and fixes.

Role-based training

Users do not need to learn the whole system, only their own work in it. A role-based curriculum maps each job role to the transactions and screens it uses.

  1. List roles (sales rep, buyer, warehouse clerk, accountant, approver).
  2. For each role, list tasks from the business processes.
  3. Write short scenario exercises using realistic data in a training environment (a copy of the system with fake data).
  4. Choose formats: instructor-led sessions for complex flows, short videos or quick-reference cards for frequent tasks, sandbox practice, and in-application guidance.
  5. Assess: a short test or a practical exercise, not just attendance.

Time training close to go-live (a few weeks before): too early and people forget; too late and nobody has time.

Python Training plan builder (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Super users and the support model

Super users (also called key users or champions) are respected staff from each department who join the project early, test, help design and later coach colleagues. They are the most effective change tool in many projects: colleagues ask them first. Give them time, recognition and direct access to the project team. Around go-live, add floor walkers (support people who stand next to users), a help desk with clear categories and a quick-reference guide.

Measuring adoption

Do not stop at "training completed." Measure what users actually do: login frequency, percentage of orders entered in the system, share of CRM records with filled mandatory fields, tickets per user per week, time to complete key tasks, and a satisfaction pulse survey. Compare to targets and follow up with teams that lag.

Python Adoption dashboard (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common mistakes

  • Treating training as the only change activity.
  • Training on generic demo data that looks nothing like the user's work.
  • Ignoring middle managers, who can quietly undermine the system.
  • Going live without a support model.
  • Declaring success at go-live instead of tracking adoption for months.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. In the ADKAR model, which stage answers 'What is in it for me?'

    Desire is the personal willingness to take part in the change.
  2. 2. What is a super user?

    Super users act as the bridge between the project and their department.
  3. 3. Why is role-based training better than a tour of every screen?

    People retain what they will use. Role-based scenarios connect the system to their daily work.
  4. 4. Which metric best shows real adoption?

    Behaviour in the system shows whether people use it, independent of attendance counts.
  5. 5. When should end-user training normally take place?

    Training close to go-live keeps knowledge fresh while still leaving time for practice.

Summary

  • Adoption decides whether the project delivers value; people resist for understandable reasons.
  • Use a model such as ADKAR to find where each group is stuck.
  • Analyse stakeholders and communicate early, honestly and through managers.
  • Train by role, with realistic scenarios, close to go-live; rely on super users.
  • Measure real usage after go-live and follow up.

Next: Testing, Cutover and Go-Live