SAM: Successive Approximation Model MicroSim
Edit the SAM MicroSim with the p5.js editor
Copy the following line to include this MicroSim in your website:
1 2 | |
Overview
The Successive Approximation Model (SAM) is an agile, iterative approach to instructional design developed by Michael Allen. Unlike the linear ADDIE model, SAM emphasizes rapid prototyping, frequent iteration, and continuous improvement through stakeholder feedback. This interactive MicroSim demonstrates how SAM works and why it's particularly effective for modern instructional design projects.
Learning Objectives
After using this MicroSim, you will be able to:
- Identify the three phases of the SAM process
- Explain how SAM differs from traditional ADDIE
- Understand the value of iterative design and development
- Recognize how quality improves through successive iterations
- Apply SAM principles to instructional design projects
The Three Phases of SAM
1. Preparation Phase (Blue)
The foundation phase where you gather essential information:
Activities: - Gather information about learners and context - Identify instructional problems and needs - Define project scope and constraints - Brainstorm potential solutions with stakeholders
Duration: Short and focused (typically 1-2 days)
Deliverable: Project brief and initial design ideas
2. Iterative Design Phase (Orange)
Rapid cycles of prototyping and refinement:
Activities: - Create quick prototypes (paper, sketches, mockups) - Review with stakeholders in Savvy Start sessions - Gather immediate feedback - Refine design based on input
Duration: Multiple short cycles (each 1-3 days)
Deliverable: Validated design ready for development
3. Iterative Development Phase (Green)
Building and testing with real learners:
Activities: - Build functional content incrementally - Test with actual learners - Collect performance data and feedback - Implement improvements immediately
Duration: Multiple sprints (each 1-2 weeks)
Deliverable: Continuously improved learning solution
Key Differences from ADDIE
ADDIE Approach
- Linear progression through phases
- Complete each phase before starting next
- Extensive upfront planning and documentation
- Testing happens late in the process
- Changes are expensive after development begins
SAM Approach
- Cyclical, iterative progression
- Rapid prototyping from the start
- Minimal documentation, maximum collaboration
- Testing throughout the entire process
- Changes are expected and welcomed
Interactive Features
Next Iteration Button: Advance through the SAM process one step at a time
Auto-play Mode: Watch the entire process unfold automatically
Iteration Speed Slider: Control how fast iterations progress
Spiral Visualization: See how the process cycles through design and development
Quality Meter: Watch product quality improve with each iteration
Phase Indicators: Track which phase is currently active
Iteration Counter: See progress toward the final product (up to 5 iterations)
Current Activities Panel: View specific tasks happening in each phase
How to Use
Manual Mode (Default)
- Click "Next Iteration" to move through each phase
- Observe the spiral visualization showing your progress
- Watch the quality meter improve with each iteration
- Read the current activities panel to understand what's happening
Auto-play Mode
- Check "Auto-play Iterations" to start automatic progression
- Adjust the "Iteration Speed" slider to control pacing
- Watch as the process cycles through all iterations
- Observe how quality increases with each cycle
Understanding the Visualization
Spiral Path: Represents the iterative journey from start to finish
Position Marker: Shows your current location in the process
Iteration Dots: Visual progress indicator (5 total iterations)
Quality Meter: - Red (0-50%): Initial rough draft - Orange (50-75%): Improving with feedback - Green (75-100%): High-quality final product
MicroSim
Key SAM Principles
1. Early and Frequent Prototyping
Don't wait for perfect designs. Create quick mockups and test them immediately:
- Sketches on paper
- PowerPoint mockups
- Simple interactive prototypes
- Rough content samples
Benefit: Find problems early when they're cheap to fix
2. Collaboration Over Documentation
SAM replaces lengthy documents with collaborative sessions:
- Savvy Start: Intensive kickoff workshop with stakeholders
- Design Proof: Working prototypes instead of written specs
- Alpha/Beta Reviews: Real testing with actual learners
Benefit: Faster alignment and better solutions through conversation
3. Embracing Change
SAM assumes you'll discover issues and opportunities during development:
- Iterate based on feedback
- Refine as you learn
- Improve continuously
- Welcome new insights
Benefit: Final product is better because it evolved based on evidence
4. Continuous Improvement
Each iteration through the cycle improves quality:
- Iteration 1: Rough but functional
- Iteration 2: Clearer based on feedback
- Iteration 3: More polished and effective
- Iteration 4: Fine-tuned and refined
- Iteration 5: High-quality finished product
Benefit: Systematic quality improvement with measurable progress
When to Use SAM
SAM is particularly effective when:
✓ Requirements are unclear - Discover what's needed through prototyping
✓ Stakeholder buy-in is critical - Involve them throughout the process
✓ Speed is important - Deliver faster than traditional approaches
✓ Innovation is valued - Encourage creative solutions through iteration
✓ Learner feedback is available - Test early and often
✓ Agile culture exists - Organization embraces iterative development
When SAM May Not Fit
Consider alternatives when:
✗ Strict regulatory compliance - May require extensive documentation
✗ Fixed requirements - Linear approach might be more efficient
✗ No stakeholder access - Collaboration is difficult
✗ Very small projects - Overhead may not be worth it
✗ One-time delivery - No opportunity for iteration
The Savvy Start Workshop
A key SAM component is the Savvy Start - an intensive collaborative design session:
Participants: - Subject matter experts - Instructional designers - Project stakeholders - Technical team members
Activities: - Brainstorm solutions - Create rough prototypes - Test ideas immediately - Build consensus
Duration: Typically 1-3 days
Outcome: Aligned team with validated design direction
Diminishing Returns
Notice in the MicroSim that quality improvements decrease with each iteration:
- Early iterations: Large quality jumps (15-20% increase)
- Middle iterations: Moderate improvements (10-15% increase)
- Late iterations: Fine-tuning (5-10% increase)
This teaches an important lesson: Know when to stop iterating and ship!
Discussion Questions
-
Compare and Contrast: How would a project differ if developed using ADDIE vs. SAM?
-
Risk Management: Which approach (ADDIE or SAM) better handles uncertainty? Why?
-
Stakeholder Engagement: How does SAM ensure stakeholder buy-in throughout the project?
-
Time to Market: Can SAM really be faster than ADDIE despite multiple iterations? Explain.
-
Quality Assessment: How do you know when you've iterated enough?
Practical Applications
For Small Projects
- Use 2-3 iterations maximum
- Combine preparation with first design iteration
- Focus on core functionality
For Large Projects
- Use 4-5 iterations as shown in MicroSim
- Create multiple prototypes in parallel
- Establish clear iteration criteria
For eLearning
- Prototype interactions early
- Test with small learner groups
- Iterate based on completion rates and feedback
For Instructor-Led Training
- Pilot with one class
- Gather instructor and learner feedback
- Refine materials between sessions
Success Metrics
Track these indicators of SAM effectiveness:
Time Metrics: - Time from start to first prototype - Time from start to first learner testing - Total development time vs. ADDIE
Quality Metrics: - Stakeholder satisfaction scores - Learner performance improvements - Error rates and confusion points
Efficiency Metrics: - Number of major changes required - Rework time after initial delivery - Cost per iteration
Common Pitfalls
❌ Insufficient Stakeholder Involvement - Solution: Schedule regular review sessions
❌ Analysis Paralysis - Solution: Set time limits for each iteration
❌ Over-Iteration - Solution: Define "good enough" criteria upfront
❌ Skipping Learner Testing - Solution: Make testing mandatory in each cycle
❌ Poor Prototyping Tools - Solution: Use rapid prototyping software
Reflection
Consider your own experiences:
- Have you ever created something, gotten feedback, and wished you'd tested earlier?
- When has iteration improved one of your projects?
- What would help you embrace an iterative approach?
- How might SAM change your workflow?
Try This Challenge
Using the MicroSim:
- Run through all 5 iterations and note the quality at each stage
- Imagine specific feedback that might occur at each iteration
- Consider what would happen if you stopped at iteration 3
- Think about how ADDIE would handle the same project differently
Related Concepts
- ADDIE Model - Traditional instructional design approach
- Agile Development (SAM Process) - Software development methodology inspiring SAM
- Rapid Prototyping - Quick mockup creation
- Formative Evaluation - Testing during development
References
- Allen, M. W., & Sites, R. (2012). Leaving ADDIE for SAM: An Agile Model for Developing the Best Learning Experiences. ASTD Press.
- Allen, M. W. (2016). Designing Successful e-Learning: Forget What You Know About Instructional Design and Do Something Interesting. Pfeiffer.
- Hnatiuk, J. (2021). SAM for Instructional Designers. ATD Press.
Case Study: Real SAM Project
Project: Employee onboarding program for 500-person company
ADDIE Approach Would Have Been: - 2 months analysis and design - 3 months development - 1 month implementation - Total: 6 months
SAM Approach Was: - 2 days Savvy Start workshop - 3 two-week design/development iterations - Deployed partial solution after iteration 2 - Total: 7 weeks to full deployment
Results: - 5 months faster - Higher satisfaction (stakeholders involved throughout) - Better quality (tested with real employees early) - Lower cost (found issues before extensive development)
Credits
This MicroSim was created to support the Intelligent Textbooks project and demonstrate the SAM instructional design process interactively. The visualization shows how agile approaches can accelerate and improve instructional design.