My approach
Training should make complex work easier to understand, repeat, and improve.
I do not see learning as a one-time event or a polished course sitting in an LMS. I see it as part of how people do their work, make decisions, follow expectations, and build confidence over time.
Overview
I build training around real work.
Good training should help people do something better. That sounds simple, but it is easy to lose when a project starts with a slide deck, a tool, or a request to “make a course.”
My approach is to slow that part down. I want to understand what the training is supposed to change. Is the issue knowledge, confidence, consistency, unclear expectations, weak assessment, poor workflow, or lack of support after training?
Once that is clear, the learning design becomes much stronger. The final product might be a course, but it might also be a job aid, checklist, assessment guide, coaching tool, webinar, onboarding path, or performance support resource.
“The goal is not to make training look impressive. The goal is to make the work easier to understand and easier to do well.”
Principles
What guides my design decisions
I care about clear expectations, practical use, and learning that holds up after the session ends.
Start with the performance problem
I look for the real gap before deciding what to build. Sometimes people need information. Sometimes they need practice, feedback, clearer standards, or better support in the workflow.
Make complex information usable
I am comfortable with policies, standards, procedures, and technical material. My job is to turn that complexity into something people can actually work with.
Design for confidence, not just completion
A completion record does not always mean someone is ready. I build learning with practice, examples, assessment, and support so people leave with a clearer sense of what to do next. Assessment tells me whether the learner can do the work, evaluation tells me whether the training itself is doing its job, and I treat those as two different questions, not one.
Respect the learner’s reality
People are busy, distracted, and often learning because they have to. Training should be clear, relevant, and respectful of the time and pressure people are under.
Support the people delivering the training
Trainers and managers need clear expectations too. Strong training includes guidance, assessment tools, talking points, and ways to keep delivery consistent.
Build for improvement
Training should not be frozen after launch. Feedback, data, learner questions, and workplace changes should all feed back into better learning over time.
Process
How I move from need to solution
I use a structured process, but I keep it practical. The point is to understand the work, build the right support, and make sure the result can actually be used.
Listen
I start by hearing from the people closest to the work, including learners, trainers, managers, and subject matter experts.
Clarify
I define what people need to know, what they need to do, and what good performance should look like.
Design
I choose the format that fits the need, whether that is a course, guide, checklist, scenario, assessment, or blended solution.
Build
I create materials that are clear, organized, visually clean, and easy for learners and trainers to use.
Improve
I use feedback, learner questions, completion data, and performance signals to refine the training after launch.
How I work
I bring structure without making the process heavier than it needs to be.
Some training projects need a formal needs analysis and evaluation plan. Others need a faster, practical fix. I try to match the process to the situation instead of forcing every project into the same mold.
That said, I do believe in being clear about the audience, the goal, the standard, and the evidence that the training worked. Without that, training can look finished without actually solving much.
What I pay attention to
- What people are expected to do after training
- Where mistakes, confusion, or delays tend to happen
- What information is essential and what can be removed
- How the training will be delivered, tracked, and maintained
- What learners and trainers need after the formal session ends
Best fit
Where this approach works well
This approach is especially useful when the work is complex, regulated, sensitive, or hard to explain clearly.
Compliance and regulatory learning
Training tied to policies, standards, procedures, audits, documentation, or institutional expectations.
Healthcare and research environments
Learning that needs to be accurate, practical, sensitive to context, and clear enough for different audiences.
Performance and competency gaps
Situations where people have completed training, but confidence, consistency, or independent performance is still not where it needs to be.
Where this comes from
This approach rests on a specific way of thinking about assessment and evaluation.
Gathering evidence about what a learner can do is a different act than interpreting that evidence to decide whether the training itself is working. I wrote that distinction out directly during my graduate coursework, and it still holds up. It’s the reasoning behind every principle above, not a separate idea sitting off to the side.
What’s on that page
- How I use assessment data as evaluation material
- Why formative results matter even when they’re not graded
- How I judge whether a question actually proves anything
- Why I evaluate past the edge of the course itself
Next step
Want to see how this looks in practice?
My project examples show how I apply this approach to real learning problems, from competency-based training to scenario-based digital learning.