# data[].attributes.body
The ASSURE model is probably the most viable option for me. My district expects our lessons to complete pre/post tests for each unit of instruction (analyze/evaluate) and connect each lesson to not only state standards, but district aligned learning targets. We are a one to one district utilizing Chromebooks, so media can easily be utilized in many different formats. This year there is a huge push for innovation and student engagement in my district. This model has a place for all of these things and I feel it can easily be used for design and implementation.

# data[].attributes.body
Analyze
Design
Develop
Implement
Evaluate

(Arshavskiy, 2017)

# data[].attributes.body
Analyze Learners
State Objectives
Select Media and Materials
Utilize Media and Materials
Require Learner Participation
Evaluate and Revise

(Arshavskiy, 2017)

# data[].attributes.body
Prepare
Present
Practice
Perform

(Arshavskiy, 2017)

# data[].attributes.body
Arshavskiy, M. (2017). Instructional design for elearning: Essential guide for designing successful elearning courses. Your eLearning World.

# data[].attributes.body
Each of the selected models stand for extremely similar things. The ASSURE and ADDIE have the analyze portion which is similar to the prepare portion of the ISD model. In this portion you are looking at the learners the lesson will be presented to and their prior knowledge of the topic.

# data[].attributes.body
While working through the steps of each, the titles may be different but what is happening is the same. The select of the ASSURE model, the design and develop of the ADDIE, and the prepare of the ISD are the locations where the lesson is being created before being presented and taught.

# data[].attributes.body
Next up is presenting the lesson to the learners in the classroom. Again, each is stated a bit differently utilize/require, implement, and present, but this is where the actual teaching of the lesson is happening.

# data[].attributes.body
Finally, student learning is evaluated with the evaluate/evaluate/practice & perform portions. Here we find out if the lesson was successful and what each student gained.

# data[].attributes.body
The main thing sticking out as a difference is the ASSURE model having an entire section dedicated to labeling the state objectives. Though this isn't mentioned in the other models, it doesn't mean it should be skipped. It is just a portion not explicitly stated.

# data[].attributes.body
The ASSURE model also provides a portion for revision at the end of the teaching and evaluating. This portion is important because if the lesson doesn't go how you expected, changes can be made and revisited to make sure understanding and learning happens.

# data[].attributes.body
I also see the ISD model as a shortened version of the ADDIE and ASSURE models. Depending on the person creating the lesson it can either be short and simple, or longer and more detailed within each portion of the design.

# data[].attributes.body
This model is also a viable option for me, however due to being less detailed than the ASSURE model, I think I may find myself looking for a place to add missing the missing pieces of the design. This model still hits many of the expectations of my district, so I think it could still be a great choice.

# data[].attributes.body
The Rapid ISD model is viable for times when I may need to design a lesson quickly. Without the detailed requirements, it could help create quick, yet still engaging ways to present lessons.