Instructional Design Protocol
Caleb J. Clark. April 2006. Original in Front Desk Files>Training Wiki, Video, Audio>Instructional Design Protocol

  • This is a process for making things in the library like projector cart directions, Wiki pages, and printed directions for special projects.
  • We use an acronym “ADDIE.” ADDIE is one of the most famous protocols for making instructional design materials (Tutorials, how-to’s, online classes and training, etc.) ADDIE stands for Analyze, Design, Develop, Implement and Evaluate. I've modified it for the Library’s specific Instructional Design needs.
  • Here are two ways of looking at ADDIE. An abstract graphic way, with a more detailed text explantion below it. Either way, think of making directions or tutorials with text and pictures, and the process you go through to get to a finished product.

  1. Analyze the Situation: For complex projects this means writing down answers in a project description document. For small projects, do this in your head.
    1. What are you trying to teach? Who is the target audience? Who will be using it? What will they already know?
    2. How will the information be best delivered? Via print, web, person to person (no media needed)? A cheat sheet? What is too advanced or belongs in another project? Is it really worth the development time?
    3. How long will it take? When is your deadline? Do you have the budget and resources you need? Who’s in charge and responsible for the project? Then...
  2. Design a Rapid Prototype. Make a rough draft or 'alpha' in the spirit of “lambs to the slaughter.” In other words, you are making a draft specifically to have something the users can be critical of. Give this to one or two people for feedback.
  3. Development Cycle. Make a 'beta' from your alpha version feedback. This is a working rough draft with all major media and content included. Google was in beta for over a year while they saw how people used it and how it worked in the ‘wild’. It will probably be a day or two until enough people have tried it out. Test the draft on a few people and listen to their feedback. Look for criticism, not praise. Fix typos. Improve graphics. Test again. Repeat. When feedback reaches a natural point of saturation and opinion…
  4. Implement Media. Polish up your beta to a “Version 1.0” and call it, “done for now.” Make finished web page, laminate the print-out. Put into use.
  5. Evaluate Regularly. Constant for the life of the media. Monitor usage. Gather feedback if any. Wait. Then make a change with gathered feedback to a “version 1.5” or “2.0." After this, periodically evaluate the content for things that have changed. Is the web page the same? Did we buy a new projector and have to re-shoot images and re-laminate?