Design documents? Ha!!

ADDIE stands for

Additional Deadlines Demand Improvisation Everywhere

Paul

I hear what you're saying - and depending on the project and the client, the level of analysis I use varies. However, I still think that there are some basics that have to be there for the learning to transfer back to the job, and then hopefully support the organization's goals for the course. (impact on the org).

Anyway, I think that we need to do some level of needs assessment to figure out 1. why we're doing the training, and 2. try to target something to measure later to see if the training worked. Then, I like to do a task analysis or content analysis with SMEs and/or source material. THen... Based on this, come up with learning objectives and a good content outline. Usually I have to handcuff a SME to the table and hold their head while they agree to everything, but it saves alot of headaches in the end.

Then, based on the learning objectives and outline, I try to think of creative ways to present the info and involve the learner (strategies), come up with some kind of learning sequence (based on Gagne's 9 events) and make sure the objectives are supported. Then, when I write the test, it is supported by the course.

Bottom line, I think ADDIE or any other version therof should be used intelligently based on the situation. The design docs are not an end in themselves, but a way to make sure everyone has agreed to the direction and end products.

The other benefit of fully developed design docs is for large projects with a big team -- helps everyone stay on track.

Also, check out the neat ISD models I stole from the web! (I'm such a geek!)