QuikAuthor

In-Depth Guide

Change Management Training: Teaching People the Change, Not the Theory

Most change programmes buy training for the people running the change and almost none for the people living through it. This guide is about the second group: what they have to learn, when each piece should exist, and how to keep it accurate while the change is still moving.

Most change programmes buy training twice and get it wrong once. They buy a framework course for the handful of people running the change, which is reasonable, and they assume the people living through it will pick the rest up from a town hall and a slide deck, which is not. This guide is about the second group. What the affected population actually has to learn, why that content goes out of date faster than anything else L&D produces, when each piece should be built, and how to keep it accurate while the change is still moving underneath it.

Why Does "Change Management Training" Mean Two Different Things?

Search the phrase and you get two completely different kinds of page back, which is a reliable sign that there are two completely different buyers.

The first is training in change management as a discipline. The named models, stakeholder mapping, resistance, sponsorship, communications planning. Its audience is project leads, HR business partners and the sponsor. It is a professional skill, the content is generic on purpose, and it is bought as a course or a certification from an organisation that sells one. Nothing in this guide helps you choose between the models, and QuikAuthor does not sell a course on them.

The second is training people on the change itself. The new system, the new process, the new policy, the new approval route, the new reporting line. Its audience is everybody affected. The content is specific to your organisation, nobody can sell it to you because nobody else has it, and it is the half that decides whether the change actually lands. It is also the half that gets squeezed, because it only becomes buildable once the detail is settled and the detail tends to settle about a fortnight before go-live.

A programme can do the first perfectly and still fail on the second. People rarely resist a change they understand and can perform. They resist the one where the old way has stopped working and the new way has not been explained to them yet.

A woman presenting at a board covered in sticky notes to a small group in an office

Who Needs What, and When?

Six audiences, and treating them as one is the most common planning error in the whole exercise. The sponsor and the person who will actually use the new screen need opposite things at opposite times.

AudienceWhat they needWhen it has to existHow long it stays true
Sponsor and steering groupThe case, the measures, and the answers to what they will be asked in a town hallBefore the announcementThe length of the programme
Project and change leadsThe discipline itself: models, stakeholder mapping, communications planningBefore the detail existsYears, because it is a career skill
Line managersWhat changes for their team, the questions they will be asked, and what to do with a complaintA clear week before their team hears itResets at every scope change
The affected populationHow to do their own job the new way, start to finishClose to go-live, not months beforeDays at first, then weeks
Service desk and super usersThe new way, plus the twenty things that will go wrong and what to say about eachBefore go-live, in more depth than anyone else getsUpdated daily through hypercare
Everyone who joins afterwardsThe new way only, with no reference to the old oneThe week after go-live, and permanentlyIndefinitely

The last row is the quiet failure. A programme closes, the team disbands, and eighteen months later the induction pack is still teaching the process that was replaced, because nobody owned the job of folding the change back into business as usual.

What Does the Affected Population Actually Have to Learn?

Six things, in this order. Most change training delivers the third one on its own and wonders why adoption is poor.

  1. Why, in one honest paragraph. Not the strategy deck. The reason this is happening, said plainly, including the part that is uncomfortable. People extend enormous patience to a change whose logic they can repeat to a colleague, and none at all to one that arrived as an instruction.
  2. What is different for me specifically. The affected population is not one group. A change that is trivial for finance can be the whole working day for the service desk. The useful version of this is a short, role-specific answer rather than a long, universal one.
  3. The task, performed start to finish. The single most valuable asset in any change programme is somebody competent doing the new thing once, end to end, narrating it. Everything else is commentary on this.
  4. The exceptions. The refund that does not fit, the record that will not migrate, the customer who is on the old contract. Exceptions are where confidence collapses, and they are almost always left out because they are not settled when the main material is written.
  5. Where to go when it does not work. Named route, named owner, expected response. A change with no visible support route trains people to invent a workaround instead, and workarounds invented in week one outlive the programme.
  6. What stays the same. Consistently omitted, and reassuring out of all proportion to the effort of saying it. A list of what is not changing shrinks the perceived size of the change more effectively than any amount of persuasion about the parts that are.

Why Does Change Training Go Stale Faster Than Anything Else?

Because it is written against a moving target, and three things move independently.

  1. The detail settles last. Configuration decisions, approval thresholds and screen layouts are still being argued about while the training window is closing. Build early and you train people on a version that will not ship. Build late and you are producing the material in the same week as the cutover.
  2. Go-live itself changes the content. The first fortnight generates more accurate training material than the whole design phase did, because real people meet real edge cases. Any programme that treats go-live as the end of content production is throwing away its best source.
  3. The change iterates afterwards. Phase two lands, a workaround becomes permanent, a field is renamed. Each is small, and each quietly invalidates a lesson somewhere. The cost of a change programme is not the build; it is the republish, and that is the line almost nobody budgets. Our guide to eLearning development costs covers where that line usually hides.

The practical consequence is a production rule: for change content, build thin and republish often, rather than building thoroughly and republishing never. A perfect forty-minute module on a process that changed last Tuesday is worth less than a rough four-minute one that is current.

When Should Each Piece Be Built?

Five windows. The ordering matters more than the quality of any single piece.

  1. Before the announcement. The sponsor's answers and the line-manager briefing. Managers hearing about a change at the same time as their teams is the single most expensive sequencing error available, because the only people positioned to absorb the first wave of questions have no answers.
  2. Between announcement and go-live. The why, the what-is-different-for-me, and the what-stays-the-same. Deliberately not the detailed task training. Teaching somebody a screen they cannot access for six weeks produces nothing but a completion record.
  3. The fortnight before cutover. The task training proper, built from whatever the configuration finally settled on. This is the window that is always too short, which is why the source material has to be something that already exists rather than something that has to be written from scratch.
  4. Hypercare. Short, fast corrections produced from what the service desk is actually being asked. The best change training in most organisations is written in week two by somebody answering the phone, and it never makes it into the course because the republish cycle is too slow to be worth it.
  5. After the programme closes. The induction version. Same content, past tense removed, no comparison to the old way, owned by whoever owns onboarding rather than by a project team that no longer exists.

What Source Material Do You Already Have?

More than most teams realise, which matters because window three is the one with no time in it. Before commissioning anything new, go and find:

  1. The vendor's own training deck or help documentation, which covers the generic product and needs your configuration layered on top rather than a rewrite.
  2. The recorded system demonstration from the selection process or the design workshops. Usually an hour long, usually watched once, and containing the end-to-end walkthrough that item three on the learning list is asking for.
  3. The new or revised standard operating procedure, which is the approved description of the new way and the only one anybody will defend in an audit.
  4. The revised policy, where the change alters a rule rather than a task.
  5. The super user's screen recording, made on their own laptop in ten minutes, which is routinely more useful than anything produced to a higher standard a month earlier.
  6. The project FAQ document, which is already a list of the questions people actually have, in their own words, and is therefore a ready-made outline.

A tool that can turn a document, a deck or a recording into structured lessons changes the economics of window three completely, because the job becomes correcting a draft rather than starting a blank page.

How Do You Keep Training Accurate While the Change Is Still Moving?

Four habits, and none of them is about the quality of the content.

  1. Separate the why from the how. Put the rationale in its own short lesson and the task in another. The rationale survives three rounds of scope change; the task does not. Keeping them together means re-recording a stable thing every time an unstable thing moves.
  2. Version deliberately, and track the versions apart. When the process changes, regenerate and reassign rather than editing in place and hoping. If you cannot tell who completed the current version as distinct from the superseded one, your completion report is describing a process that no longer exists.
  3. Route by role instead of writing by role. One build with branching will carry three audiences further than three builds that all have to be maintained when the shared part changes.
  4. Budget the republish before go-live, not after. The hypercare corrections are the highest-value training in the whole programme and they are the first thing cut, because by then the budget is spent and the team is tired. Naming the line in the original plan is the only reliable defence.

How Do You Tell Whether the Training Worked?

Not by completion rates, which measure delivery rather than capability. Three better signals, in increasing order of effort:

  1. Question-level responses rather than pass rates. A pass rate tells you the cohort cleared the bar. The distribution of wrong answers tells you which step of the new process is not landing, which is the thing you can act on this week.
  2. The shape of the support queue. Change programmes already collect this, in the service desk categories. If the same question is asked two hundred times in week one, that is a missing lesson with a precise specification attached.
  3. Whether the old way is still happening. The only measure that matters in the end, and it usually lives in operational data rather than in the LMS: the spreadsheet still being maintained, the old form still being submitted, the shadow process still being run.

It is also worth asking whether training was the right intervention before measuring how well it was delivered. A change that fails because the new process genuinely takes longer is not a knowledge problem, and no amount of training will fix it. Our training needs analysis guide covers the can't-do versus won't-do test that separates the two.

How This Fits With QuikAuthor

QuikAuthor is an authoring tool, so it serves the second kind of change management training and not the first. Specifically, the parts of the job that are production problems:

  1. Turning what already exists into lessons. The AI Asset Converter takes a PDF, a Word document, a PowerPoint deck, an audio file or a video and turns it into structured lessons with draft knowledge checks. That is the six source materials above, converted rather than rewritten.
  2. Keeping the recording. The AI Video Editor keeps the footage instead of extracting from it: upload the system walkthrough, and it transcribes, detects logical break points to split it into lessons, and generates contextual quizzes from each segment. For an end-to-end demonstration, that is usually what you want.
  3. The policy half. Where the change alters a rule rather than a task, Compliance Builder reads the policy you upload and writes knowledge checks traceable to specific requirements in its text, defaulting to a 100% pass rate.
  4. Republishing when it moves. Upload the revised document and regenerate, then track who has completed the updated version separately from the previous one.
  5. Routing by role. Branching is included on every plan and can route on a learner choice, a quiz result, a skip decision or a confidence rating.
  6. A face on the rationale. AI Avatar Video puts a presenter in the lesson without a camera or a studio, and AI voiceover generates narration from your script with synced captions created automatically. Free plans get two avatar credits per month and Pro gets ten, and building a clip with Google's free tools and uploading it uses none.
  7. Getting it to people and proving they did it. Assign to individuals or whole teams, set due dates, let automated reminders chase what is outstanding, filter completion by team, location or department, and issue branded certificates automatically. Courses also export as SCORM 1.2 or SCORM 2004 if the record belongs in your own LMS.
  8. Multi-site changes in one build. AI Translation supports 20 languages and preserves your design, layout and formatting, so a process change reaching four countries is one build rather than four.

The free plan covers 25 courses and up to 50 active monthly learners with every AI feature, no credit card and no expiry, which is enough to pilot one role's task training before the programme commits to anything.

Where This Guide Stops

Four things a change programme needs that an authoring tool does not provide, and it is worth being plain about all four.

  1. The discipline itself. If what you want is a course teaching your project leads a change management model, buy one from somebody who sells it. QuikAuthor builds courses from your material and ships no library on the subject. A pre-created course library is listed on the roadmap as upcoming rather than available.
  2. Readiness and sentiment measurement. Pulse surveys, readiness assessments and resistance mapping are a real part of the discipline, and QuikAuthor has no survey tool. What it measures is whether somebody can answer questions about the new process correctly, which is a different thing and not a substitute.
  3. In-application guidance. If the requirement is step-by-step prompts overlaid inside the new system while somebody uses it, that is a digital adoption platform rather than an authoring tool. The two are complementary and only one of them is being described here.
  4. Reinforcement drip-fed over weeks. QuikAuthor does not have spaced repetition. For a change with a long embedding period, that is worth naming, because the mechanism available here is republishing when the process moves rather than scheduled reminders of a version that may have moved already.

Frequently Asked Questions

What is change management training?

Change management training covers two different things that share a name. One is training in the discipline of managing change, aimed at project leads and sponsors, covering models, stakeholder mapping, resistance and communications planning. The other is training the people affected by a specific change on what is actually changing for them: the new system, process, policy or structure. The first is a generic professional skill you can buy. The second is specific to your organisation, has to be built, and is the half that determines whether the change is adopted.

Who needs change management training?

Six audiences with different needs and different timings. Sponsors need the case and the answers they will be asked in public. Project and change leads need the discipline itself. Line managers need to know what changes for their team, a clear week before the team hears about it. The affected population needs to perform their own job the new way, close to go-live rather than months ahead. The service desk and super users need more depth than anyone, before go-live. And everyone who joins after the programme closes needs the new way taught as business as usual, with no reference to the old one.

When should change training be delivered?

In five windows, and the sequence matters more than the polish. Sponsor answers and manager briefings before the announcement. The why, the what-is-different-for-me and the what-stays-the-same between announcement and go-live. Detailed task training in the fortnight before cutover, once the configuration has actually settled. Fast corrections through hypercare, built from what the service desk is being asked. And an induction version after the programme closes, owned by whoever owns onboarding.

Why does change management training go out of date so quickly?

Because three things move independently. The configuration detail settles last, often while the training window is already closing. Go-live itself generates more accurate material than the design phase did, as real users meet real edge cases. And the change keeps iterating afterwards, as phase two lands and workarounds become permanent. The practical response is to build thin and republish often rather than building thoroughly and republishing never.

How do you train people on a process that is still changing?

Separate the rationale from the task, because the rationale survives scope changes and the task does not. Version deliberately and track completion of the current version separately from the superseded one. Route by role with branching rather than maintaining several near-identical builds. And budget the hypercare republish before go-live, because it is the highest-value training in the programme and the first thing cut once the money is spent.

Can QuikAuthor build training for a system or process change?

Yes, for the production side of it. The AI Asset Converter turns a PDF, a Word document, a PowerPoint deck, an audio file or a video into structured lessons with draft knowledge checks, so the vendor deck, the new standard operating procedure and the recorded walkthrough become a course rather than a reading list. The AI Video Editor keeps the footage instead, transcribing a recorded demonstration, splitting it at logical break points and generating contextual quizzes from each segment. Where the change alters a rule rather than a task, Compliance Builder writes knowledge checks traceable to specific requirements in the policy you upload.

How do you keep change training current after go-live?

Upload the revised document and regenerate the course, then track who has completed the updated version separately from the previous one. That matters more on a change programme than on almost any other training, because the version people completed in the week before cutover is frequently not the version that shipped, and a completion report against a superseded process is evidence of nothing.

Does QuikAuthor measure change readiness or resistance?

No. QuikAuthor has no survey tool, so pulse surveys, readiness assessments and sentiment tracking are outside what it does. What it measures is whether a learner can answer questions about the new process correctly, broken down to individual question responses so you can see which step is not landing. That is capability rather than sentiment, and a change programme usually needs both.

How much does change management training cost to produce?

The build cost depends far more on how much source material already exists than on the size of the change, because converting a document or a recording is a different job from writing from a blank page. On the tooling side, QuikAuthor's free plan includes 25 courses and up to 50 active monthly learners with every AI feature, no credit card and no expiry. Pro is $69 per author per month, or $799 per year, with up to 200 active monthly learners. Team is $2,000 per year for three authors. The line most change budgets miss entirely is the republish cycle after go-live, which our guide to eLearning development costs works through.

Build the First Lesson Before the Configuration Freezes

Take the recorded walkthrough or the draft standard operating procedure you already have, turn it into one role's task training, and find out how long the real cycle takes before the programme depends on the answer. QuikAuthor's free plan includes 25 courses, up to 50 active monthly learners and every AI feature, with no credit card and no expiry.

Ready to build courses with AI?

Free plan available. No credit card required.