When a Company Changes a Process, the Training Must Change More Than Knowledge

A company introduces a new platform. The training shows employees where to click, how to log in, and how to complete a form. Everyone finishes the course before launch.

Then the platform goes live, and people keep using the old spreadsheet.

Did the training fail? Perhaps it taught the system but missed the change.

When an organization changes a procedure or moves from paper to digital work, employees need more than instructions for the new tool. They need to understand why their familiar way of working is changing, recognize exactly what will be different, practice the tasks they will perform, and feel able to do them without a trainer beside them.

That is a learning design challenge. It is where the training department has an important role in change management.

Begin with “Why are we changing this?”

In my experience, the first question employees ask is often, “Why are we changing this?” The next is, “What’s in it for me?”

I always address those questions at the beginning of training on a change. Before showing the new steps, I explain the reason for them. I highlight how the change may make employees’ work easier, help them avoid mistakes, or solve a problem they already experience.

Imagine a paper form that frequently arrives at the next department with missing information. A digital version with required fields could catch some of those omissions before submission. Showing that connection gives meaning to the new steps employees are about to learn.

The explanation must be honest. A change may benefit the organization without making every part of every employee’s day easier. If the new process adds a step, acknowledge it. Employees can judge the training against their own experience, and an exaggerated promise can undermine the rest of the course.

Show precisely what is changing

A common approach is to teach the new procedure from start to finish. But employees already know a procedure. Their challenge is to identify where the new one differs from what they do today.

That is why I create side-by-side visuals: what happens now beside what will happen after the change. The comparison helps employees see which steps stay the same, which move, which disappear, and which responsibilities shift to someone else.

For a paper-to-digital transition, the visual might show that an employee currently completes a form and sends it to a supervisor, who passes it to an administrator. Under the new process, the employee enters the information directly, the supervisor reviews it in the platform, and the approved record becomes available to the next team.

A system demonstration shows how to enter the information. The comparison shows how the work itself changes.

It also helps the training designer find gaps. What if a form needs correcting after approval? What happens when the supervisor is away? Those situations may require practice examples, a job aid, or an answer from the process owner before the course is finalized.

Design practice around real tasks

Employees do not use a new system as a collection of menus and features. They use it to complete work.

Training should therefore be built around the decisions and tasks each group will face. The employee creating a record needs different practice from the supervisor approving it. A person handling an exception may need more than the standard “happy path.”

I would rather have employees practice a few realistic situations than watch a tour of every feature. Let them submit a record with missing information. Let them find and correct an error. Let them decide what to do when a request does not fit the usual steps.

Practice gives employees a chance to make sense of the change before the stakes are real. It also shows the training team which parts of the new process need a clearer explanation.

Train managers and supervisors first

In my experience, managers and supervisors should be trained before employees. Once a change launches, they are often the people employees turn to with questions.

Training them first gives them time to try the procedure, identify uncertainties, and understand where to take questions they cannot answer. It also gives the training department a valuable opportunity to improve the employee training before it reaches the wider team.

Managers do not necessarily need a longer version of the same course. They may need practice with approvals, exceptions, and the questions their teams are likely to ask. Their training should prepare them for their role in the new process and for the support employees will need while learning it.

Blend learning across the transition

The change curve reminds us that people may respond differently as a change unfolds. Some are ready to experiment quickly. Others need more time, clearer answers, or reassurance that they can make a mistake while learning. The curve is a prompt to consider these needs, not a fixed sequence that every employee follows.

This is one reason I see value in blended learning for change. A single course delivered before launch cannot do everything.

• A short introduction can explain the reason for the change.

• A side-by-side visual can clarify the new workflow.

• A live session can give employees space to ask questions.

• Self-paced scenarios can let them practise role-specific tasks.

Each format answers a different learning need.

Then, when employees begin using the new procedure, they need support within reach. I always create a job aid they can refer to at the beginning of the change. It helps them check the steps while doing the work and gradually build confidence in the new process.

The job aid is part of the training design, not an afterthought. Its purpose is different from the course: it helps someone perform a task at the moment they need to do it.

Design for the first day and the weeks after

A course completion report can tell us who finished training. It cannot tell us which step employees will forget on their first busy day or which exception will cause confusion two weeks later.

That is why training for change should be designed with follow-up in mind. The training department can review the questions employees ask after launch and use them to improve a job aid, add a short practice activity, or clarify an instruction. If a problem comes from the procedure or system itself, the training team can bring that finding to the people responsible for it.

The goal is not to keep employees in training indefinitely. It is to help them move from understanding the new way of working to using it with confidence.

When a company changes a process, the training department’s contribution is not simply to explain what is new. It is to design the learning journey between “This is how I’ve always done it” and “I can do this in my work now.”

That journey deserves more thought than a system walkthrough.