The ADDIE Model Explained
Turn this article into takeaways for your work.
Each assistant summarizes the article only for you and suggests best practices for your work.
ADDIE is a five-phase process for building training: Analysis, Design, Development, Implementation and Evaluation. It's the default vocabulary of instructional design. Ask almost any course producer how a project runs and the answer will map onto those five words, even if the team never calls it ADDIE.
If you build or sell learning products to companies, the model matters for a practical reason. It shapes how projects get scoped, how long they take, where the money goes and where a buyer's own team ends and a vendor's begins. This article explains the five phases, what's known about the model's origin, how it moved from a strict sequence to a looser loop, what its critics say, and what it means for a company producing courses. For the wider discipline, start with instructional design basics.
Key Facts
- ADDIE stands for Analysis, Design, Development, Implementation and Evaluation. Its direct ancestor is the Interservice Procedures for Instructional Systems Development (IPISD), a five-volume US military training system dated 1 August 1975 and written by Robert Branson and colleagues at Florida State University's Center for Educational Technology (Branson et al., 1975, DTIC).
- The IPISD was prepared under a contract with the US Army Combat Arms Training Board. When the Interservice Committee for Instructional Systems Development became its approving authority, the scope widened to include Air Force, Marine and Navy requirements as well as the Army's (DTIC).
- The IPISD itself didn't use the ADDIE label. Its five phases were analyze, design, develop, implement and control (DTIC). Michael Molenda, who went looking for the source of the ADDIE name in 2003, concluded that it came into use by word of mouth as a label for the whole family of systematic instructional development models (ERIC, Molenda 2003).
- The IPISD already had a feedback step built in. Its fifth phase, control, collects and evaluates data on the instruction so that revision decisions can be made, and a negative answer on whether trainees learned what was intended calls for revisions to the content or procedures (DTIC).
- Allen Interactions' SAM (Successive Approximation Model) has three phases: Preparation, Iterative Design and Iterative Development. It describes itself as minimizing time-consuming upfront analysis, in contrast to ADDIE (Allen Interactions).
The five phases
ADDIE is a checklist of questions in a sensible order. Each phase produces something the next one needs.
| Phase | The question it answers | Typical outputs |
|---|---|---|
| Analysis | Who is the learner, what's the performance problem, and is training the answer? | Needs analysis, learner profile, constraints, success measures |
| Design | How will the learning work? | Learning objectives, assessment plan, course outline, storyboards or scripts, style guide |
| Development | What does the actual material look like? | Authored modules, videos, activities, facilitator guides, quizzes |
| Implementation | How does it reach learners and trainers? | Platform setup, pilot, trainer preparation, launch |
| Evaluation | Did it work, and what should change? | Learner feedback, assessment results, performance data, revision list |
Analysis
Analysis defines the problem before anyone opens an authoring tool. A good analysis looks at the business goal, the audience and the gap between current and required performance. It also checks whether the gap needs a course at all, or whether a clearer process, a better tool or a manager conversation would close it. That's the same logic described in training needs analysis, which is effectively a deep dive into this one phase.
Design
Design turns the analysis into a plan. Teams write measurable objectives, decide how learners will show they've learned, choose the delivery format and sequence the content. The deliverable is usually a blueprint: an outline, sample screens or scripts, and an assessment approach. Design decisions are cheap to change on paper and expensive to change after video is shot, which is why many projects add a formal sign-off at this point.
Development
Development is production. Writers write, designers build, narrators record, developers configure interactions. This is the most visible phase and usually the most expensive, because it consumes the most labor. It's also the phase most often outsourced, a point we'll return to below.
Implementation
Implementation puts the course in front of learners. That can mean uploading a package to a learning management system, training facilitators for a live program, or running a pilot with a small group first. Delivery format changes the work here a lot. A live cohort has a schedule and instructors to prepare, while a self-paced course mainly needs hosting and reporting. For more on that trade-off, see cohort-based vs self-paced learning.
Evaluation
Evaluation checks results against the objectives set in Design and the problem named in Analysis. It can happen during the project, through reviews and pilots, and after launch, through learner feedback and performance data. In practice it's the phase most often cut when budgets tighten, and the one buyers later ask about when they need to justify renewal. How customers try to prove value is covered in proving training ROI.
Where ADDIE came from
The origin story gets repeated with more confidence than the record supports, so it's worth separating what's solid from what isn't.
What's solid: in the 1970s, Florida State University's Center for Educational Technology worked under contract to the US Army Combat Arms Training Board to build a systematic way to develop training. The result was the Interservice Procedures for Instructional Systems Development, a five-volume set dated 1 August 1975. It was approved by an interservice committee, which broadened it to cover Air Force, Marine and Navy needs as well as the Army's (DTIC).
What's less solid: the name. The IPISD's five phases were analyze, design, develop, implement and control (DTIC). The last one isn't "evaluation", and the document doesn't use the ADDIE acronym. Molenda searched the literature and interviewed practitioners whose experience went back to the 1960s, and concluded that the term spread by word of mouth as a label for the whole family of systematic instructional development models (ERIC, Molenda 2003). Treat claims that a specific person coined ADDIE in a specific year with suspicion unless they cite a primary document.
That distinction matters for how you describe the model to buyers. "A process descended from a 1970s US military training system" is defensible. "Invented by the Army in 1975 as ADDIE" overstates what anyone can show.
From straight line to loop
The original IPISD is laid out as five phases in order: analyze, design, develop, implement, control (DTIC). That gave the model its waterfall shape: finish one phase, sign it off, move on.
It was never a pure straight line, though. The final phase exists to feed data back. The IPISD describes collecting data, evaluating it and deciding what it implies for the course, and it says that a negative answer on whether trainees are learning what was intended, or whether that learning is of the expected benefit, should lead to revisions (DTIC).
So the strict waterfall reading of ADDIE is partly a caricature. Modern guides usually draw it as a cycle, with evaluation findings feeding back into analysis, and with small loops inside each phase. Whether a given team actually works that way is a different matter, and that gap is where most of the criticism comes from.
The criticisms
It looks like waterfall. Even in loop form, ADDIE is usually taught as phases with handoffs. Allen Interactions contrasts SAM with what it calls ADDIE's sequential waterfall phases (Allen Interactions). The practical problem is feedback timing. If stakeholders only see something real during Development, the first honest reaction to a misunderstood requirement arrives after most of the money is spent.
Heavy upfront analysis. Allen's materials argue for minimizing time-consuming upfront analysis and doing most of it while considering alternative solutions (Allen Interactions). The counterpoint is that skipping analysis is how companies end up building a polished course for a problem training can't solve.
It's a process, not a theory of learning. ADDIE says what to do in what order. It doesn't tell you whether a given activity will teach anyone anything. Teams can follow all five phases perfectly and still produce dull, ineffective content, because the model has no opinion on pedagogy. That judgment comes from instructional design practice, covered in instructional design basics.
It's an informal label. Since the name isn't tied to one authoritative document, "we use ADDIE" can mean anything from a rigorous military-style process to a vague habit of "plan, build, ship, check". When a buyer or vendor says it, ask what artifacts they actually produce at each phase.
Alternatives: SAM and rapid prototyping
The usual alternatives keep the same basic activities but change the order and the size of the steps.
SAM (Successive Approximation Model). Developed by Michael Allen and described by Allen Interactions as having three phases: Preparation, Iterative Design and Iterative Development. Preparation gathers background information before any solution is attempted. Iterative Design uses a repeated "design, prototype, evaluate" cycle. Iterative Development produces a Design Proof, then Alpha, Beta and Gold releases (Allen Interactions). The idea is that people react better to a rough working version than to a document describing it.
Rapid prototyping. The older cousin. Teams build a quick, low-fidelity version, test it with real learners and refine. It's another common alternative to ADDIE. The honest framing is this: SAM and prototyping mostly rearrange ADDIE's work, they don't replace it. Analysis, design, development, delivery and evaluation still happen. They just happen in smaller, earlier loops.
A rough rule of thumb for choosing:
| Situation | Better fit |
|---|---|
| Regulated or compliance content with fixed requirements and formal sign-off | ADDIE, with documented approvals at each phase |
| Large, high-stakes program with many stakeholders and a long shelf life | ADDIE, with prototypes added inside Design |
| New concept where nobody can describe the "right" course in advance | SAM or rapid prototyping |
| Tight deadline, flexible scope, a stakeholder who "will know it when they see it" | SAM or rapid prototyping |
Many teams blend the two: a front-end analysis in the ADDIE style, then iterative design and build cycles in the SAM style.
What ADDIE means for a company producing courses
For an EdTech or corporate-learning company, ADDIE is less a methodology debate and more a project-management skeleton. Four practical consequences follow.
Scoping. The five phases give you a natural way to break a quote into pieces. A project estimate that lists Analysis, Design, Development, Implementation and Evaluation separately is easier for a buyer to read and to challenge than a single lump sum. It also exposes the choice most buyers are making without knowing it: how much of the front and back end they want to pay for.
Timelines. Phases create dependencies. Design can't finish until Analysis is agreed, and Development can't start safely until Design is signed off. Delays usually come from reviews and approvals rather than from production, so a realistic schedule builds in stakeholder review time at each handoff. The more a project looks like a straight line, the more a late change in one phase cascades into the next. Iterative approaches shorten the feedback loop but need stakeholders who will actually review rough work.
Where custom-content vendors fit. Most outside vendors sell into the Development phase, sometimes with Design attached. The buyer's L&D team usually owns Analysis, because it requires knowing the business, and often owns Implementation, because it involves their own platform and employees. Evaluation tends to be shared. That split explains why vendors who also offer help with needs analysis or measurement can stand out, and why a vendor who only quotes production often competes on price. It also shapes how companies buy: custom work is typically a project purchase, while licensed content is closer to a subscription or catalog decision (how companies buy training, training content licensing).
Business model. ADDIE-shaped work is labor-heavy, which is why custom course development is usually priced by project or by phase. Products built from the output, such as reusable courses sold many times, change the economics. The trade-offs are laid out in corporate training business models. If a team runs custom builds and wants to move toward a product, the Design and Development outputs are the raw material, and clean documentation from earlier projects makes that move easier.
Practical tips
- Ask what each phase will produce, in writing, before agreeing a scope.
- Put the first real review of working material as early as possible, even if the process is nominally ADDIE.
- Define evaluation measures during Design, not after launch.
- Separate analysis fees from build fees. Buyers can then see that a "no training needed" finding is still valuable work.
- Keep the revision list from Evaluation. It's the start of your next project and your renewal conversation.
Frequently Asked Questions about the ADDIE Model
What does ADDIE stand for?
Analysis, Design, Development, Implementation and Evaluation. They're the five phases of a systematic approach to building training, from understanding the problem to checking whether the training worked.
Who created the ADDIE model?
Its direct ancestor is the 1975 Interservice Procedures for Instructional Systems Development, written by Florida State University's Center for Educational Technology under a US Army contract. That document used the phases analyze, design, develop, implement and control, so the ADDIE name itself has no clearly documented author.
Is ADDIE linear or iterative?
Early descriptions were largely sequential, though the final phase fed revision data back into the course. Modern versions are usually drawn as a cycle. How iterative it is in practice depends on the team.
Why do people call ADDIE a waterfall model?
Because it's often taught as phases that finish and hand off to the next, which delays real feedback until late in the project. Defenders say that reading is a simplification, since the model has always included a feedback step and modern versions allow overlapping work and loops.
What is the difference between ADDIE and SAM?
SAM, developed by Michael Allen, replaces long upfront analysis with a short Preparation phase and then repeats design, prototype and evaluate cycles before building releases. ADDIE is more phase-based. Both include the same underlying activities, but SAM gets working prototypes in front of stakeholders sooner.
Which should a course-production company use?
Many use a blend. A short analysis and a signed-off design suit fixed-requirement and compliance projects, while prototype-and-review cycles suit projects where the right answer isn't obvious yet. Whatever you call it, define what each phase delivers and when stakeholders will review real material.
Where does a custom-content vendor fit in ADDIE?
Most vendors concentrate on Development, often with some Design. Buyers' internal L&D teams usually own Analysis and much of Implementation, and Evaluation is often shared. Vendors that help with analysis or measurement can differentiate beyond production price.
Related reading
