Training design / L&D build
ADDIE (Instructional Design)
ADDIE is the backbone method for building training that works: Analyze the performance gap, Design the learning solution, Develop the materials, Implement the programme, Evaluate against the original gap.
Its discipline is the front end — most bad training skipped the analysis.
- Problem
- Training design / L&D build
- Altitude
- Program
- Effort to run
- Moderate
- Evidence base
- Established
Theory & origin
ADDIE emerged from instructional-systems design work at Florida State University for the US military in the 1970s and became the default grammar of the L&D profession. The model’s power is its insistence that training is an intervention against a defined performance gap: analysis decides whether training is even the right tool, and evaluation closes the loop against that same gap. Agile critics call it waterfall — modern practice runs the phases iteratively (SAM, rapid prototyping) — but the phase logic survives every iteration fashion because the failure it prevents is timeless: building a beautiful course for a problem training cannot fix.
Explore the model
How a consultant runs it
- 01 Interrogate the request in Analysis: is the gap skill, or is it incentives, tooling, role design? Decline the course if training is the wrong tool.
- 02 Write measurable performance objectives before any content — "after this, learners can X to Y standard" — and get the sponsor to sign them.
- 03 Design assessment first, content second; if you cannot test it, you cannot claim it.
- 04 Prototype one module and pilot it with real learners before developing the full curriculum.
- 05 Evaluate against the original gap (Kirkpatrick levels 3-4), not completion rates, and report the loop back to the sponsor.
When to use
- 01 Building any training programme with real stakes — compliance, onboarding, capability shifts
- 02 Auditing an existing curriculum that consumes budget without moving performance
- 03 Forcing a sponsor conversation about whether the problem is trainable at all
When not to use
- 01 Rapidly changing content where iterative methods (SAM, continuous curation) beat a full cycle
- 02 When analysis shows the gap is incentives or process — no design phase fixes a non-training problem
- 03 Micro-learning or knowledge-base needs where the full ceremony outweighs the asset
Worked example
A logistics firm requests customer-service training after complaint volumes double. Analysis interviews find agents know exactly what to say — but the returns system takes eleven screens and customers boil over during the wait. The consultant returns a two-line training scope (new-hire onboarding only) and a process finding. The returns flow is rebuilt to three screens; complaints halve with two days of training instead of the requested twenty. ADDIE’s first phase saved the client from buying eighteen days of theatre.
Common pitfalls
- 01 Skipping Analysis and building a course for a problem training cannot fix
- 02 Objectives written as topics ("understand X") instead of observable performance
- 03 Evaluating with completion rates and satisfaction scores, then wondering why the budget gets cut
- 04 Running the phases as a rigid waterfall when the content demands iteration
Sample deliverable
One real engagement, end to end — watch the numbers travel from raw input, onto the chart, into the artifact.
Input — raw data
- Analyze — gap interviews30 h
- Design — objectives & tests45 h
- Develop — 6 modules120 h
- Implement — 4 cohorts60 h
- Evaluate — 90-day check25 h
Process — mapped
The performance gap sets the objectives; effort is planned per phase against them
Programme build — onboarding redesign
- Objectiveramp time 6 → 4 months
- Pilotcohort 1, then revise module 3
- Evaluatetime-to-quota at day 90