What is instructional design?

At its core, instructional design is the practice of applying learning science and pedagogy to real-world content so training is clear, engaging, and actually changes performance—not just “covers material.”

Why is it needed? People often assume that if you know a subject, you automatically know how to teach it. That’s rarely true. Experts tend to either (a) include everything they know, or (b) assume learners know far more than they do. Both paths lead to overloaded, confusing training and poor results. Instructional design prevents that by defining what learners must do, then building only what supports that goal.

One of the most widely used structures for instructional design is ADDIE, a five-phase model. I use it as a practical roadmap and, because collaboration is central to how I work, each phase is done with leaders, trainers, and SMEs—not in isolation.

ADDIE (and how I approach it)

1. Analysis: I start with curiosity, not assumptions.

• Meet with leaders to clarify the business goal, constraints, timeline, and what success should look like
• Talk with SMEs and front-line performers to understand the real tasks, common errors, and “what good looks like” on the job
• Define the audience: their background, current skill level, environment, and how much time they truly have for learning
• Translate all that into a clear performance gap and a short list of must-have outcomes

Deliverable: a brief needs/performance summary and draft objectives aligned to organizational goals.

2. Design: This is where we build the blueprint together.

• Draft measurable learning objectives and a high-level outline, then review with the team for buy-in
• Choose the best modality (CBT, ILT/VILT, blended, job aids) based on the task, risk level, and learner context
• Plan practice that mirrors reality: scenarios, decision points, demonstrations, and feedback
• Use quick mockups (slides, flow diagrams, sample interactions) to confirm alignment before full build

Deliverable: design plan + storyboard/outline that the team has already validated.

3. Development: Here the plan becomes the product—with frequent check-ins.

• Build the course/module/materials using the agreed tools and standards
• Share prototypes early and invite critique while changes are still easy
• Incorporate feedback in clear cycles so SMEs and stakeholders see how their input shaped the result
• Create supporting materials (facilitator notes, rubrics, job aids, templates) so delivery is smooth and consistent

Deliverable: the finished learning assets, ready to launch, plus trainer/learner support materials.

4. Implementation: Launch isn’t a handoff. It’s a partnership.

• Coordinate rollout with trainers/leads so expectations, timing, and logistics are clear
• Ensure learners know where to access training and how it fits their workflow
• Support instructors or supervisors with quick run-throughs, FAQs, or coaching notes
• If there’s a platform involved, verify the experience works as intended end-to-end

Deliverable: a clean rollout and people who feel prepared to use and support the training.

5. Evaluation: Where training proves its worth and improves.

• Gather learner feedback (Level 1) and knowledge/skill evidence (Level 2)
• When possible, look for behavior or performance shifts on the job (Levels 3/4)
• Review results with stakeholders to decide what to refine, reinforce, or scale
• Treat evaluation as a loop back into the next design cycle

Deliverable: a short results summary and practical recommendations for improvement.

In short, ADDIE gives structure, but collaboration gives it power. My goal in every project is to work shoulder-to-shoulder with SMEs and training partners to create learning that’s accurate, realistic, and genuinely useful in the field.