Home/Trainer's Corner/A Calm Software Rollout
Checklist · 5 min read

A calm software rollout.

Everything to settle before the software reaches anyone's desk, so launch day is uneventful in the best possible way.

A team planning a software rollout together

Rollouts rarely go wrong on launch day. They go wrong weeks earlier, in the things nobody confirmed: who actually needs access, whether the machines can run it, whether enough licenses were bought, and whether anyone is available to teach it.

Work through these before the software goes live, and launch day becomes an ordinary Tuesday.

01

Know exactly who is getting it

Before anything else, settle the list. Not "the sales team" but named people, with the level of access each one needs. This list drives your license count, your training schedule, and your permissions setup, so getting it wrong early costs you three times over.

  • Every user named, with department and role
  • Access level decided per person, not per team
  • Anyone who needs admin rights identified separately
02

Check the machines can actually run it

This is the step most often skipped and most likely to derail a launch. Compare the software's requirements against the computers and laptops your people actually use, not the ones you bought two years ago. Processors vary more than they used to, and a machine that runs everything else fine can still struggle with a new application.

  • Minimum and recommended specs confirmed against real devices
  • Processor compatibility verified, especially on newer or mixed hardware
  • Operating system versions and updates checked
  • A plan for anyone whose device will not make the cut
03

Buy enough licenses, with room to grow

Count from your user list, then add for the hires you already know are coming. Running short mid-rollout means someone sits out their own training session.

  • License count matches the confirmed user list
  • A few spares for new hires and unexpected additions
  • Admin and trainer accounts included in the count
04

Line up the people who will teach it

Somebody has to know the software well enough to answer real questions. That means subject matter experts, trainers, or both, confirmed and available on the dates you need them, not hoping the vendor's recorded demo will do the job.

  • Subject matter experts identified and briefed
  • Trainers confirmed for every session and shift
  • Someone named as the go-to for questions after launch
05

Decide how you will reach everyone

If you do not have enough trainers to cover every person in a room, decide now how you will close the gap. A learning management system for self-paced modules, live webinar sessions for larger groups, or a train-the-trainer approach where you build in-house experts who carry it forward.

  • Delivery method chosen for each group and shift
  • Learning management system set up, if you are using one
  • Webinar sessions scheduled and tested
  • Quick-reference guides ready for people to keep at their desks
The part everyone gets wrong

Train about two weeks before launch

Training has to happen before the software goes live, but not too far before. Teach people two months out and they will have forgotten most of it by the time they can use it, because nothing reinforced it in between. Teach them the morning of launch and you have no time to fix what did not land.

Roughly two weeks is the sweet spot: recent enough to be fresh, with enough runway to run a second session for anyone who needs it.

Too early
Six weeks or morePeople forget. Nothing they learned gets used, so nothing sticks.
About right
Roughly two weeksFresh at launch, with time to catch anyone who needs a second pass.
Too late
Launch dayNo room to fix gaps. Questions arrive while people are trying to work.
One more thing: plan the week after launch too. Someone available for quick questions in those first few days prevents the quiet drift back to the old way of doing things.
Related resources

Keep exploring

Rolling something out this quarter?

We plan rollouts so launch day is uneventful.

Training, documentation, and a schedule that fits around how your team actually works.

Book a Discovery Call →