Demo
Use case · Go-live training

Go-live and ERP training: will your users be ready on day one?

A successful go-live isn’t won on launch day. It’s won in the weeks before, when every user gets to practice, make mistakes and prove they can do the job, before their access is switched on.

Book a demoSee the countdown
K-Studio
Assessment 8 of 8Module certified
Simulation
Purchase orders
New purchase orderSubmit order
SupplierItemQuantityDelivery
iAssessmentCreate the order for supplier Lyon Parts.!AlmostWrong supplier, try again.✓CertifiedOrder submitted: you’re ready for go-live.
65,000Crédit Agricole employees prepared for the new core banking system before cutover
54,000Intermarché users, including 35,000 mobile users
2,200training modules built with K-STUDIO for Intermarché
The short answer

How do you get users ready for go-live?

Build your end user training plan backwards from the go-live date, with one simple rule: nobody gets access without having practiced first.

D-90Scope

Pick the processes

The 20 to 60 tasks that matter, per user group.

D-60Build

Simulate the application

Clone stable screens, without waiting for a training environment.

K-STUDIO
D-30Train

Practice and certify

Replayable exercises, then a scored assessment per module.

K-STUDIO
DGo live

Guide users in the live system

In-app help takes over at the first real transaction.

K-NOW
D+30Hypercare

Measure and fix

Spot the screens that block users and adjust the help.

K-VALUE
The problem

Classic training comes too early, on a system that isn’t finished.

Sessions booked weeks before cutover, an incomplete training environment, screens still changing: by go-live day, users have forgotten what they never really practiced. It’s the most common failure point in ERP training.

×Go-live endured
  • A training environment to build, load and maintain for every country and language.
  • Classroom sessions that can’t be scheduled for teams in stores, branches or workshops.
  • Training that is watched, not practiced: no proof the user can actually do the job.
  • Support and super users swamped from the first week of hypercare.
✓Go-live prepared
  • A simulated replica of the application, with no infrastructure: Michelin built no training environment per instance or language.
  • Self-paced exercises on PC or tablet: SNCF Voyageurs trained 3,000 maintenance agents.
  • An assessment before access is granted: at SNCF Voyageurs, every module ends with a self-assessment.
  • In-app help after cutover, which takes the load off super users.
Our doctrine

Certify before granting access.

One simulation serves three successive uses. The third changes everything: you no longer assume a user is ready, you measure it.

It’s the approach GNFA takes: every year, 3,000 vehicle inspection agents train in simulation as part of a mandatory, certifying course.

They did it

Six go-lives prepared in simulation.

65,000employees · 39 regional banksCrédit Agricole · core banking250 interactive modules to practice before the Nice project cutover.Read the case study → 54,000users · 3 applicationsIntermarché · LOREA program2,200 K-STUDIO modules before cutover, then K-NOW in the applications.Read the case study → 10,000employees · 70 user groupsHSBC · HUB portal200 business processes simulated before go-live.Read the case study → 7,000employees · 68 exercisesAllianz · ABS moves to the web100% of the application’s behavior reproduced: the simulation replaces the training environment.Read the case study → 5,000advisors · 700 storesYves Rocher · Cegid Retail POSEveryone practices on the till before taking real payments.Read the case study → 90%+of sessions rated as meeting expectationsANRU · IODA application1,630 internal and partner users trained on a tight deadline.Read the case study →
Super users and trainers

Train the trainer without burning out your super users.

Super users (key users) carry the go-live: they train, answer, reassure. A ready-made simulation saves them from giving the same demo a hundred times.

The French Ministry of Education trained 130 national trainers on 97 K-STUDIO practice cases; they then cascaded the training to local trainers and 8,000 schools. Read the case study.

130national trainers
97K-STUDIO practice cases
8,000schools
Safran Seats · off-the-job training, frequent user
5–10 d3–6 d
Before
After

And none at all for occasional users.

Safran Seats · key user time spent on support
25%20%
Before
After

Time handed back to operations, across 10 sites in 5 countries.

Go-live checklist

Eight things to check before go-live.

0/8Ready for go-live
  • Critical processes listed per user group, with how often they are used.
  • Screens frozen in testing before simulations are built.
  • Modules published in the LMS at least three weeks before go-live.
  • Certification rate tracked by site, role and manager.
  • Super users trained first, with early access to the simulations.
  • In-app help ready on high-risk screens from day one.
  • Hypercare plan set: support channels, alert thresholds, duration.
  • Usage metrics in place to measure adoption at D+30, alongside your cutover plan.
The solutions

Before, during and after go-live.

K
K-STUDIOApplication simulator

Practice and get certified before go-live.

A faithful replica of the application, in three modes: discover, practice, assess.

Explore K-STUDIO→
  • Cloned screens, sensitive data anonymized
  • Scored assessment per module
  • SCORM delivery in your LMS
  • PC, tablet, classroom or self-paced
K
K-NOWDigital adoption platform

Guidance on go-live day and through hypercare.

Guidance and alerts shown in the live application, at the first real transaction.

Explore K-NOW→
  • Contextual step-by-step guidance
  • Alerts on risky data entry
  • Content updated without a new release
  • Fewer requests to super users
K
K-VALUEDigital adoption analytics

Steer adoption after go-live.

Real usage metrics to decide when hypercare can end.

Explore K-VALUE→
  • Activation from the first weeks
  • Completion of key processes
  • Views by site, role or user group
  • Prioritized list of help to add
FAQ

Go-live training: your questions.

When should you train end users before go-live?
As close to cutover as possible, on frozen screens: typically two to three weeks before. A simulation built from the test environment lets you hold that schedule without waiting for a training environment.
Can you train users before the system is live?
Yes. K-STUDIO clones the application’s screens as soon as they are stable in testing. That’s how Allianz reproduced 100% of ABS’s behavior for 7,000 employees.
How do you check that a user is ready for go-live?
With an assessment mode, scored and without hints, at the end of each module. The score flows into the LMS via SCORM so you can track certification rates by site or role.
Can a simulation replace a training environment?
For learning processes, yes. Michelin built no training environment per instance or language to train its finance teams on Oracle E-Business Suite.
What role do super users play during go-live?
They remain the first line of support. Simulation saves them from repeating demos and in-app help cuts their workload: at Safran Seats, their time spent on support dropped from 25% to 20%.
What should happen during hypercare?
Measure real usage, spot the screens that block users and publish targeted help without waiting for a new release.
What is the difference between a super user and a train-the-trainer approach?
A train-the-trainer approach turns a few experts into trainers who then run sessions. Super users stay in the field after go-live as the first line of support. A simulation serves both: trainers stop repeating demos, and super users can point colleagues to an exercise instead of re-explaining.
Your next go-live

Give us your go-live date. We’ll build the countdown.

We start from your processes and user groups to plan simulation, certification and support through to the end of hypercare.

Book a demo