SAM is an agile, iterative instructional design process that works in rapid cycles: build something rough, get feedback, improve it, repeat until it’s ready to ship.
Why it matters#
When you’re under time pressure or requirements aren’t fully defined, ADDIE’s sequential structure can slow you down or leave you stuck. SAM lets you start producing and testing early — problems surface before they become expensive, and stakeholders stay engaged because they see tangible progress from day one.
The three phases#
- 1. Preparation Gather background information about the learners, the content, and project constraints. This phase ends with a Savvy Start — a short, focused session where the designer, subject matter experts, and key stakeholders come together to share knowledge and produce rough first prototypes (sketches, storyboards, or slide mockups). The goal isn’t polish; it’s to make ideas concrete enough to react to.
- 2. Iterative Design Cycle through: prototype → review → refine → repeat. Each round gets closer to the right solution. Prototypes can still be rough — the point is to make decisions fast, test them, and discard what doesn’t work before investing in development.
- 3. Iterative Development
Build increasingly complete and functional versions of the course, evaluated and improved at each stage: Design Proof → Alpha → Beta → Gold → Rollout
- Design Proof — confirms the visual and interaction approach works
- Alpha — first fully functional version; rough edges expected
- Beta — refined version ready for broader testing
- Gold — approved final version ready for release
Key facts#
- SAM1 and SAM2 differ in one key way: whether design and development happen together or separately. SAM1 keeps them integrated — the same person or small team sketches, builds, tests, and refines in a single loop. SAM2 separates them into distinct phases, for when development is handled by a different team, content volume is large, or formal approval gates are required.
- It produces less documentation than ADDIE. This is a feature when speed matters, but a problem in regulated or institutional contexts that require formal records.
- It only works if stakeholders give fast feedback. The iterative loop depends on timely responses. If collaborators are slow or expect a finished product before engaging, SAM breaks down.
- It’s better for new projects than for maintaining existing ones. The flexibility of SAM is most valuable when requirements may shift. For stable, well-understood content, ADDIE may be more efficient.
When to use it#
- Tight deadline or limited budget
- Requirements are unclear or likely to shift
- Design and development can be handled by the same person or small team → SAM1
- Development will be handed off to a separate team or contractor → SAM2