In addition to speaking on mobile design with David Metcal at the Mobile Learning Jam at DevLearn, and with Richard Clark on pragmatic mobile development, I’ve got a contract with Pfeiffer for a mobile learning book. Yep, I’m writing another book. Flat learning curve, eh?
Seriously, I’m excited about the opportunity, because I’ve been on the stump for mobile for years, and think the market is right for mobile to finally contribute to organizational performance like I’ve believed since I wrote an article on the topic back in 2001. Consequently, I’m glad that Pfeiffer thinks the time is right for a practical book on the subject.
To make it a practical book, however, I need input. I hope to talk to some of the experts in the field, but I also want to hear from you. What do you think should be covered? What are your concerns? What are your hot-button issues? In short, what would be required to make the mlearning book for those of you charged with designing learning solutions? I don’t want to write a book for the sake of writing a book, I want to provide a useful guide. Please, let me know. Comments here are welcome, or other forms of contact, are welcome as well. Thanks!
The point is, we have to quit looking at it as design, development, etc; and view it not just as a process, but as a system. A system with lots of inputs, processes, and places to go wrong. I tried to capture a stereotypical system in this picture, with lots of caveats: clients or vendors may be internal or external, there may be more than one talent, etc, it really is a simplified stereotype, with all the negative connotations that entails.