A man in an industrial warehouse represents the need to abandon outdated processes prior to SAP Go-Live

Before an SAP Go-Live, People Need to Let Go of the Old Way First

Change is not necessarily difficult. It takes time to be processed. I say this a lot, and I recently said it on camera. In a 70-second video there is only room for the idea. Here I want to take it one step further, into the place where I see it play out most often: the months before an SAP go-live.

Watch the video on LinkedIn, or keep reading.

Every program I have worked on had a plan for the system. Very few had a plan for the time people need to get there. That gap is where most of the pain sits, and it is what good change management is really about.

The holiday you have to cancel

If you have read The Resistance Nobody Recognizes Before an SAP Go-Live, you know this story. I keep coming back to it because everyone has lived some version of it.

  • At workYour boss tells you to cancel a holiday you have been planning with your partner. A work commitment. You are annoyed.
  • On the drive homeYou are already moving on. How to tell them, how to explain it, maybe even some alternative dates.
  • At homeThey get upset. Maybe angry. They want to understand why. They do not care about alternative dates yet.
  • And thenYou get frustrated, because you expected them to understand. Maybe even support you.

You had a head start. They did not.

Here is the thing. The part most people get wrong is not the news. It is the expectation.

You had the whole drive home to process it. You went through the annoyance, made your peace, and started planning. By the time you walked through the door, you were already on the other side. Your partner was hearing it for the first time.

Before someone can accept a new plan, they need to accept that the old plan is gone.

That sentence explains more SAP programs than any status report I have read. The project team has lived with the new system for a year or more. They have had their drive home. Then they walk into a warehouse, a finance team or a plant and present the new way of working. And they are surprised when people want to talk about the old one.

The project team

A year with the new system. Ready to talk about what comes next.

The people using it

Hearing it for the first time. Still holding on to the old way.

Change happens in phases, not in a switch

The first reaction to change is rarely acceptance. It might be denial, anger, frustration or sadness before someone starts moving forward.

It is not linear. People go forward and back. Two people on the same team, hearing the same message on the same day, can be in completely different places. Everybody experiences it differently.

Let us be honest: expecting someone to jump straight to the positive side of a change is unrealistic. Yet that is what most go-live plans assume. Announcement in week one, training in week two, everyone ready by cutover.

Resistance is not a sign that the message failed. Often it is a sign that people are still letting go.

What this looks like before an SAP go-live

In an ERP transformation, the phases rarely show up with their real names. Nobody says "I am in denial." They say other things:

We will keep the spreadsheet running in parallel, just in case.
The old system did this in two clicks.
We are too busy this month for training.
Silence in the training room, and no questions at all.

None of this means people are against SAP. It means they have not finished with the old way yet. If you treat it as a training problem, you add more training. If you treat it as a communication problem, you send more emails. Neither gives people what they actually need, which is time.

So what can a program lead do?

01

Announce early, train later

Give people the news well before they have to learn anything. Let the drive home happen before the classroom.

02

Make room for the reaction

Ask what people will miss about the old way, and listen. It feels slow. It is faster than fighting it after go-live.

03

Don't judge readiness by attendance

A full training room tells you who showed up, not who has accepted the change.

04

Expect different speeds

Teams reach acceptance at different times. Put your support where people are, not where the plan says they should be.

The question is not what reaction you are going to get. It is how quickly you can help someone move toward acceptance.

Technical-ready is not human-ready

Your SAP system can be technically ready on the planned date. Your people get there on their own timeline. A go-live succeeds when those two dates come close together.

That is the human side of ERP change management, and it is where an SAP go-live is really decided: in the time and space people need to get from the old way to the new one.

One question

On your program, who has had their drive home, and who is hearing the news for the first time?

Book a strategy call

Methodix. We monitor people's readiness during SAP and Oracle transformations. We work where almost no one is looking.

Share the Post:

Keep reading