ADDIE: Does this eLearning Model Need Innovation?
The new idea of making repeated small steps (iterations) meshes well with the ADDIE model. It is better than executing a giant step.
The idea to write a blog on this topic first came to my mind when I came across a book, titled Leaving ADDIE for SAM by Michael Allen. Are we really leaving ADDIE for good? Is ADDIE dead? Or, is it going through a phase of rejuvenation? All these questions hovered in my mind when I first came across a title like this.
On the Internet, you can find online content and eye catching titles such as “Adapting 20th Century Training Models for the Future”. So, what is your opinion on the context? Is it the right time to seek other ideas or eLearning models?
As a reminder, ADDIE stands for Analyze, Design, Develop, Implement, and Evaluate. In today’s time, people may feel that ADDIE is too slow for rapid eLearning development. It might be too archaic for just-in-time course development. ADDIE faces more such attacks when it comes to the long time period associated with this model. It’s sad, but true.
Why do Traditional Models of E-learning Development Fail and Where Do New Models Take the Advantage?
Traditional eLearning models fail as they end up developing disappointing training programs. A lot of valuable time and money is wasted with a little or no impact. This leaves the room for successful models to gain ground. Successful models work within existing constraints. They:
- Investigate alternatives
- Deliver projects on time within budgets
- Use available delivery resources
- Use labor-saving tools
- Keep stakeholders informed
New Lifeline for ADDIE:
The only way to save ADDIE is to make it more agile. It’s not that I am a defender of ADDIE; but you folks have to agree that ADDIE is the backbone of the eLearning processes. We have to consider this from a different angle. The new idea of making repeated small steps (iterations) meshes well the ADDIE model. It is better than executing a giant step. Thus, this agile model ensures better learning and retention and most importantly creates more business impact. This continuous iterative approach enables the developer to move closer to the final product with each milestone.
Thus, the process goes this way. Initially, we need to have all the background information of the given context. After going through the content, we can ask the client any queries if required. What all knowledge and instructional strategy we gather; we prepare a small prototype and send it to the client for his approval. Once the client gives the nod, we proceed to the next part and thus finish the whole task with limited resources and in the existing timeframe without any re-work. Moreover, the stakeholders are well aware as to what is happening at each stage.
Thus, this agile process will come handy once it is being used and improve upon at each level. So, what do you think? Will this agile ADDIE works for you?