Change Management for an LMS Launch
Follow

May 14, 2026 17:25

A new LMS rollout is half technical setup, half employee change management. The technical setup gets the most attention; the change management gets less, which is why teams hit the same friction point every time. This guide covers the change management track of an LMS launch — what to communicate, when, to whom, and how.

When this matters

This guide applies to any LMS rollout where the audience is more than a small handful of users — moving from a previous LMS to Continu, launching Continu for the first time, expanding from a single team to the full org, or rolling out a major new feature like Eddy or a Journey-based onboarding flow.

If you’re a small admin team setting up Continu for internal training only and your users are a handful of colleagues, you can skim this. For everyone else, change management is the part of the launch most likely to determine whether adoption sticks.

The three messages you need

Every employee in your audience needs to land on three answers, ideally in this order:

Why this is happening — what changed, what wasn’t working, what the org is investing in
What it means for me — what employees will see, when they’ll see it, what they need to do
How to get help — where to go when something’s confusing, broken, or different than they expected

Most LMS rollouts under-communicate the first one and over-communicate the second one. Skipping the “why” makes the launch feel imposed; over-loading on “what to do” turns the launch into homework before employees have any reason to care.

Why this is happening — what to communicate

A short, honest version of the case for change. Not marketing copy. Examples that land:

“Our previous platform made it hard to find content, and our compliance reporting wasn’t telling us what we needed to know. We picked Continu because it solves both — better search and reporting we can actually use.”
“We’re consolidating six different training systems into one place. By the end of the year, everything you need to learn for your role lives in Continu.”
“We’re investing in skills development for the team. Continu is the platform that supports that — better content, better tracking, and AI-powered just-in-time answers through Eddy.”

What to avoid:

“We chose a new platform that will revolutionize the way we learn.” (No one believes this and no one cares.)
Talking about the procurement process or evaluation. Employees don’t need to know which competitors lost.
Promising things the platform doesn’t do.

What it means for me — what to communicate

The concrete day-one experience. Employees should know:

When access opens for them
How to log in (which IdP, which URL)
What they’ll be asked to do in the first week (any required onboarding, compliance, or assigned content)
What changes for any in-flight training they had on the previous system (carry-over? Start fresh? Lost?)
Where to find content they used to bookmark

If your launch is phased — different teams getting access at different times — say so explicitly. Each cohort should know which wave they’re in.

How to get help — what to communicate

The escalation path, in order of preference:

The help center (link directly to the most-likely-asked article, like signing in or finding content)
Eddy if it’s deployed (where to access it, what kinds of questions it can answer)
The admin team’s internal support channel (a Slack channel, a shared inbox, an internal form)
Their manager (for content or assignment questions specific to their role)

The order matters. Direct people to self-service first; reserve admin team time for what self-service can’t handle.

A communication timeline

The single biggest mistake in LMS rollouts is announcing the platform on launch day. By then it’s too late to set expectations or surface concerns. A typical sequence:

Six weeks before launch — leadership awareness

Share with senior leadership and team leads. Cover:

What’s happening and why
The rollout timeline
What’s expected of leaders during the launch (sponsoring the change, answering team questions, modeling adoption)
How the launch will be measured

Goal: leadership shouldn’t be surprised by employee questions, and should be able to answer them with the same message you’ll send broadly.

Four weeks before launch — broad heads-up

A short, all-hands message from a senior sponsor (the L&D leader, head of HR, or higher). Cover:

The “why” and the “what”
The launch date
That more details are coming
Where to learn more in the meantime (a brief FAQ doc, a Slack channel, an intranet page)

Goal: no one is hearing about Continu for the first time on launch day.

Two weeks before launch — preview to admins and managers

If your launch includes admins and managers (people who’ll have additional roles in Continu), bring them in early. Give them:

Access to a preview environment or the production environment, before full rollout
A short admin walkthrough so they know what they’re working with
A FAQ specific to their role — what they’re being asked to do, what’s optional, where to get help

Goal: by launch day, admins and managers have already touched the platform and can support their teams.

One week before launch — confirmation message

A reminder that lands the week before. Cover:

The exact launch date and time (with timezone)
The first thing they’ll be asked to do
Where to log in
Where to get help

Goal: no one shows up Monday morning surprised.

Launch day — first-touch message

Brief. Cover:

“Access is now open”
The login link
One action to take right now (sign in, check your assigned content, complete a first task)
The help center link

Goal: a clean, low-friction first interaction. Not a long email.

Two weeks after launch — check-in

Cover:

Quick recognition of what’s gone well so far
Any platform feedback being incorporated
A reminder of any in-flight required content (compliance, onboarding)
Continued direction to the help center and support channels

Goal: keep adoption momentum, show that feedback is being heard.

What to send each audience

Different audiences need different versions of the same content. A simple matrix:

Audience	Tone	Length	Most important message
Senior leadership / exec sponsors	Strategic, brief	One page or short email	Why this matters at the org level, what success looks like
Team leads / people managers	Practical, action-oriented	Page or short doc	What they’re being asked to do, what their team will experience
Admins / content creators	Operational, hands-on	Walkthrough or training session	How to do the things they need to do day-one
Compliance owners	Specific, audit-friendly	Memo with timelines	How compliance reporting changes, what’s preserved from the previous system
All employees	Friendly, low-jargon	Short email or Slack message	What’s happening, when it affects them, where to get help

Don’t send the all-employee message to leadership and expect leadership to translate it. Don’t send the admin walkthrough to all employees. Different audiences, different copy.

Practical artifacts to prepare

A short checklist of the change-management artifacts that pay off:

Pre-launch FAQ doc — anticipate the questions employees will ask. “How do I log in?” “What happens to my existing training?” “Will my old completions transfer?” “Who do I contact if something breaks?”
One-page intro for leadership — covers the why, the timeline, the success metrics, and what leaders are being asked to model
Manager talking points — bullet-point version of the announcement that managers can use in team meetings
Admin walkthrough materials — short videos or written guides on the admin features they’ll use most
Launch-day welcome message — drafted and approved before launch week
Internal support channel — a Slack channel, shared inbox, or form where employees can ask launch-week questions and get fast answers
Two-week check-in message — drafted before launch so it doesn’t get forgotten

If you only have time for two of these, prioritize the pre-launch FAQ and the internal support channel. Together they handle the bulk of launch-week confusion.

Measuring change-management success

Beyond technical adoption metrics (logins, content completions, etc.), change management has its own success indicators:

Support volume in launch week — high volume with quick resolution is healthy; high volume with slow resolution is a sign your FAQ and self-service material missed the questions employees actually had
Repeat questions — if you’re getting the same question more than three times from different employees, the answer needs to be more visible. Update the FAQ, repost in Slack, add it to the launch-day message.
Manager support requests — managers escalating to admins for routine “how do I” questions usually means the manager talking points were too high-level. They need the same self-service material as their teams, with the additional context they need to support their reports.
Quiet adoption — employees using the platform without asking questions is the best signal. Quiet adoption means your communication worked.

Common pitfalls

Pitfall	Symptom	Fix
Announcement on launch day with no prior heads-up	Confusion, frustration, low day-one engagement	Communicate the launch six weeks out at minimum; ramp up messaging from there
All audiences get the same message	Leadership feels patronized, employees feel overwhelmed	Tailor by audience — different tone, length, and emphasis per group
Compliance owners not looped in early	Compliance team blindsided by reporting changes mid-launch	Brief compliance owners six weeks out; show them what the new reports look like
No internal support channel	Launch-week confusion spills into IT or HR tickets; admins can’t see the pattern	Set up a dedicated Slack channel or shared inbox before launch day
FAQ written after questions start coming in	Same questions answered ten times before the FAQ catches up	Draft the FAQ in pre-launch based on the questions you anticipate; update post-launch
Two-week check-in skipped	Adoption momentum drops after week one; second-wave questions unanswered	Schedule the check-in message in the launch plan; commit to it

Change Management for an LMS Launch Follow