Updated 16 November 2026 Updated with recent project examples and practical guidance on reviewing existing training materials.
“It’s only a small update.”
A perfectly reasonable sentence, and one that can cover quite a range of possibilities. A changed logo and a new contact name? Great. A different process, a new audience and several decisions nobody is entirely sure who actually made. Slightly more involved.
When you already have slides, a course or a folder full of information, it’s tempting to get straight into building. The content exists. Surely we can just tidy it up and get it out there?
This is where I tend to start asking questions.
What needs to change as a result of this training? Who will use it? What are they finding difficult now? And does the existing content still reflect what actually happens?
I often describe effective e-learning as 90% preparation and 10% production. That’s an expression, rather than a measured split of project hours. Building takes time and skill. But the thinking beforehand shapes what we build, why we build it and whether it will be useful.
It’s remarkably easy to build the wrong thing efficiently. Particularly given all of the AI-driven tools out there that can in theory, build you a course in minutes.
In Short.
Before creating or updating training, establish what needs to change, who needs support and what is getting in their way. Check whether training can address the problem, agree what success would look like and test a small part before building everything. The preparation should be proportionate to the project, but even a small update benefits from checking the assumptions behind it.
1. Start with what needs to happen differently
Recently, I worked on a course update prompted by changes in legislation. It was expected to be a fairly quick job. The client had reviewed the changes and sent over what needed updating.
At first glance, that could have meant adding some new wording and amending a few existing sections. But there was another question to work through: what would someone taking the course need to do with this information?
“They need to know this now” became “They need to know this, recognise when it applies and understand what to do in that situation.”
That meant reviewing the relevant training as a whole. Where did the change affect an explanation, an example or a decision someone would need to make? Did the course explain why it mattered, when it applied and how to put it into practice?
The work grew from a few hours to a few days, with some additional review time for the client. That was more than a wording change, but it meant the update was reflected throughout the learning, including the places where people were being asked to apply their knowledge.
It also gave the client a useful reason to draw attention to the courses again. There was something specific to communicate: what had changed and why the updated learning mattered to the people using it.
This is why I start with what people need to do differently. Even when the request is “just update the content”, it’s worth following that change through to the job someone needs to do.
2. Check whether training will help
If someone isn’t completing a task correctly, it’s worth finding out why before creating a training course about it.
On another project, the request was for training for helpdesk agents. Too many support calls were being passed to third-line support, and clients were unhappy that their issues weren’t being resolved at the first point of contact.
Training was part of the answer. But looking at how the agents handled calls showed that the system they were using needed attention too.
Additional fields, drop-downs and conditional formatting could help them capture the right information and spot what needed attention. A script could support their questioning, helping them work through the problem while the caller was still with them.
These were practical changes that the business could largely make in-house. My contribution was one part of a wider solution.
Another recorded Teams session could explain what agents should do. It couldn’t, on its own, make the information easier to capture or put the right prompts in front of them during a call. Improving that everyday support addressed more of the problem than training alone could.
Before deciding someone needs more training, it’s worth looking at what they’re working with. Do they lack knowledge or practice? Or does the process make it difficult to do the job well, even when they know what’s expected?
Sometimes people need both learning and a better way to apply it.
3. Find out who will use it and under what conditions
“Staff” is rarely a detailed enough description of the people we’re designing for.
Someone doing a task for the first time needs different support from someone who has done it for years and needs to learn one change. A person using a shared device between appointments has a different experience from someone with protected learning time at a desk.
Find out:
- What people already know and can do.
- Where and how they will access the learning.
- How much time they can realistically give it.
- What language, accessibility or confidence needs should inform the design.
- Where they will go for help afterwards.
Where possible, involve the people doing the work. They can explain the awkward steps, unofficial workarounds and questions that don’t appear in the process document.
Those details are useful design information. They help us create something that fits the working day people actually have.
4. Look at what the existing materials need to become
Existing materials give you a starting point, but they still need reviewing.
On a recent project, we started with a slide deck that supported a speaker. Quite rightly, the slides weren’t packed with explanations. The speaker supplied those.
But we needed enough supporting information for another facilitator to deliver the session. The slides alone couldn’t tell them how to explain a point, introduce an activity or respond to a question.
When writing a facilitator guide, I start by assuming the facilitator knows nothing about the particular session. That prompts me to include the purpose, explanations, examples, activity instructions and likely discussion points, rather than relying on someone filling in the gaps.
An experienced facilitator can draw on what they need. Someone coming to the session for the first time has a much clearer starting point.
Existing materials aren’t always up to date, either. I’ve worked on projects where we’ve converted what was available into a new format and then used that version to review and update the content.
That can be a more practical route than waiting for someone to rewrite everything before handing it over. Updating an old deck alongside the day job isn’t necessarily something anyone is excited to begin. A fresh structure can make the review feel more manageable and help people see familiar material differently. Anything still needing an accuracy check or a decision stays clearly marked until it’s resolved.
I bring that fresh perspective too. As a professional ‘novice’ in the subject, I notice where I’m struggling to follow an explanation or understand how to apply it. Those moments give me useful questions to take back to the expert.
Would a template help me do this? Is there a missing step? Could a worked example explain something more clearly than several PowerPoint slides?
Having completed so many different topics and subjects in theory I should be an expert on all sorts of things. If I’m honest, once the project is done, my head gets emptied out and I start again! It’s a skill I’ve honed over the years and actually helps me do my job a whole lot better.
The useful starting point is to look at what you have, what it needs to become and how the team can get it there with the least unnecessary work.
5. Agree what good looks like
Finishing a course tells us that someone reached the end. We still need to consider whether they can do what the learning was intended to support.
For a booking process, that might mean completing a realistic example correctly. For a difficult conversation, it might involve practising a response and receiving feedback. For a procedural update, it could mean recognising when the new rule applies.
Agree an appropriate way to check this before building. Otherwise, assessment can become a few questions added at the end because the course needs a quiz.
Think about the workplace afterwards too. Who will support people as they apply the learning? What would suggest that it’s helping, and when would it be useful to review that?
You don’t need an elaborate evaluation project for every small piece of learning. You do need a clearer ambition than “everyone has clicked through it” though.
6. Test something small before building everything
Preparation doesn’t mean trying to predict every detail and then refusing to change the plan.
A short prototype, sample activity or outline gives people something tangible to respond to. It can reveal a misunderstanding while it is still relatively straightforward to fix.
For example, you might test one scenario with a few intended learners. Does the situation feel recognisable? Are the choices realistic? Is the explanation useful? Can they access and use it comfortably?
End users are the best and most important part of a successful project. They can be brutal reviewers and given the opportunity for an honest assessment, bring wonderful qualitative feedback to hone a project. You might not like what they have to say, but the reality is it will always save you something. Money, hours, time, effort, marketing budget….Get them on board early, let them tell you what they need, deliver it, and they will market it for you.
Agree who reviews what as well. The subject expert may check accuracy, while learners help test whether the activity makes sense in practice. Someone also needs responsibility for resolving conflicting feedback.
Finding out early that “this isn’t quite what we meant” is useful. Finding out after every screen has been built is considerably less enjoyable.
A short brief before you begin
For a small project, a page of clear decisions may be enough. Capture:
- The purpose: what needs to improve.
- The people: who needs support and in what circumstances.
- The task: what they should be able to do.
- The barriers: what is making that difficult.
- The approach: what learning or other support is needed.
- The checks: how you will test accuracy, usability and usefulness.
- The responsibilities: who provides information, reviews and approves the work.
Record anything that is still uncertain and who will resolve it. An unanswered question is easier to manage when it’s visible.
The brief should help people make decisions as the work progresses. If it becomes a document everyone carefully files and never opens again, it probably needs simplifying.
A PRACTICAL CHECK
Could you explain why this training is needed?
Choose a course you’re planning, updating or asking people to complete.
Try finishing this sentence:
“After this, people should be able to __________, which will help us __________.”
Then ask what is currently stopping them.
If the answer is missing knowledge or practice, learning may help. If it’s an unclear process, missing access or conflicting expectations, those need attention too.
That short conversation can change what you decide to build.
Need help working out what to build?
If you have a folder of content and a feeling that it needs to become training, Jessanol can help work through the questions before production begins.
We can clarify the task, understand who needs support, review what already exists and agree an approach that fits the work.
That might lead to e-learning, a workshop, a practical guide or something much smaller than you originally expected.
You don’t need to have the answer before we talk. Working it out is part of the job.
Get in touch if you’d like help deciding where to start.
I enjoy making things. I’d just like us to be making the right thing.



