If you ask a learner how they want to learn, taking a high-gloss eLearning course is rarely mentioned. Instead, what we all consistently hear is that people want personalized learning - a term easy to throw out there but not so easy to define.
Richard Calutta, from the US Department of Education at the Office of Educational Technology, has a simple formula for what it means to personalize learning:
This is the 3rd in a series of 3 pertaining to how personalized learning can be applied to education and training. In the first I explored the application of personalization in K12, and in the second how personalization can be applied to high-skill knowledge workers. In this post, I explore how personalization is already enabling service workers in the retail industry learn job skills at a fraction of the cost of traditionally-developed training.
Personalization: The Training Solution for Service-Oriented, High Employee-Turnover Industries
This is the 2nd in a 3 part series addressing the impact of personalization in the education and training markets. In the first post, I addressed the application of personalization in K12. In this post I address use cases that apply to a high-skilled knowledge workforce.
Personalization for the high-skill knowledge worker
Personalized learning has different applications for different audiences. In the previous post, I discussed how personalization is a key plank in the educational reform movement.
Over the next weeks, I will be writing about personalized learning and how that applies to different learning populations. At first I’ll address K12 learning, then I’ll address how personalization affects a high-skill knowledge workforce, and a service workforce.
It seems that, for years, people have been writing obituaries for the corporate Learning Management System (LMS). Just do a quick search for “LMS is dead” and you’ll find many blog posts, articles, webinars and conference presentations discussing its demise. Some people, myself included, have even been actively working towards this end trying to hasten its death through carefully worded argument and debate. The trouble is that many organisations have invested heavily in their LMS. Somehow that investment needs to be recouped.
In our first post on agile development from January (http://bit.ly/I67W8Q), we discussed the basics of the Agile software development process and why it is good for software vendors and their customers. This article looks at what makes a good User Story – the core of defining requirements.