Archives For

Have you ever been sitting in a training course, perhaps learning all about the fabulous new vendor management system your organization is implementing, when you felt that familiar buzz in your pocket? A new email has arrived via your smart phone and you just can’t resist responding. But not to worry, you can do that and still listen to the instructor, right? Fast forward a few weeks and you need to bring in a new vendor ASAP, but you just can’t remember how to use that new system. You don’t have any notes on the part that is stumping you. What to do? Too bad there aren’t any tools to help you out.

Most of us think we can multitask to some degree. We think we can read a book and listen to music at the same time, or text while driving (please don’t). We think we can listen to a speaker/lecturer while responding to an email. We think we can walk and chew gum at the same time.

multitasking myth mug

While you might have mastered that last one, study after study has shown that Continue Reading…

sharingOne of the hardest lessons to learn growing up is how to share… how to share your toys, your candy, and maybe your room with a sibling.

As a child, it is difficult to get past the thought “but, it’s MINE!” We try to hang on with tightly to what is “ours” and, if we are goaded into sharing, we attempt to dictate how we share (“You can play with the toy for 5 minutes ONLY”.)  Sharing is made a bit easier for children when there is a perceived advantage to them (“You can play with my toy if I can play with yours.”)

Organizations, especially before the turn of the century, had a very similar approach to sharing.

Organizations kept what was perceived as Continue Reading…

I was asked recently to define situations where eLearning is a smart management decision over the same course in an instructor-led training (ILT)  format. There is a tremendous amount of information available about the advantages of eLearning as a delivery method, but there is not a whole lot devoted to this particular question.

I decided to poll some of my colleagues to get their take on this question. I’ve compiled their responses along with my own thoughts and I hope you find them helpful if you are considering eLearning for your employees.

 

Top 5 Situations where eLearning can be a Smart Management Decision

  1. Situation: Your audience is geographically diverse. In this situation, your audience of learners may be scattered across Continue Reading…

Let’s face it…ERP training is typically boring at best and utterly overwhelming at worst. The systems are complicated, users have to learn new terminology, new codes and numbers for products, vendors, accounts and everything in between. And then there are the new procedures.  Many, many new procedures. I’ve seen week-long SAP training courses covering over 100 procedures for people who plan and scheduled production in a manufacturing plant. Really?  That’s a lot to ask people to remember…and I seriously doubt they do much of the time. (In defense of the nameless, travel was necessarily a huge factor in the case of the week-long class. You have to work with what you’ve got.)

So what can we do to help more of the important points stick?  We’ve tried the review games and the quizzes and the endless exercises, and those things all help to some extent.  Ultimately though, those things tend to just blend into the rest of the course in our memories.  What’s needed is a hook that will hold the learner’s attention long enough to move the memory into long term storage. One way to do this? Tell a good story.

Connie Malamed, The eLearning Coach, wrote a great post Why You Need to Use Storytelling for Learning  on this subject with 10 reasons why storytelling works as a learning tool.  Her 10th reason sticks out in my mind, “Stories give meaning to data,” for how well it applies to ERP training.

Even a simple ERP system contains more master and transactional data than most people can fathom. The trick is to learn how to locate and interact with “your” data effectively.  And, to understand how the choices made while creating important documents like, say, contracts can have far reaching consequences.   I feel a story coming on…

A few years ago, I worked on a project for major university that was implementing PeopleSoft Financials. I was tasked with writing  training manuals, designing eLearning modules, and designing classroom exercises and activities for the areas of purchasing and travel & expenses. Then, I actually ended up teaching the courses I had designed to hundreds of users over a period of 8 weeks.

This was a huge change for these folks. And the content was boring. The person in charge did not believe in incorporating anything fun into training that might help people remember important stuff.  It really fell to us as instructors to help people understand what they would need to watch out for back at their desk.

When teaching the users about creating purchasing contracts, one of the very important points to remember was that you have the create the right kind of contract…was it a quantity-based contract, a time-based contract, or a quantity and time based on contract?  Selecting the wrong option could come back to haunt you.

To illustrate this point, I told a (mostly) true story that had happened at the vet school a few years back. A new study on the developmental stages of chimpanzees was starting up and a contract was created with a vendor to supply the vet school with 240 chimps. The university planned to have the young chimps arrive in groups of 20 once every other month over a period of two years. But, the contract didn’t say anything about that plan…only that the university wanted 240 chimps.

Imagine the bad day the contract person had when all 240 chimps arrived at once a few weeks later. I understand it was not pretty.

Another important point in purchasing documents? Always double-check the unit of measure. And another mini-story: Nine years later, our small company is still trying to use up the pallet of napkins ordered by an admin assistant who had meant to order a case.  See what I mean…far reaching consequences.

Funny thing though. The university used an online skills assessment at the end of each course to determine if the user passed the course and should be authorized to use the system.  The assessment tool had a wide range of reporting options and I could look up groupresults by question and instructor.  Not a single person who heard the monkey story in one of my classes got the assessment question about importance of contract type wrong.  I wish I could say that for the rest of the questions.  The story apparently stuck. And, some other points without supporting stories obviously didn’t. The story gave them a hook for remembering at least that one important point.

I had a theatre history professor in college who had a particular fondness for telling us stories about how important people in theatre history died. While I don’t really remember any other details about her, almost 20 years later I still remember poor Mary Saunderson who died in a tragic pageant wagon accident. The story stuck with me.

So, how can you use storytelling to help engage learners and enhance retention in your training classes?  Here are a few tips:

  • Identify a handful of important points in your course that you need learners to remember and develop stories to illustrate those points.
  • Utilize subject matter experts and business users to help you craft stories that will help your points be remembered.
  • Don’t be afraid to use humor and/or “bad examples” in your stories. A story that illustrates what not to do can be a very effective tool in remembering important things to do.
  • Practice your stories. The way in which a story is told is just as important as its content.

Happy storytelling!

 

Once upon a time, a major manufacturing company implemented SAP to handle all of their North American operations. Several years passed and the company implemented new SAP modules and fine-tuned existing modules. Everything was working well and they were getting a good return on their system investment. Finally, it was time to start bringing the wonder of SAP to the company’s global operations.

The company was smart and planned a phased global implementation over several years. First they went to countries south of the border where a different language was spoken by many. So, the company scribes (Instructional Designers and Documentation Specialists) and their SMEs created materials in their native tongue and sent them along to another company to translate into the 2nd language. But alas, the screen shots were still in the 1st language! The translators did not know SAP and the scribes did not know the 2nd language to take new screen shots.

So, a third company was hired to run SAP transactions in the 2nd language and place screen shots in the translated materials. Finally the documents were ready for end users…and then there were changes to SAP… again, and again, and again. The scribes were quickly succumbing to the flurry of documents, back and forth, seemingly endless versions in various states of completeness. But, in the end, the scribes prevailed and managed the storm for this round.

Next came some small implementations in countries across the ocean. These projects added two more languages to the document versions maintained by the scribes, but blessedly few SAP changes. Shiny new digital libraries were built to house the materials.

The next year, five more countries, 2 more languages, and many new SAP processes came online. With the addition of these countries, the scribes were managing up to 12 versions of each document with translation and screen shots. They were dealing with almost 1200 documents in the 1st language alone, and quickly losing the battle. But, help arrived in time and once again the battle was won with many extra man-hours.

Today the company is ½ a year away from bringing 3 more countries online, representing 2 additional languages, bringing the total to 8. This time, the scribes have been challenged to provide as many of their documents as possible, fully translated, 6 months before Go Live to be used by system testers. The scribes shudder…6 months is an eternity of testing and update cycles that will force changes to the “completed documents” over and over…how many hands must touch these documents with each change? The scribes are despondent. How will they cope? This time, they may just lose the battle.

Unfortunately, that little fairy tale is based in real life…my real life. My client and I are fully encased in the Snowball Effect. An uncomfortable state in which constraint after constraint has been layered on top of what was once a fairly simple process until the process is almost paralyzed by said constraints, but the project keeps rolling relentlessly forward. The effort involved in managing document updates, documenting new transactions and processes, and then managing the screen shots and translation or retranslation of those documents is simply overwhelming. The point of paralysis is close, where the management of the process will take up so much time that the progress on new material halts. The snowball becomes unstoppable.

So, what to do? First and foremost, we are finding compromises. Here are a few we have made with the project to mitigate the snowball effect and continue forward progress:

  • Instead of delivering thousands of pages of printed materials for the testers, we are delivering the documents electronically on a local print server via a simple web page. This compromise resulted in 3 additional weeks of development time since that time was no longer needed for printing and shipping activities, and the ability to update date the print server with newly translated versions on a daily basis. This compromise saved the company a significant amount on printing costs as well.
  • We have compromised on translation timelines for the other languages not directly related to this implementation. These will now be handled after the bulk of the work for this implementation phase has passed. This has drastically reduced the volume of documents to be managed at one time and has allowed us to focus forward instead of backward.
  • We are compromising by providing limited access to secured network sites and systems for the translation and screen shot companies in order to expedite document transfer. This represents an additional expense, but saves an enormous amount of time as documents progress through screen shots and translation.

So what is the moral of our story? For me, I think this shows us that while an ERP system like SAP has an amazing potential to globalize business processes, we can’t forget that the people using the system will always have specific local needs. As the number of localizations increases, it is easy for the snowball to start rolling and eventually mow down everything in its path. In order to stop the snowball, we must compromise and find paths that we might not normally take.