User training occupies an uncomfortable place in the schedule of a roll-out: it needs a tool stable enough to be shown, and it must come shortly before first real use. Its sessions are therefore placed, for the most part, between the end of acceptance testing and go-live, in an interval that any project delay shortens.
This workstream is decided point by point: the audiences, the timing, the format (classroom, remote, coaching by champions, help built into the tool), the people who design and those who deliver, the check on the effect. It also has a limit, to be stated from the outset. A business case missing from the tool, a missing access right or an instruction that management has not given cannot be resolved in a training room.
Audiences divided by role, content drawn from real work
The audience for a training course is defined by what the person will do in the tool. A division by department or by hierarchical level can bring together in the same room people who will not have the same screens. Division by role starts from the list of populations and the impact analysis, where the project has produced them; how they are built is described in our article on the change management plan.
Each role receives content built on its work situations: handling a routine case, handling the special case that comes up regularly, correcting an error, knowing whom to contact. The cases run through in acceptance testing by users provide material that has already been tested, complete scenarios on representative data, as our article on user acceptance testing explains.
Some audiences may be forgotten: managers, who approve or read reports without entering data; occasional users; the support team, which must have seen the tool before the first call. For people who will join the team after the roll-out, the programme provides from the outset for what will remain available once the project has closed.
A date set by first real use
Training taken long before first use risks being forgotten; our service page places it shortly before go-live. The useful reference point is, for each audience, the date on which it will carry out for the first time the task it is being prepared for. In a roll-out in waves, that date differs from one site to another. For a periodic task, such as a monthly close or an annual campaign, it may fall well after go-live, and the corresponding sequence is placed at that time.
Upstream, the tool must be stable enough for the screens shown to be those of the first day, and a training environment must exist, with plausible data. Downstream, the teams must be able to be released: a session placed during a busy period for the business may be held in front of empty chairs.
The window is calculated early, on simple quantities. Take, as a hypothesis, a logistics provider that brings a warehouse management tool into service on the same day across 6 sites. Each site has 30 order pickers, 4 team leaders and 2 stock controllers, that is 180 pickers, 24 team leaders and 12 stock controllers: 216 people. At 10 pickers per session, 18 sessions are needed, 3 per site. In the same hypothesis, a trainer who runs 2 a day totals 9 days of sessions, travel not included. If the organisation sets a window of 5 working days before go-live, a single trainer is not enough: 2 are needed, or another format for part of the audience.
Classroom, remote, coaching by champions or help built into the tool
These formats combine more than they replace one another, depending on the audience and the action to be learnt.
| Format | Suits | What it requires |
|---|---|---|
| Classroom session | A new action, a process that changes, an audience unfamiliar with IT tools | An equipped room per site, a trainer, teams released |
| Remote session | A dispersed audience, short content, users accustomed to similar tools | A workstation and a quiet moment for each person, a facilitator who has participants practise |
| Coaching by champions | The first real cases, a team’s special cases | Champions trained before the others and relieved of part of their work |
| Help built into the tool | A reminder of an action already seen, occasional tasks, newcomers | Content updated with each change to the tool, by a designated person |
In the hypothesis of the 6 warehouses, coaching changes the calculation. The 24 team leaders, trained first in 2 remote sessions of 12 people, can support the pickers at their workstations: 180 pickers for 24 team leaders, that is 7 or 8 each. The choice then falls to site management, because a team leader busy with this coaching during start-up does not perform their usual role at the same time.
Who designs user training, who delivers it
Designing means choosing the situations, writing the exercises and materials, preparing the environment. This work requires knowledge of the business and of the tool as it has been configured: we propose entrusting it to a business lead and a person from the project, overseen by the person who holds the change management plan. A training aid taken unchanged from a vendor’s documentation describes the standard product and may leave out the business rules specific to the organisation.
For delivery, we propose a division according to the audience: a trainer from the project or the integrator for administrators and champions. For other users, a business champion has an advantage: they talk about the team’s cases and remain on site after the session. The presence of the line manager, at least at the opening, can signal that the new practice is expected.
The programme includes what follows the session: a quick reference guide per role, support in the first days, and a solution for those who were absent.
Checking the effect, and recognising what is not a training matter
Counting attendees and gathering their feedback at the end of the session shows how the programme ran. The effect is checked elsewhere, on the work. We propose three observations, with no threshold: an end-of-session exercise in which each person handles a case from their role alone; observation of the first real cases by the champions; the nature of support requests in the first weeks. Requests that concern an action that was taught point to a sequence to be repeated, for a specific audience.
A difficulty in use may have a cause other than a lack of know-how. Several are checked before any new session:
- the user’s case does not exist in the tool: a defect or a change request, to be examined by the project;
- their access rights do not match their role: a setting to correct;
- they do not see why the practice is changing: a matter of communication and management;
- the old tool remains accessible and management does not require the new one: a management decision;
- there is not enough time to practise: the team’s workload to be lightened.
The ADKAR model entry gives a grid for locating what a population lacks, and our article on resistance to change a diagnosis by cause. In an IT project, sessions built on the application’s menus are among the signs noted in our article on change management in an IT project.
In our change management assignments, training the users affected by the project is one of the workstreams of the support we provide: role-based learning paths, built on real work situations and scheduled as close as possible to go-live, with the materials and support for the first days.