Case Study- Reducing eLearning Cost to 50% by Using Must-Learn Lessons and Micro-Learning - Tip #61

This case study presents a series of strategies and tactics which help you answer these questions:

• How do I respond to rapid business needs for e-Learning?
• How do I decide which approach can dramatically increase the speed of development and how do I calculate the returns?
• How do I work effectively with Subject Matter Experts (SMEs) to obtain content?
• What strategy ensures that the software meets rapid development and cost objectives?

Here are some excerpts from the article:

• Rapid e-Learning as a term is an oxymoron. e-Learning is inherently rapid.  Its principles are all about speed and quality. It provides immediate learning. Its tools and software are fast, inexpensive and have more capabilities than we can even imagine. It is personalized and just-in-time learning at its best.  
• Our e-Learning programs are at least 50% heavier than they should really be (too much content).  These are at least 75% cumbersome (too much control) than what is required by e-learners.
• We need to present an architectural plan or infrastructure for our e-Learning program so all contributors can follow a process.
• Remember "Garbage in, garbage out"? Well, it may be more like: "The more garbage is generated, the slower the speed or flow, the higher the costs - and the quality stinks."
• Software developers and suppliers have their own "beliefs" borne out of their backgrounds, origins, interests and skill sets.
• Add interactivity only whenever and wherever it matters.
• This architecture provides clear direction for design, processes, and software and resource requirements - that lead to a clarity of standards and streamlined decision making.
• Reduce the amount of content to focus on "must learns." This increases the speed of development, cuts the costs and meets e-learners' needs.
• The ability to randomly select application  points allows e-learners to learn or apply ideas rapidly; it cuts down by 75% the burden of forcing learners to go page by page.
• Assist SMEs to organize, categorize, write and display the content that meets the standard of your architecture (structure their contribution so it is easy and time efficient for them).
• You can also maximize the full capability of the software when you know the end results you wish to derive.
• Not all content should be in an interactive form. Don't rush into converting content into interactive format if  plain text, images and references will work. If only 20% of your content needs to be interactive, then you already drastically reduce your development time. You also help the learners focus on what is truly important and what matters - which is one of e-learners' needs.

Ray Jimenez, PhD
Vignettes Learning
"Helping Learners Learn Their Way"