Framework

Constant evaluation

Once I started the Instructional Design program at George Mason, I was struck by the similarities – the parallel paths – with the principles of project management. Both disciplines require rigorous requirements. What I've learned is the most important aspect is constant evaluation.

I first studied the ADDIE methodology in EDIT 705 and was intrigued by the cycle: Analysis > Design > Development > Implementation > Evaluation. As we studied the concept, I looked at all the different ADDIE diagrams I found on the Internet, and how the labels changed between business processes > software development > shipping and delivery.

I believe one aspect of ADDIE is greater than the others, in part, because it's part of all the others: Evaluation. Yes, evaluation is the natural consequence of implementation, and successful evaluation starts off further analysis. But evaluation is a part of analysis, part of design, part of development and implementation. Evaluation is part of micro- and macro-management in all phases of the methodology.

Constant evaluation within the phases saves an additional cycle for small mistakes.