AG09 - 502: Creating Curricula for Multiple Delivery Methods – Tools, Tips, and Tricks

Presented by: Rebecca Jimenez, CUNA Mutual Group.

So this session is about the Tools, Tips and Tricks utilized by instructional designers... but not every instructional designer. Rebecca first completed an audience analysis because this session was more only towards novice instructional designers, and those ISDer’s who manage other beginning instructional designers. Fortunate enough, I fit into this audience so I decided to stay.

Some of the multiple delivery methods or platforms that were discussed throughout Rebecca's presentation were:

• Online
• Synchronous
• Web
• Virtual
• Research Centers
• Job Aids

Throughout the session there were many great tips for designer's presented from Rebecca that I would like to share:

Tip #1: DON’T get caught up in the end solution. DO focus on the assessment.

• If you don’t know what you will be accessing, you can not get there.
  
  
• Tools to use – Questionnaires, Performance Data, Task Analysis, Observations, etc.
• Assessment Tools - GAP Analysis (Needs Analysis) and Real World Scenarios (Observations).

Some assessment questions:

• What does future state look like?
• What does current state look like? (Ask future before current because it is usually difficult to view current; it is best to work backwards.)
• What does the learner need to DO that they don’t DO now? (Tasks)
  
• What situations will the learner DO this in? (Scenarios)
• What is currently available to aid the learner in DOING this? (Tools)

Tip #2: DON’T assume you know how a solution will fit the business need, or that your client does. DO tie the solution to the business need

• Define the business need.<!--[if !supportLists]-->The “audience” are making too many mistakes “doing what activity”, which results in “business impact”. When “audience” performs to “level and measurement”, this results in “business impact”.
  
  

Tip #3: DON’T focus on the development. DO focus on the design.

• What's the difference? Designer is the architect (writer), creates the blueprint based on assessment, theories, etc. Developer is the constructor (illustrator), builds the building from the blueprint.
• Why is it important? Because it is very difficult to do both at the same time.

Other useful tips:

• Tell a story
• offer most EFFECTIVE solution
  

"Your SME's are not SME's on development, they are SME's on content." - Rebecca Jimenez