The 6 Hottest Training Technologies

OK, just off the top here, I want to apologize for the title.  I am not a fan of click-bait but I was just copying and pasting an article I wanted to comment on in this blog titled:  The 6 Hottest Training Technologies That You Can’t Overlook.  But, to spare you actually clicking on the links, let me list the 6 below:

  1. Mobile learning
  2. Video-based training
  3. Virtual environments and avatars
  4. HTML 5 and responsive design
  5. Automation and adaptive learning
  6. Big Data

There you go.  Now, don’t you agree those are the hottest?    Good, now that is done, I want to talk a bit more about mobile learning.

Mobile learning – it seems like we have been hearing this for years that mobile learning is coming.  But, I think it is still further out then many may expect.  Here is reasoning.  I believe we are repeating history of back when “e-learning” became the new buzzword.  It was going to revolutionize training it was.  But it took a bit of time.  What happened at first is that everyone just picked up their paper manuals and training material and digitized them.  Boom, e-learning delivered!!!  But, the learners were ‘less than thrilled’ with the new revolution.  It took years for the training area to change not only how they delivered the content, but how they thought about developing the content while utilizing new technology.  As the technology matured, so did e-learning with more engaging content and programs.  I feel that we are the early stages with mobile learning. Sometimes the solution is take the current content and make it accessible on mobile.  Wait, the module is too long for mobile.  OK then, let’s take the 30 minute module and chunk it up to 6 five-minute modules.  There you go, mobile learning delivered!!!!


And hey, that is all fine and dandy for now, but I think it is still early.  I think we need to forget about how we do “e-learning” now and think more about the mobile device and how users consume content.  Here is an example using two large social networks, you may have heard of them; called Facebook and Twitter.  Yes, those ones.  Well, it seems like almost everyone in the free world uses one or both of those services. And what do they both have in common from a content consumption point of view?  They both deliver content in a timeline.  Here is a definition of a Twitter timeline and a Facebook timeline.   I also included an image of the Twitter timeline in this blog.  Basically, content is delivered in a stream that views scroll down to see the latest updates on top.  And it seems that users are ‘OK’ with getting content in a timeline.  So, why do we not have mobile learning in a timeline?  Makes sense, doesn’t it.  It is a format that both users and designers are already familiar with and navigation is easy to understand (hint, scroll down on your phone).  So, why aren’t developers using the most common content delivery user experience?  Well, for one Mr Smart Guy, I am not sure if Code of Conduct is going to be too interesting in a timeline (sorry, that was me talking to me…and now I am going to answer me).  Well, maybe, and maybe not.  But if I locked a bunch of e-learning designers in a room for a week, and said they had to deliver a course in a timeline, I think they might come up with something.  And maybe being in that locked room will help people start to think differently.  Of course, it may not be a timeline at all.  Maybe it’s an interface like What’s App or Instagram or Snapchat.  Or maybe no-one has thought about it yet.

Anyway, I believe that mobile learning will continue to continue to grow and evolve (hopefully).


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: