Saturday, October 27, 2012

Instructional System Design

Reading about Instructional system designs made me think a lot about my early days in education when I began learning how to do basic lesson planning. As a teacher we are always having to go through different design activities related to lesson planning and course design. Instructional system design I see as being able to take on varying sizes of projects. Often in my educational training we go through procedures to design a unit or lesson using some different type of method usually which puts focus on some new skill we have acquired. I see this Instructional system design to be something that can be used for even non educational purposed items which might still have some educational value. Video Gaming is one of the worlds where I could see Instructional System design to be used. Playing a video game there is often objectives the creators of the game have set out to instill on the user playing the game. Often the game starts out by teaching the player how to use the functions of the game to play. Then a mini assessment of sorts will be given to see if that development was successful. The player must implement to new skills learned along the way. I am sure when developers of games design them they would create very similar charts shown here for the ADDIE model. Analysis, Design, Development, Implementation, and constant Evaluation...isn't this what we do as educators on a daily bases? Basically instructional system designs is just another way of systematically think about the things we all already do in the classroom. It provides a way to organize the ideas as teacher we already have in the back of our minds as important. Basically it is an organizational tool which can be used with even modifications in a variety of ways.

1 Comments:

At November 1, 2012 at 4:10 PM, Blogger DiMoore said...

Hi Dawn-
I agree that instructional design can be used in many types of settings. I used to work in pharmaceutical research with a team working on the design of a new drug. We made flow charts with feedback loops and contingency paths for the various stages of the development. There was an overall goal with many objectives along the way. The collective knowledge of the team was documented first as separate documents (in 30 binders in pre-digital days) and then in an overall executive summary. It was carefully planned from the beginning of the project and updated continually as we gained more knowledge about the product we were making. So the pattern was plan, action, feedback, update plan, new or more action, more feedback etc. It was a self-sustaining project where the decisions were either made or recommended by the team. The instructional design part was where knowledge was distributed by members to other members of the team as we worked towards a common goal- the production and regulatory approval of a new drug.
-Diane

 

Post a Comment

<< Home