The course isn’t the problem. The launch is.
Every L&D team I know has had this conversation. Completion rates are flat. The post-course survey scores are middling. Someone in the room suggests the module needs more interactivity, better video, and maybe a scenario branch or two. The instructional designer nods politely while quietly knowing the truth: the course was probably fine. The rollout killed it.
I’ve watched perfectly solid compliance modules get torched by a single badly-worded email from a regional manager. I’ve also seen a fairly ordinary induction course crush its engagement targets because the executive sponsor recorded a thirty-second intro video and the rollout was sequenced properly. The difference wasn’t the build. It was everything that happened in the two weeks before launch.
Learners decide whether to engage before they click “start”
By the time someone opens a module, they’ve already formed a view about it. They’ve seen the calendar invite, the Teams message, the manager’s offhand comment in a stand-up. They know whether this is “the new safety training the GM actually cares about” or “another tick-box thing HR is making us do.” That framing locks in attention before the splash screen loads.
This is the part of elearning development services Australia clients tend to underestimate. We can spend twelve weeks crafting scenarios, recording voiceover, running accessibility checks, building branching logic that responds to the learner’s role. None of that survives contact with a launch email that opens with “As per our compliance obligations, you are required to complete the following mandatory training by…”
You’ve just told everyone the training is a chore. They will treat it like one.
What pre-launch communication actually needs to do
Three things, really. Tell people why this exists. Tell them what’s in it for them or for the people they work with. Tell them roughly what to expect, including how long it will take. That’s it. The tone should match how your organisation actually talks, not how the legal team writes.
A practical example. We worked with a state government agency on a workplace behaviour module. The original draft of the launch comms was about 400 words of policy citation. We pushed back, hard. The Director ended up sending a short note that essentially said, “We’ve heard from a lot of you that the old training felt disconnected from the work. We rebuilt it. It runs about 25 minutes, the scenarios are based on real situations from your teams, and I’d like your feedback after you’ve done it.” Completion in the first fortnight was over 80 percent. The previous version of that program had limped to 60 percent over three months.
Same audience. Same LMS. Different framing.
Manager involvement is the variable nobody controls for
Frontline managers and team leaders set the temperature. If they treat the training as important, their team treats it as important. If they roll their eyes and say “just get it done before end of month,” you’ve lost. Most rollout plans I see don’t account for this at all. They send comms to learners and assume managers will fall in line.
A better pattern: brief managers a week before learners get access. Give them a one-page summary of what’s in the course, why it was built, what their team will get out of it, and three or four talking points they can drop into a team meeting. Don’t make them read the course themselves unless they’re going to do it properly. A skim does more harm than no exposure at all, because they’ll misrepresent it.
LMS rollout decisions that quietly sabotage engagement
The mechanics matter more than people admit. A few things I’ve seen wreck otherwise good programs:
- Assigning everything at once. A learner logs in, sees seven mandatory modules due in the next month, and triages. Yours might not win.
- Vague due dates. “Complete by end of Q2” tells people to do it in week 12. Most won’t.
- Auto-generated LMS notification emails. The default templates from most LMS platforms read like ransom notes. Rewrite them. It takes an hour and changes the tone of every reminder for the next two years.
- Launching during peak operational periods. Pushing a 45-minute module to retail staff in the week before EOFY, or to a frontline workforce during a known surge, is asking to be ignored.
None of this is glamorous. None of it shows up in a course design portfolio. But it’s the difference between a program that lands and one that doesn’t, and it’s almost entirely controllable.
Treat the launch as part of the build
The shift I’d argue for is small but meaningful. Stop treating communications and rollout as a separate workstream that happens after the course is done. Build it into the project from scoping. When you’re storyboarding the module, you should also be drafting the launch email, the manager brief, and the LMS notification copy. They’re the same product. The learner experiences them as one thing.
On our side, when we scope custom course development with a client, we now ask early questions about who’s sending the launch comms, what the manager cadence looks like, and how the LMS is configured for reminders. Not because it’s our job to write that material, but because if those pieces aren’t being thought about, the course we’re about to build is walking into a headwind.
Practical takeaways
If you’re planning a rollout in the next quarter, a few things worth pressure-testing before launch day:
- Read your launch email out loud. Does it sound like a human, or like a policy document? If it’s the second one, rewrite it.
- Brief managers separately and a week earlier. Give them words to use.
- Check your LMS notification templates. The defaults are almost always wrong.
- Sequence assignments. Don’t dump everything on a learner in one hit.
- Pick your launch window deliberately. Avoid known peak periods.
If your last program underperformed and the post-mortem landed on “the course needs more interactivity,” I’d gently suggest looking upstream first. The fix might be a better email, not a bigger build. And if you’re scoping a new program now, this is the moment to design the launch alongside the learning. Worth a conversation with whoever’s running your next rollout.
