Here are some of the mistakes that I have made and learned from when creating a design.
- Somewhere along the design process, forget the learner and his needs.
- Let the Subject Matter Expert (SME) lead the design.
- Don’t consider the implementability of the design given the learner’s work environment.
- Don’t onboard the training holders and understand their expectations.
- Don’t enable the development team to realize the design.
3 comments:
Thanks Pooja. I will add my top 5 to this list.
1. The design format/template becomes more important than the actual design -- "...but this is the format provided by the client...".
2. Let time lines bog you down and cut corners -- "...there is no time for design..."
3. Get swayed by effort metrics -- "...this project is on very tight budget, we can't spend time on design..."
4. Agree to everything the client suggests -- "...but the client has asked for this..."
5. Forget to onboard the SME. This is similar to your point of letting the SME lead the design -- "...the SME wants it this way..."
Submitted on 2008/03/04 at 4:01pm
The number one thing I see developers do wrong is forget that the correct path of a scenario is actually a single narrative that should make sense on it’s own. It should be a “story” that hangs together on it’s own. I think if people start doing it this way, they’ll wind up with much more engaging scenarios. Another problem is I think people neglect to read their scripts aloud, a simple trick to ensuring that you’re writing believable scripts.
Submitted on 2009/02/20 at 2:18pm
Hi Pooja and Manish, good list and I agree with all the points. What I realize is that you sacrifice good instructional design if you start saying things like this is what the client wants. I guess we are offering our expertise to the client and we need to suggest the best possible solution.
Post a Comment