I have led ERP programs for over 20 years. The uncomfortable truth: most S/4HANA go-lives don't fail on the technical build. They fail on the humans. Configuration is hard, but recoverable. Losing the trust of 4,000 users in week one is not.
Here is the playbook I use to land global S/4HANA rollouts — the concrete moves that separate a smooth cutover from a war room that never sleeps.
Stakeholder alignment: buy commitment, not attendance
A steering committee that shows up is not the same as a steering committee that owns outcomes. On one global rollout, I stopped asking sponsors to "review" the plan and started asking them to sign a one-page decision log — scope, non-negotiables, and the three metrics we'd be judged on.
That single artifact killed 80% of the scope-creep debates before they started. When a plant manager later demanded a custom Z-report two weeks before cutover, I didn't argue. I pointed to the log the sponsor had signed. Decision made in four minutes, not four meetings.
Concrete rule: every process area gets one named business owner with the authority to say no. No owner, no go-live for that stream.
Super-users are the program, not a nice-to-have
The most reliable predictor of a calm go-live I have ever measured is the super-user network. Not the SI's headcount. Not the number of test scripts. The super-users.
My ratio is roughly one trained super-user per 15–20 end users, identified 4–5 months before go-live. These are respected operators, not volunteers nobody could refuse. They test with real data, they co-write the training, and on day one they sit on the floor — not in IT.
- They cut level-1 tickets dramatically, because a peer at the next desk answers faster than any hotline.
- They translate SAP language into "how we actually do it here."
- They give you an early-warning radar — they feel resistance weeks before a survey would.
If your super-users can't run the top 10 daily transactions blindfolded two weeks before cutover, you are not two weeks from go-live. You are lying to yourself.
Training: teach the job, not the software
The classic mistake is training people on SAP screens. People don't do transactions; they do jobs. So we build training around role-based end-to-end scenarios: "You are a warehouse clerk, a truck just arrived, walk it through to goods receipt."
Three things that consistently move the needle:
- Sandbox with real, messy data — clean demo data teaches nothing about month-end reality.
- Simulations users can replay at 11pm — self-service beats a full classroom you'll never schedule for everyone.
- Competency checks before go-live — a short scored run-through, not a smiley-sheet. If a role fails, that's a risk you now see instead of discover.
Cutover comms: over-communicate, then double it
Cutover is where rumors move faster than facts, and rumors are always worse than reality. During the blackout window — when the legacy system is down and S/4HANA isn't live yet — silence is interpreted as failure.
So I run a daily cutover bulletin: same time, same channel, same format. Green/amber/red on every workstream, what's done, what's next, who to call. Even "everything on plan, nothing needed from you" is a message worth sending. It buys you enormous credibility for the moment you do need to say "we hit an issue."
One non-negotiable: a single, visible "here's how to get help on day one" card in every user's hands — laminated, on the intranet, and pinned in Teams. When the system is new and adrenaline is high, people should never have to hunt for the lifeline.
Hypercare: a phase, not a hope
Hypercare is where you win or lose adoption, yet it's the phase most programs under-resource because the budget is exhausted. Don't. I plan a 4–6 week hypercare window with the full team retained and the SI still on the hook.
- Floor-walkers in every major site for the first days — visible help, not a portal.
- A triage board reviewed twice daily, ranked by business impact, not by ticket age.
- Clear exit criteria: ticket volume trending down, no open severity-1s, key month-end processes proven — then you stand the team down. Never a calendar date alone.
The pattern under all of it
Every one of these moves is the same bet: invest in people ahead of the technology, and the technology lands. Skip it, and the cleanest build in the world will still generate a war room.
S/4HANA is a genuinely powerful platform. But go-live day is not a technical event — it's the day your organization decides, together, whether to trust the new way of working. Everything above exists to make that decision an easy yes.
Cédric Bignet is an AI & ERP Change Management expert at Novartis and founder of AInspire. He writes about change management, AI adoption and enterprise transformation.