eLearning Weekly

I’m in an interesting position right now: I get to work on designing our organization’s mobile learning (mLearning) strategy and I get to develop mLearning applications, but things aren’t working 100% as I would’ve imagined. I’m finding there are more roadblocks that I expected and they’re popping up in unusual places. I want to document my experience here…and I appreciate any feedback / tips you can provide.

So, here’s what I’ve recently learned:

• If you’re thinking about implementing mLearning, make sure you’re doing it for the right reasons. Don’t use mLearning because you think it would be cool, or because somebody else is doing it. Otherwise you’ll find yourself wandering around with the proverbial hammer, looking for nails to hit. I recommend that you research mLearning a bit and then see it as another tool in your toolbox. Use it when it is the best solution for the situation.
• The hardest part isn’t the technology. The hardest part has to do with politics, logistics, and security. Be prepared to involve several departments and get ready to face barriers. Just stay creative and look for ways to work around these road blocks. Read case studies to see how other companies have overcome obstacles and seek out blogs, articles, etc. Share the info with peers (ahem).
• To SCORM or not to SCORM, that is the question. When developing mLearning applications, decide early on if you need to track usage in your LMS. If so, you’ll need to research something like Pocket SCORM or OnPoint’s CellCast Solution. Fair warning, though, this definitely adds complexity to your project. You may even want to consider the SCORM tracking to be the second phase of your mLearning deployment.
• Know your audience and the devices they own. Create your mLearning solutions based on this info. If your learners have a wide array of devices, aim for the lowest common denominator: Use voice and text-based solutions rather than fancy animations, web-based content, and downloadable applications. There are podcasting solutions that allow for delivery via phone call, and there are SMS text-based learning solutions that can be quite effective, too. Remember Occam’s razor: "All other things being equal, the simplest solution is the best."

I hope all of this doesn’t come off as being too negative, but I’m trying to be very open about my experience. Please chime in - I’d love to hear your thoughts!

Over the past few weeks I’ve built a few small mobile learning (mLearning) applications and I’ve learned several lessons along the way. Here’s a brief recap:

• First, as I’ve mentioned before, the point of mLearning is not to create a 45-minute course that can be accessed on a cell phone. mLearning is best used for performance support: quick, easy look-up tools for your learners are a good place to start.
• Second, it’s easier than I originally thought. I’ve found that a small web page - when formatted properly - can be the simplest way to start with mLearning. Give it a shot: Create a basic HTML page, put it on a web server, and then go to it using your phone (if the phone is web-enabled). That’s it. Of course, if you add images and Flash, things get more interesting. Take it one step at a time and you’ll see that it’s not too bad. (Now, don’t get me wrong, there are some parts of implementing mLearning that get complicated, but I’ve found the hardest parts are related to politics and logistics.)
• Third, people get really excited when you demo what you’ve created. After doing a demo of your work, ask people to start thinking of additional mLearning tools that would be helpful. I got some great ideas from colleagues just by giving them a quick demo and then following up with questions. I kept hearing, "It would be really cool if you could (do XYZ)."
• Finally, Adobe’s Device Central is very helpful for testing. Device Central is an emulator that allows you to test your mLearning apps on your PC and see how they’ll render on a variety of cell phones.

Have you tried building mLearning apps? If so, share some tips here!

If you’re interested in Mobile Learning (mLearning), check out Clark Quinn’s free white paper titled, "mLearning Devices: Peformance To Go." (Get the PDF or read his blog post.) Clark presents his theory of mLearning and explains why mLearning is important to consider as an option for our learners. He states that mLearning is more about doing than about learning. He says, "We learn to accomplish something: to get better at things we need to do, to better perform those things we want to do, to be more effective, more efficient, smarter, even wiser."

Clark also dispels several common misconceptions about mLearning, including:

• My employees don’t have mobile learning devices
• Those small screens are too limiting
• Too hard/costly to program these things
• Limited to (smart) phones
• I don’t know what (devices) employees have
• Mobile devices aren’t secure

Clark then outlines the types of mobile devices that are often used for mLearning, including cell phones, digital media players (ex. iPods), GPS units, handheld gaming systems (ex. PlayStation portable, Nintendo DS), and PDAs. He avoids classifying laptops as mobile learning devices, mainly because they function the same as a desktop PC when internet connectivity is available. (As an aside, I once heard Judy Brown state that mLearning takes place on portable devices that are within arm’s reach and have untethered power supply that can last for at least a day. I thought that was a pretty solid definition.)

The white paper then goes into some of the specific functions and connectivity options available in mobile devices (ex. GSM, CDMA, WiMax, IR, Bluetooth, WiFi). It’s a great little summary, especially if you’re not familiar with these technologies.

I have high hopes for mLearning, but I still have a few logistical concerns about it. They include…

• Do all employees at your organization have a mobile device (ex. a cell phone)? Sure, I know most people do, but will an organization buy a phone for the few that don’t currently own one?
• Will organizations make their employees use their personal devices (phones) to access mLearning materials? What if people aren’t comfortable with this?
• What if employees don’t have a data plan on their personal phone? Will the organization pay for their data plan so they can access mLearning materials?
• Is it unfair to make mLearning materials available to a lucky few in the organization who have capable devices? Could the left-out employees complain if they don’t have access to the same learning materials as everybody else?

Organizations are working through these scenarios now. I’m guessing best practices will emerge in the coming months. Please chime in if you have thoughts on this!