ADDIE is a five-phase framework for designing and developing training: Analysis → Design → Development → Implementation → Evaluation.
Why it matters#
Without a structured process it’s easy to jump straight into content creation before clarifying who the learners are, what they need, or how you’ll know the course worked. ADDIE forces those questions first. It also gives you a shared language when working with SMEs, clients, and stakeholders — making the design process visible and defensible.
The five phases#
| Phase | Core question | Output |
|---|---|---|
| Analysis | Who are the learners? What gaps need filling? | Learner profile, goals, constraints |
| Design | How will learning be structured and assessed? | Blueprint: objectives, sequence, assessments |
| Development | Build the actual content | Course materials, media, activities |
| Implementation | Deliver the course | Live or published course; trained facilitators |
| Evaluation | Did it work? What needs to change? | Survey results, outcome data, revision plan |
Key facts#
- The process is cyclical, not linear. Evaluation feeds back into Analysis, starting a new cycle. More cycles mean a better course — ADDIE is designed to improve iteratively over time.
- Evaluation has two forms. Formative evaluation happens throughout every phase to catch problems early when they’re cheaper to fix. Summative evaluation happens at the end to measure whether learners achieved the learning objectives.
- Development takes the most time. Budget accordingly — teams often underestimate this phase and over-invest in Analysis.
- It can be slow. Its sequential nature means significant time is spent in Analysis and Design before any content exists. If requirements are unclear or deadlines are tight, consider SAM instead.
When to use it#
- You have a well-defined audience and stable requirements
- The project is large enough to benefit from structured phases
- You need a documented, repeatable process — for a team, a client, or an institutional context