ERP Change Management That Holds Up at Go-Live

The real problem: ERP is a people project with hard deadlines

ERP implementations come with a clock. Data conversion, integration testing, cutover plans, and payroll cycles do not wait for emotions to settle.

At the same time, people have their own motivations, fears, and priorities. A process owner can be worried about disruption. A department lead can be worried about performance metrics. An end user can be worried about looking incompetent. Someone else can be worried about whether the new system makes their role smaller.

The video frames resistance in a way that is useful, not dismissive:

• Some resistance comes from fear of the unknown.
• Some resistance comes from pride and care for an existing process that already works “well enough.”

That distinction matters because it changes the response. Fear needs clarity and repetition. Pride needs respect and real-world proof.

“ERP projects are not just technical solutions. They are people projects.”

A cautionary scene: when “support” becomes damage control

One story in the video lands because it is so recognizable: a go-live where problems pile up fast, and the support model becomes a visible symbol of frustration.

In the example, the team tried to create a lightweight help signal: if someone had an issue, they would plug in a string of Christmas lights at their desk. The idea was simple. The result was not.

The lights appeared everywhere. Confusion spread. People who had never used web-based tools were expected to perform in a brand-new environment with minimal runway. Training was late and too broad. Testing did not match real scenarios. Stakeholders outside the company received unfamiliar paperwork without warning.

The operational consequences were immediate: delays, rework, and a loss of trust.

The point is not “do not use Christmas lights.” The point is that a support mechanism cannot compensate for missing fundamentals. If a rollout does not account for user readiness, a help desk becomes a triage unit.

What strong change management looks like before go-live

The video’s advice is practical because it treats preparation as a set of repeatable actions. The best parts are not flashy; they are the habits that reduce surprises.

Communicate early, then communicate again

Many teams treat communication as a single artifact: an announcement email, a project plan, a monthly status update.

The video pushes a stricter definition: communication is not “sent.” It is “received and understood.”

That leads to simple implications:

• Explain the change early enough that people can process it.
• Repeat the message in multiple formats.
• Expect questions. Answer them directly.
• Avoid surprises; surprises create resistance.

A useful structure for the message is the “five W’s”:

• Who will be affected (roles, teams, locations).
• What is changing (processes, screens, responsibilities).
• When it will change (timeline, phases, go-live).
• Where it will show up (systems, documents, handoffs).
• Why it is being done (the measurable outcomes, not slogans).

The video also makes a key point that many implementations miss: communication is not only internal. External stakeholders can be disrupted by new document formats, new process timing, and new expectations. If customers and vendors are surprised, internal teams pay the price.

Create champions who can explain the change in plain language

One practical recommendation is to build a small set of internal champions who can deliver an “elevator speech” that answers the questions employees are already asking:

• What is changing for my job this month?
• What stays the same?
• What do I need to learn first?
• Where do I go for help?

Champions reduce uncertainty because they shorten the distance between a question and a credible answer.

Define KPIs that match reality, not wishful thinking

If leadership says an ERP project will reduce cycle time or improve accuracy, the project needs clear measures that reflect those outcomes.

The video emphasizes “SMART” measures: specific, measurable, achievable, relevant, and time-bound. More importantly, it connects measurement to trust. When teams can see the real situation, good or bad, they are less likely to fill the gap with rumors.

Celebrate small wins without pretending everything is perfect

The video argues for small wins as reinforcement, not as propaganda.

A small win can be as simple as:

• A department completing role-based training by a target date.
• A key handoff working cleanly in a conference room pilot.
• A recurring issue dropping after a process adjustment.

Celebration is valuable because it tells the organization what “good” looks like while change is still fresh.

The human side: resistance follows a pattern

The video treats resistance as a predictable cycle. People often move through a sequence that looks like:

1. Shock or paralysis
2. Denial
3. Anger
4. Bargaining
5. Low point
6. Acceptance

The value of this framing is not psychology trivia. It is operational guidance.

If a rollout is announced late, people hit the “anger” stage right as they are expected to perform. That is when mistakes spike and internal friction becomes expensive.

The video’s guidance is to build time into the plan for the emotional adjustment. That time is not “soft.” It protects throughput.

It also stresses active listening. Not every complaint is wrong. Some resistance contains real process risk. A team that listens early can address issues before they become production problems.

Training that works: short, role-based, and tied to real scenarios

The video’s strongest practical section is about training. It rejects the “train everyone on everything” approach and replaces it with role-based learning tied to real workflows.

Here are the training standards the video reinforces:

• Role-based: teach what a person needs for their job, not the full system.
• Job-specific handoffs: show what changes when work moves from one team to another.
• Short and repeatable: training should be easy to revisit.
• Real scenarios: training has to include the messy cases, not only the clean ones.

It also argues for a “train the trainer” model:

• Identify subject matter experts who know the business process.
• Teach them the system deeply.
• Have them train end users in the context of the work.

This approach reduces translation errors. It also creates in-house capability that lasts beyond go-live.

Readiness is a decision, not a date on the calendar

A useful part of the video is its view of readiness as a multi-factor assessment. Many projects treat go-live like a milestone you reach because the calendar says so.

The video recommends a “go/no-go” mindset built from several readiness checks. A strong readiness review typically looks at:

• Executive and strategic readiness: sponsorship, decisions, funding, accountability.
• Process readiness: handoffs defined, workarounds eliminated, exceptions understood.
• People readiness: training delivered, confidence measured, resistance addressed.
• Testing readiness: real transactions tested, not only scripted demos.
• Data readiness: converted data is clean and usable.
• Technical readiness: integrations, permissions, environments, and performance validated.

Surveys and quick polls can help measure confidence. Adoption metrics can help verify behavior. If the organization cannot be honest about readiness, risk goes up.

Adoption after go-live: measure behavior, not optimism

A key theme in the video is that change management does not end when the system turns on. It continues every time a new employee starts, a process shifts, or the system receives upgrades.

That calls for metrics that show whether the system is being used as intended.

The video mentions login history as one signal, but it also points to broader measures:

• Are key transactions moving through the system end-to-end?
• Where do handoffs stall?
• Which roles have training gaps on uncommon but critical tasks?
• Are users avoiding the system with spreadsheets and side processes?

A useful way to think about it: adoption is visible in throughput, not in intent.

Practical takeaways: a checklist for change that holds up under pressure

This is the core value of the video. It gives teams a clear set of moves that reduce chaos.

Communication checklist

• Set expectations early; remove surprises.
• Repeat key messages in short formats, not only long emails.
• Answer “who, what, when, where, why” in plain language.
• Include customers and vendors when outputs change.

Training checklist

• Build role-based training with real scenarios.
• Use internal power users for “train the trainer.”
• Make training short and repeatable.
• Cover corner cases before go-live.

Readiness checklist

• Define a go/no-go standard that includes people readiness.
• Validate handoffs in a conference room pilot.
• Confirm data quality and integration behavior.
• Use surveys and adoption metrics to verify, not guess.

Adoption checklist

• Track process throughput after go-live.
• Watch for bottlenecks and drop-offs.
• Use resistance as feedback; do not ignore it.
• Keep change management active for upgrades and onboarding.

Why this video is worth your time

Many implementation teams already know the basics. The value of this SmartTalks session is that it treats change management as a system with inputs, outputs, and measurable results.

If your last rollout felt harder than it should have, this video gives a practical way to diagnose why:

• Was communication late or unclear?
• Was training generic instead of role-based?
• Were real scenarios skipped in testing?
• Was readiness assumed instead of verified?
• Did adoption metrics arrive after the damage was done?

The video also gives language leaders can use without sounding like a motivational poster. It frames change as normal, resistance as expected, and adoption as the measurable outcome that matters.

Want to watch the full session?

The embedded SmartTalks video expands on these ideas with concrete examples, including what to do when resistance is high and how to measure adoption without guessing.

Want to go deeper on this topic? Join an upcoming SmartTalks webinar for a live walkthrough and open Q&A.