What are the mlearning mistakes you’ve seen or experienced that you’d recommend others avoid?
A- Customize your solution for mlearning. I agree we need “continuity” from an enterprise product running on a Web browser to a mobile device. But it can’t be the same. And it can’t be all of it. Even if it’s all of it, redesign your presentation strategy (be it features or content).

(Never implemented, but my idea is)

QR codes on everything, even the front door for new workers. They link to places on your intranet with tutorials, videos, reference info, maps, instructions on how to use equipment, safety and training requirements, etc. No more asking people for help, just get your mobile device out, scan and learn just-in-time. Orient new people by leading them through the workplace to people and locations and resources and their desk etc. Sort of like a guided FourSquare experience.

Idea number two is a way of capturing what people are scanning to see what is hot, working and helpful.

2. Assuming your target audience uses a particular mobile device and so designing with blinkers on.

Response to your questions (numbered):

1. Don’t try and create a separate mobile learning strategy. Instead concentrate on weaving ‘mobile’ into existing strategies. This will help with adoption as it will not be viewed as ‘something else’ or ‘yet another initiative’

1. When you are faced with doubters, ask them to reflect on EXACTLY how they have used their phones over the past week or so – this is likely to show them just how useful the device to ‘them’ and (no doubt) to their employees/learners

1. Try and get your foot in the door by using existing apps to help enhance what your/your Org is doing http://tayloringit.com/2012/01/getting-your-foot-in-the-door/

2. Avoid the perception (in yourself or others) that mobile learning is ‘just’ shrunken down desktop learning http://tayloringit.com/2012/06/is-this-another-fine-mess-weve-got-ourselves-into/

Craig