Good learning design is invisible — learners don't notice the scaffolding, they just find themselves understanding something they didn't before. Here's what goes into making that happen.
"Training that gets completed is not the same as training that changes behavior. The only metric that matters is whether someone can do something differently on Monday morning."
— The question that drives every design decisionLearners need to understand why before they can absorb how. Every course I build establishes stakes and relevance in the first two minutes — or it loses the learner before the first knowledge check.
Slides are not learning. Wherever possible, I design for doing — branching decisions, scenario-based practice, performance-based assessments that simulate the real task environment rather than testing memory of bullet points.
Completion rates are a vanity metric. I design for Kirkpatrick Levels 3 and 4 wherever the budget and access allow — tracking behavior change and business impact, not just satisfaction surveys.
AI-enhanced workflows, modular design libraries, and rapid prototyping disciplines mean I can move fast when timelines demand it — without producing the generic, template-pasted output that gives fast LXD a bad name.
Tools are a means, not an identity — but fluency matters. Here's what I reach for and why.
Authoring
Multimedia & Design
Systems & Standards
Methodologies
Every engagement is different, but the underlying discipline is the same. Here's how I typically move from kickoff to delivery.
Before a single slide gets built, I need to understand the performance gap. What are people doing now? What should they be doing? Is training actually the right solution — or is this a process, access, or motivation problem? I conduct needs analysis and SME interviews to get to the real root cause.
Learning objectives first, always — written to a measurable, behavioral standard. Then a design document or storyboard that maps content to objectives before any production begins. Stakeholders see and approve the structure before I write a single line of narration or place a single interaction.
Rapid prototyping to get a working draft in front of stakeholders early — not a pixel-perfect final, but enough to validate direction before full production investment. I use modular design patterns and reusable templates to maintain quality while moving fast.
Structured review cycles with clear feedback protocols — not "what do you think?" but "does this meet the learning objective?" Final delivery includes QA against all technical specs, accessibility checks, and LMS testing before launch. Post-launch, I track data and feed insights back into the design.
Whether you need a single course or a full learning system — I'd rather understand the problem first and scope from there.