A little over a week ago I shared the first five of ten mobile learning resolutions for you to consider in my post, “Talkin’ ‘Bout Some Resolutions, Part 1.” Did you get started on any of those? I am going to share five more in this post, and most of these will be rather challenging if you haven’t tackled the first five. Well, I guess it’s OK if you didn’t attend a mLearning conference in the last two weeks, but you could have registered for one! And the other four, you should have a healthy start.
So, what’s next? How can you start moving forward and making progress towards the goal of implementing a mLearning deliverable in your enterprise? These next five resolutions will allow you to make big steps towards that goal:
- I will assess my current learning curriculum for potential mobile learning content. Review your active eLearning, CBT, and ILT, and identify some content that has a high potential to be successful. Maybe it is something as simple as a checklist of best practices or safety standards. It might be some valuable employee onboarding information. Look for that “low-hanging fruit” that resonates with your target audience. You are most likely going to make this first effort relatively simple, so you don’t want to launch something overly complicated.
- I will build a mobile learning development team. Who is in your department that is going to help you get to your goal? You are going to need some specific roles and responsibilities such as instructional designer, developer, IT, quality control/testing and project manager. You are going to want someone who is going to “champion” the effort and evangelize it within the organization. Which of these roles are you going to take on? Build a team of people who see the power and potential of mLearning so you are all working with passion toward the common goal.
- I will learn about the different types of mobile delivery. Mobile website? Mobile Web app? Native app? Hybrid? Aaaah! Don’t get frustrated. The delivery that is best for you is going to be driven by different factors and help you make this choice. Delivering to a variety of mobile devices? Probably not a native app. Want to make use of the camera? Native app, probably! It’s good to know what each of these delivery types is capable of and where they falls short. Your IT person is going to want to have a say in this choice so discuss it with them as well. This resolution is a big one as you will most likely need to learn about mobile application management (MAM), mobile device management (MDM), mobile security and BYOD (bring your own device). I know all these acronyms might make you want to BYOB, but you don’t need to become an expert in all of this. Just make sure you understand the principles and advantages and disadvantages of each. Your IT team member can do the heavy lifting in this area.
- I will consider a prototype for a deliverable. Float Mobile Learning is a HUGE proponent of the prototype. We write blog posts about it, magazine articles, give presentations – we talk prototypes to anyone who will listen! Why are we so high on prototypes? For one, there is less risk involved. You are going to make mistakes with your mLearning initiative, especially if it is the first effort within your enterprise. Why not make those missteps on a smaller, more manageable effort? Prototypes also help you keep the Big Three in check: scope, schedule and budget. The smaller deliverable will not cost as much as a full build, and it will have a shorter timeline. Also, it will give you a powerful and engaging deliverable to show your stakeholders and get them on board for the complete project.
- I will implement mobile learning in my organization for the right reasons. I saved this resolution for last, even though it is the most important one. Any mLearning project you develop must result in your target audience becoming better at what they do. Make them more informed. Make them more productive. Allow them to become more efficient in their job. Smarter. Safer. Faster. Happier. What does success look like for your mobile learning? Make sure you have that clearly defined in a business case and that you can measure it so you know when you have reached your goal. Don’t let the wrong reasons hijack your mLearning effort. If you hear yourself saying, “We are doing this because mobile learning is cool,” or, “The AVP said he wanted an app!”, be forewarned you might have a negative outcome. Build a strategy that leads to success so that your audience gets excited about learning on a mobile device. You will pave the way for many more mobile learning deliverables.
If you can hold to these resolutions this year, I can safely say you have a great chance of talking about your successful mLearning at the office Christmas party in December. Did you have any resolutions this year? Maybe some that aren’t on this list? Add them to the comments below or keep me posted during the year. I would love to hear both successes and failures. Lessons learned make us all better.
Have a great 2013 and happy mLearning!
Latest posts by Scott McCormick (see all)
- 5 Reasons Why Performance Support Solutions Are Vital For The Enterprise - February 17, 2016
- 8 Times Your Employees Can Solve Problems With Performance Support - February 3, 2016
- 12 Types of Work-Based Performance Support Tools You Can Use Today - January 20, 2016