How-to guides

How to train employees on new software

The best way to train employees on new software is to teach the tasks each role does, close to go-live, and to have people do each task themselves before it counts. Below is a six-step method with a worked example and the sums.

Updated

How-to guides
Short answerList the tasks each role does in the new system and pick the 10 to 20 that matter most per role. Choose a format for each task: show it, let people practise it, check it, or give them a reference page. Run the training in the last three weeks before go-live, keep help close for the first four weeks after, and measure what people can do.

Start from the job, then open the software

Most rollout training is built around the software: a tour of the menus, module by module, delivered once to everyone. People leave knowing what the system contains and still cannot do their own work in it on Monday morning.

A sales rep's job in Salesforce comes down to a dozen tasks: convert a lead, log a call, move an opportunity to the next stage, raise a quote. An accounts payable clerk in a new ERP has a similar list that starts with posting a supplier invoice. Training works when each person has done their own list with their own hands before the old system is switched off.

The method in six steps

  1. Work out who does which tasksList the roles, count the people in each and write down what each role will do in the new system.
  2. Pick the 10 to 20 tasks that matter per roleTrain the frequent and the costly ones. Document the rest.
  3. Choose a format for each taskShow it, let people practise it, check it, or only give a reference.
  4. Schedule it close to go-liveEnd users in the last three weeks, in short sessions. Super users and trainers much earlier.
  5. Support people through the first weeksSomeone to ask on the floor and one place to send questions.
  6. Measure what people can doChecks passed before go-live. Errors, task times and tickets after.

Step 1: work out who does which tasks

Sit down with the process owner for each area and list the tasks in verb and object form: "post a supplier invoice", "convert a lead", "log an incident". Group people by the job they do. Two people with the same system permissions can do very different work, which is why Microsoft's implementation guide for Dynamics 365 advises defining training personas by business role, not by security role.

The output is a grid with roles across the top, tasks down the side and a headcount per role. The software training plan template has a filled-in example you can copy. Super users and approvers need different training from everyone else, and end user training sorts those groups out.

Step 2: pick the 10 to 20 tasks that matter per role

Say the first list for a service agent comes to 40 tasks. Ask two questions of each one. Does an agent do this every week? Would a mistake cost money, a customer or a compliance finding? That might leave 14 tasks. Those get trained. The other 26 still get written up, as reference pages people can find when the need arises.

The range of 10 to 20 is a working rule. A list shorter than 10 usually means several tasks have been lumped into one, and "manage orders" cannot be taught or checked. Above 20, people will not get through the training in the weeks you have.

Step 3: choose a format for each task

There are four things you can do with a task. You can show it in a demo, live or recorded. You can let people practise it, on a software simulation or in a training copy of the system. You can check it by scoring an unaided attempt. And you can give people a reference to look up while they work. Few tasks need all four.

Kind of taskExampleShowPractiseCheckReference
Daily and simpleLog a call against a contactTwo-minute demoOne guided runNo formal checkNot needed after week one
Daily and complexConvert a lead and raise a quote with three productsDemo with the reasons for each fieldRepeat until done without hintsScored unaided run before go-liveOne-page guide
RareReassign accounts when a rep leavesShort recorded demoOptionalNoneStep-by-step guide, easy to find on the day
High risk: money or complianceChange a supplier's bank detailsDemo that includes what goes wrongSeveral runs, including a wrong onePass mark required before access is grantedGuide plus who to call
Judgement and exceptionsDecide whether a discount needs approvalWorked cases in a live sessionTalk through real casesManager reviews the first few real onesThe policy, one page

The show, practise, check sequence has a longer name in training circles, show me, try me, test me. Rare tasks are the case for just-in-time learning: nobody remembers a year-end step taught in February, so put the guide where people will look in December.

A worked example: 220 people moving to Salesforce

Say you are the training lead at a company moving its sales and service teams onto Salesforce. There are 140 sales reps, 60 service agents and 20 managers. After steps 1 and 2 the reps have 12 tasks, the agents 14 and the managers 6. You allow 20 minutes a task: a demo, a couple of practice runs and a check.

4 hPer sales rep

12 tasks at 20 minutes. 140 reps makes 560 hours.

4 h 40Per service agent

14 tasks at 20 minutes. 60 agents makes 280 hours.

2 hPer manager

6 tasks at 20 minutes. 20 managers makes 40 hours.

880 hWhole rollout

Against 1,760 hours for a one-day class for all 220.

That is half the time away from work that an eight-hour day for everyone would take, and each person spends it on their own job. The price falls on you: 32 task lessons to build and keep current. If a lesson takes half a day to record, build and review, that is 16 working days.

Step 4: schedule it close to go-live

Train end users in the last three weeks before go-live, in sessions of an hour or less, with catch-up slots in the final week. Microsoft's guidance puts the principle well: train system users late enough that they have not forgotten by go-live, and leave room for the project to slip. The same guide says it is never too early to train super users and trainers, because they have to help everyone else.

A note on forgetting statistics

You will see it claimed that people forget 90 per cent of training within a month. Figures like that trace back to Hermann Ebbinghaus memorising lists of nonsense syllables in the 1880s, an experiment replicated in 2015 with the same kind of material. Nonsense syllables are a long way from converting a lead, so distrust the exact number. The direction is safe to plan on: a task you were shown once and have not done since fades.

If go-live moves by more than a fortnight after people have trained, run a short refresher in the final week.

Step 5: support people through the first weeks

However good the training, day one produces questions. Put a super user or floor-walker with each team for the first two weeks. Give people one place to ask, such as a chat channel or a help desk queue, and tag every question with the task it was about. Keep the guides and the practice lessons open for new starters. If you have a digital adoption platform, this is where its on-screen prompts help most.

By Friday of the first week the tags will show which few tasks cause most of the trouble. Fix those guides and rerun those lessons first.

Step 6: measure what people can do

Attendance tells you who was in the room. Before go-live, the number to report is the share of each role that has completed its key tasks unaided. After go-live, watch error rates, time per task and tickets per task, week by week.

Microsoft's guide suggests timing a "day in the life" task against the target for the job. Its example is a call centre agent expected to handle six calls an hour, who should therefore be able to complete one call from start to finish in the system within 10 minutes. For the wider picture, see how to measure training effectiveness and, for the months after go-live, user adoption.

If people pass the checks and the system still goes unused, look outside the training. Change management covers the rest of a rollout, and the ADKAR model is a quick way to find what a team is missing.

The four mistakes that cost most

Training too early

Training gets booked for when rooms and trainers are free, and that can be six or eight weeks before go-live. Clarkston Consulting's advice on SAP projects names both edges: train too late and you risk disruption at go-live, train too early and you will need refreshers. Budget for the refresher or move the dates.

Training features instead of tasks

Feature agenda
  • The Leads tab
  • The Opportunities tab
  • Reports and dashboards
  • Settings and personalisation
Task agenda
  • Convert a lead from a web enquiry
  • Log a call and book the follow-up
  • Move an opportunity to "Proposal"
  • Find your open quotes for the week

The left-hand agenda is quicker to write because it follows the vendor's menu. Only the right-hand one can be practised and checked.

One long session

A full training day is easy to schedule and hard to learn from. By the afternoon people are being shown their twentieth screen, and anyone off sick has missed the whole course. Short sessions across a fortnight let people try a task and come back with questions.

No practice

Watching a demo gives people the feeling that they could do the task. The first time they find out for certain is when they try, and that should happen somewhere safe: a sandbox or a simulation, with nobody's real order at stake. If your plan has no line for hands-on training, it is a communication plan.

Where Recourse fits

Practice for each task, built from a screen recording

Recourse turns a recording of someone doing a task into three things: a Demo to watch, a Practice mode on a replica of the screen with hints that escalate, and an Evaluate mode that scores an unaided run against a pass mark. That covers show, practise and check for the daily and high-risk rows in the table above. The limits matter. The replica follows the task you recorded, so it is not a sandbox and people cannot explore the rest of the system in it. It does not put prompts on top of the live system, it is not an LMS, and it exports SCORM 1.2 only. There are buyer guides for Salesforce rollouts and ERP go-lives.

Start free

Questions people ask

What is the best way to train employees on new software?
Train tasks, by role. List what each role does in the system, pick the 10 to 20 tasks that matter most, show each one, let people practise it and check they can do it unaided. Run it in the three weeks before go-live and keep help on hand for the first weeks after.
How do you roll out new software to employees?
Tell people early why the change is happening and when. Train super users first, then end users close to go-live. Put support on the floor in the first two weeks and close the old route once the new one is working. Training is one part of the rollout. The rest belongs to change management.
How far before go-live should you train employees?
End users in the last three weeks, so the tasks are fresh on day one and there is still time for catch-up sessions. Super users and trainers should start months earlier, because they test the system and help everyone else.
How long should training on new software take?
Count tasks, then multiply. Allowing about 20 minutes a task for a demo, practice and a check, a role with 12 tasks needs about four hours. A role with 6 tasks needs two. A flat one-day course for everyone gives some roles too much and others too little.
How do you know the training worked?
Before go-live, by the share of each role that has completed its key tasks unaided. After go-live, by error rates, time per task and help desk tickets per task. Attendance and satisfaction scores tell you much less.

Sources

Keep reading

Last reviewed 21 November 2026. Recourse publishes these guides for learning, customer education and change teams. Details drawn from public sources can change.