Subscribe

Your email:

More from Allen Interactions:

UpcomingWebinar
5myths(2)

 ZEBRAZAPPS

CS&DM(2)

WhitePapers(2)

Connect with Us!

Facebookdescribe the imagedescribe the image

e-Learning Leadership Blog

Current Articles | RSS Feed RSS Feed

When You Really Need To Know

  
  
  

Angel Green

by Angel Green, Instructional Strategist

An interesting thing happened at lunch one day this week. The hostess seated me next to a table where restaurant employees were participating in a training program on alcohol safety. Though, to be honest, “participating” is about the worst word to accurately describe what I was observing.

Propped up at one end of the table was a portable DVD player, playing what appeared to be a well produced video on the restaurant’s policy on alcohol. Certainly this is very important and (likely) legally required information that employees at a restaurant need to know. However, not a single person at that table even glanced at the DVD.

As I watched, the trainees at the table next to me chatted, laughed and stole French fries from one another as the video played on.

Obviously, this program was created with the intent of actually teaching the learner something. However, the problem is, this very expensive program did nothing more than keep those employees hostage until the box could be checked indicating training was complete. So, how will these team members actually learn what they need to know?

Shaker - Custom e-LearningMy theory is that an experienced team member will say, “Oh, you took that Alcohol Safety training? Well, let me tell you what you really need to know.”  This seasoned employee proceeds to share tips on spotting fake IDs and tells the story of Joe who was arrested for serving a minor using a fake ID, some questions to ask guests to determine if they are intoxicated and finally some enthralling stories about the police being called to regulate issues when patrons have had one-too-many.

So, as training developers and designers, how do we ensure that the programs we create do not simply hold the learners captive? How do we develop training that’s of the “what you really need to know” kind?

Think back to what the seasoned team member shared: how Joe was arrested for serving a minor and how to spot fake IDs, how the police needed to become involved when guests had one-too-many and some good questions to ask to ensure you aren’t serving intoxicated patrons. These stories and consequences made the learning meaningful to the new employee. The listener develops a sense of motivation because of the potential consequences from his or her own actions on the job.

What once was a set of arbitrary ideas and laws had now become real enough to alter behavior. And, isn’t that the holy grail of training – presenting information and facts in a way that it is worthy of altering behavior? When you create interactions that mimic these real world consequences, you offer your employees the opportunity to learn and to change their behavior.

Present your learners with an interaction in which they try to sell a new product without appropriately identifying the buyer’s needs. What happens? Will they get the sale and get that commission check? Not likely. Show a bartender a series of IDs and have them decide if they would choose to serve the patron.  What happens when a fake ID slips past? The learner gets “arrested” for serving a drink to a minor.

When designing your training, start by identifying the consequences – positive, negative, neutral – instead of identifying the topics that should be included. Then, create a risk free environment where learners have the chance to make a decision and experience the impact of that decision. In doing so, you will move light years closer to creating training that shows the learner “what they really need to know” – and they won’t feel as if they’ve been held captive; in fact they just might have a little fun!

Comments

Very thought-provoking and engaging blog. These ideas are not new, of course, but they certainly bear repeating. I see their application immediately in compliance training, such as the example you give. Have you some tips, other than case studies, of how to teach this way with new technical analysts who don't know the basics of the software at first, but whose goal is to troubleshoot, requiring higher order judgements? Thanks.
Posted @ Wednesday, August 24, 2011 10:48 AM by Paul Safyan
Extremely relevant and informative! A well written, concise blog that I will be sending on to my Masters students that are now developing programs designed to address the needs of a specific population.
Posted @ Wednesday, August 24, 2011 1:26 PM by Linda
Very well written. I learned from this. Thanks.
Posted @ Wednesday, August 24, 2011 4:17 PM by Larry
It`s great to know the people behind Allen Interactions, thanks all of you for sharing your experiences so generously.  
 
Angel, the experience you write about shows that people don`t always pay attention to instructional materials simply because it is relevat for their work. The content in the video was clearly relevant to those employees, but their lack of interest means that, often, it takes more than simply presenting information for people to reflect and change.
Posted @ Wednesday, August 24, 2011 6:49 PM by Daniel Albarran
For me the article was timely and spot on. Thank kyou.
Posted @ Thursday, August 25, 2011 5:55 AM by LC
Daniel: I think your comment goes to the heart of the matter. There are no immediate consequences for NOT paying attention, and, as Angel points out, the best way to learn may be from savvy veterans...or making the presentation force some action on the learners' part.
Posted @ Thursday, August 25, 2011 8:55 AM by Paul Safyan
Thank you for a good post. I fully agree that this type of strategy should be used in compliance training.After all without gaining learners interest it's not possible for learning to happen and change in behavior to take place.I often read Ethan's post and enjoy the insightful information he shares.I enjoyed reading this one too. Thanks again for sharing your knowledge. 
Posted @ Thursday, August 25, 2011 10:41 AM by BZ
Thank you all for your thoughts, opinions and comments. This being my first blog, I really appreciate the feedback and the time each of you took to respond. I am very excited to continue to hear from you and how you may have used, or intend to use, consequence based interactions in your learning. 
 
Paul: Since “technical analysts” is a broad description of a job role, I’ll make an assumption. My assumption is that, while knowing how to use the software is important, what would be really impactful is if learners knew how the software is used. If this is true, then I think you’re headed in the right direction. You’ve identified a task – troubleshooting, a competency/skill – higher order thinking, now you need to identify the consequences. To do so, answer some questions – or seek to find these answers – of what happens when troubleshooting is not done quickly, effectively or efficiently? Is it a loss of money for a software implementation that has to be delayed? Is it an upset end user who misses a deadline because his/her software is frozen? What are the real business or human impacts that can be solved with the help of a great technical analyst? Build your interactions based, not on the software itself, but on the end result and you’ll create training that is engaging and meaningful to the learners. 
Posted @ Thursday, August 25, 2011 10:47 AM by Angel Green
Thanks, Angel. Yes, you understand my situation. Where I am struggling is (1) How to teach and measure the teaching of good troubleshooting, and (2) How to measure the consequences in some meaningful metric. We have metrics about time and call volume but not about quality that we have been able to identify.
Posted @ Thursday, August 25, 2011 11:11 AM by Paul Safyan
Comments have been closed for this article.