Iteration
The process of repeatedly reviewing, testing, adjusting, and refining a learning solution as new information, feedback, evidence, or needs emerge.
Iteration
Build, learn, and make each version stronger.
Iteration is the process of developing something, learning from it, making informed changes, and repeating the cycle when useful. It allows a learning solution to become stronger as the team learns more about the content, audience, experience, and results.
Iteration can happen during planning, design, development, review, testing, implementation, or after launch. Each cycle creates another opportunity to learn and refine the solution.
The Cycle
Create, learn, adjust, and try again.
An iteration can be a small, focused cycle. Create enough to learn something useful, gather information about how it is working, and use that insight to shape the next version.
Throughout the Project
Use iteration throughout the project.
Early iteration gives the team opportunities to test assumptions, explore ideas, and refine decisions while the solution is still taking shape. Later iterations can strengthen the experience as more evidence becomes available.
Use What You Learn
Let evidence guide the next version.
Useful iteration connects feedback and evidence to the original need, audience, goals, constraints, and design decisions. This helps the team focus its effort where changes can make a meaningful difference.
- Look for patterns across learner, SME, stakeholder, and project-team feedback.
- Address factual corrections and content changes that affect accuracy or understanding.
- Pay attention to places where learners consistently struggle with instructions, content, navigation, practice, or expectations.
- Revisit the intended performance or learning outcome when deciding which changes add the most value.
- Include accessibility, usability, technical performance, and real-world use when reviewing the experience.
What did we learn, and how can that insight make the solution more useful or effective?
Move Forward
Know when the solution is ready to move forward.
Iteration works best when each cycle has a clear purpose. Timelines, budgets, requirements, priorities, and evidence all help determine when a version is ready for its next step.
- Define what each review or test is intended to help the team learn.
- Prioritize improvements that strengthen accuracy, accessibility, usability, learning, or performance.
- Focus project time on changes that meaningfully improve the learner or performance experience.
- Capture useful ideas that can be considered for a future version or later phase.
- Move forward when the solution is ready to support its intended purpose and audience.