9.2 SAM, Agile Development and Prototypes

Agile Alternatives: Allen's Successive Approximation Model (SAM)

Iterative development is useful when the team needs early evidence about learner experience or a design alternative. It can be used within ADDIE as well as in other models. Model names alone do not determine speed, documentation quality or regulatory suitability.

To overcome lot delay and late-stage design failure, Dr. Michael Allen introduced the Successive Approximation Model (SAM). SAM applies agile software development principles to instructional design, prioritizing rapid prototyping, cyclical iteration, and continuous SME collaboration over rigid, sequential handoffs.

SAM2 Extended Architecture:

[ PREPARATION PHASE ]
  Information Gathering ===> [ SAVVY START ] (Collaborative Brainstorming & Rapid Sketching)
                                   |
                                   v
[ ITERATIVE DESIGN PHASE ]
  +---> Prototype Design ===> Review ===> Refine Prototype ---+
  |                                                            |
  +----------------- (Cycle 3 Times) <-------------------------+
                                   |
                         [ Design Proof Frozen ]
                                   |
                                   v
[ ITERATIVE DEVELOPMENT PHASE ]
  +---> Alpha Build ===> Beta Build ===> Gold Release ---------+
  |     (Usability)      (Remediation)   (Final Rollout)       |
  +----------------- (Cycle 3 Times) <-------------------------+

SAM1: The Compact Cyclical Model

SAM1 is engineered for small, single-designer projects or discrete, low-complexity safety topics (such as an annual 20-minute hazard communication update). SAM1 operates across three perpetual, interconnected steps repeated in rapid micro-sprints:

1. Evaluate: Review current worker behaviors, error reports, and baseline capabilities.
2. Design: Immediately brainstorm and sketch a lean instructional intervention.
3. Develop: Build a rough, functional prototype (e.g., a paper mock-up of a chemical labeling guide) and put it into workers' hands immediately for feedback.

SAM2: The Extended Enterprise Framework

For complex, organization-wide safety initiatives—such as commissioning an entirely new robotic manufacturing line or rolling out an enterprise-wide process safety management (PSM) program—SAM2 provides a structured, eight-step process divided across three operational phases:

1. Preparation Phase:

   • Information Gathering: Rapid collection of existing safety procedures, incident logs, and regulatory standards.
   • The Savvy Start: An intensive, multi-disciplinary kickoff sprint. Rather than spending weeks writing an analysis report in isolation, the instructional designer convenes safety engineers, frontline supervisors, maintenance craftspeople, and equipment operators in a single room. The team actively sketches ideas, challenges operational assumptions, and creates multiple competing rough prototypes.

2. Iterative design: Build and review prototypes with relevant stakeholders and learners. Use feedback to refine activities and evidence of learning. The number of iterations is determined by the project; there is no universal requirement for exactly three cycles.

3. Iterative development: Produce increasingly complete versions, validate technical and instructional quality, test representative use, and resolve defects before release. Define what each release must demonstrate instead of assuming that naming it alpha or beta establishes readiness.

---

Rapid Prototyping and Lot Delay Elimination

Rooted in Tripp and Bichelmeyer's design research, Rapid Prototyping integrates the concurrent execution of analysis and design. In conventional ADDIE, a designer might spend two months drafting technical storyboards before discovering during implementation that the chosen simulator interface is unusable for workers wearing heavy chemical gloves. Rapid prototyping circumvents this catastrophic failure by creating early, low-fidelity mockups (paper prototypes, wireframes, tabletop simulation cards) within days of project initiation.

---

ISD Model Comparison: Selecting the Optimal Framework

Selecting the correct ISD framework is not an ideological preference; it is a calculated risk-management decision based on project parameters, regulatory oversight, and organizational velocity.

Agile work without losing validation

An Agile approach uses small increments, frequent inspection and adaptation. In instructional development, an increment might be a working scenario with feedback, a usable performance checklist or an accessible lesson prototype. A prioritized backlog identifies what to develop next; its items should connect to the learner outcome and identified risk. A finished animation that does not support an objective is not necessarily the most valuable next increment.

Define acceptance criteria before reviewing the increment. For a branching case, criteria can include technically valid decisions, useful feedback, accessible navigation and evidence that representative learners understand the prompt. Test those criteria rather than accepting the work solely because stakeholders like its appearance. Record unresolved issues and decide whether they block release.

SAM and Agile do not authorize releasing hazardous misinformation to see whether it works. Technical review, safe pilot conditions and required approvals remain necessary. A smaller reviewable increment can expose an error earlier, but it still needs the right reviewer. Documentation can be maintained alongside each iteration rather than postponed until the final course.

Allen Interactions' SAM process describes preparation, iterative design and iterative development.

Key takeaways

• SAM uses preparation, iterative design and iterative development.
• Agile increments need acceptance criteria linked to outcomes and risk.
• Rapid iteration preserves technical validation and safe release decisions.