Designing #mlearning Book Review – Chapter 6

Posted on Sep 10, 2012

As I mentioned in a previous blog post, I intend to provide a brief synopsis of each chapter of ‘Designing mlearning‘, but more importantly I intend to answer the questions that Clark poses at the end of each chapter and then pose those same questions back to you ‘Dear Reader



Chapter 6 – Getting Concrete

This chapter provides an insight into several real-world, concrete examples which demonstrate a range of mlearning possibilities and applications, each of them following this template. (which with a little tweaking, would make a nice business case template)

  • The organisation: Who was involved?
  • The challenge: What was the need?
  • Why mobile: What made mobile a solution?
  • Making the case: How was the solution presented?
  • The solution: What was actually done?
  • The benefits: What was expected?
  • The results: What was observed?
  • Lessons learned: What recommendations came out of this project?

There were an impressive number of examples in this chapter and I won’t spoil your future reading by going into each one, however what I will highlight is a few surprises that some of these case studies held for me?

I had always assumed that Blackberry was a particularly crappy platform to develop for and in turn deliver content via, this assumption was based upon the low number of apps available for BB and the teeth-sucking and eye-rolling that took place whenever BB development was suggested to some former colleauges. This chapter helped to reshape my perceptions of what can be achieved via BB as a result of reading a case study which centered around the delivery of pharmaceutical sales training and performance support to field sales teams utilising their BB Bold 9000 and 9700 devices. This reshaping of my BB expectations will certainly be of use to me on in my new role within an organisation whose mobile solutions at this moment in time, is BB.

Reading many of these case studies also brought to light just how long many people/organisations/vendors have been developing mobile solutions (as we might define them today) with Hybrid Learning Systems developing XML SCORM compliant mobile solutions in 2006 – that’s 6 years ago folks!

There are no questions being posed at the end of this chapter, which was a little disappointing as I found that in previous chapters they had helped to focus my thoughts and gave me an opportunity to openly reflect and share.

One Comment

  1. @dbswe I’m on it…

Enough of the lurking! Why not leave a comment? You know you want to...

%d bloggers like this: