If you're a trainer or design instructional material, your job is to train people.
But what exactly are you training them? What kinds of things? If your initial answer is "stuff for work," we can dive down a little deeper on that. The benefit of doing so is that once we realize that we train people on different kinds of "stuff for work" (or to speak a little more formally, we train people to help them with different types of learning), you can get a little more efficient and use different training techniques for each of those different types of learning that you want your employees to master.
That's what we're going to cover in this blog post. So if that sounds spot-on, continue reading. If you're not quite sure how you feel about it, keep reading nonetheless, if you can spare the time. You just might find some tips to make the training programs at your workplace more effective and efficient.
Let's start by giving some thought to some different types of learning.
So, let's go back to that earlier discussion of teaching workers, and wanting them to learn, "stuff for work."
Obviously, you know that's such a crude phrase it's silly. You can break that down immediately, right? For example, you'd probably agree that there are things that your employees have to "know," and other things that they have to "know how to do." Right? So if our goal is to start teaching out the different types of learning, we've got a little start already.
But we can go even deeper, breaking that down further.
How do these types of learning strike you?
We're going to spell each of these types of learning out for you in the sections below, but take a moment to review the list right now by yourself. Do you know what each of these are? Can you come up with an example of each? Can you think of times when you've tried to help workers learn each of them?
Now let's take a closer look at those different types of learning. Here's a list of the kind of things you'll probably want your employees to learn, with an example of each.
One way to look at training people is you can train them to "know" things and/or training them to "use" or "apply" that knowledge on the job.
When it comes to facts, you'll train people because you want them to know the facts. So you'll want them to be able to prove they remember the facts by having them repeat, list, or state them.
When it comes to the other types of learning, you want them to "know," but when it comes to on-the-job performance, you want them to be able to apply that knowledge. So that's what you'll be trying to teach them, what you should let them practice, and what you should assess their learning--by having them apply it in a realistic way, like they would on the job.
Here's a table to help explain that better.
Now that we've identified the six different types of learning listed above, let's look at some suggestions for how to train your workers for each type of learning.
As Clark notes, "facts are unique, one of a kind information." (1)
For example:
It's inefficient for the brain to process, store, and retrieve facts, simply because they're somewhat random. All our brains can do is commit each individual fact to memory. And traditionally, job training programs (and yes, school education too) has tended to rely too much on getting people to remember facts.
Instead of having people remember facts, try whenever possible to simply create job aids (or references) that they can refer to on the job and/or during training. For example, if a machine operator needs to enter up to ten different codes into a machine at different times of the day based on different circumstances, don't try to teach the operator to remember all the codes. Instead, during training, provide a list of the codes and teach the operator to enter them at the correct times. Likewise, provide a job aid that includes a list of the codes at the spot in the work area where the operator needs to enter them.
In some cases, a job aid won't cut it and you will have to provide some training to your workers on the facts themselves. Below are some tips from Clark's book:
A "concrete" is something unique and specific; Clark's example is the 1040EZ tax form (which is distinct from the concept of "tax forms"). Another example might be "this is the off button for the bagger." One way to train your workers to identify concrete facts like this is to include a diagram with labels. For example, imagine a diagram of that bagger, with various parts, including the off button, labeled.
Present data, such as specifications about machine operating conditions, in the form of a list or table instead of embedding it in a normal written paragraph. Presenting data in this manner makes it easier to scan and process.
In some cases, a fact might create an association between two concepts. A simple example might be "great white sharks are the apex predators in California's Red Triangle region." A more work-focused example might be "ideal operating conditions for paper machines is to run between 85 and 95 percent peak efficiency."
In that example, present the fact in written materials with a label and then the fact in sentence form. Like this:
Ideal Operating Conditions: Paper machines should run at 85-95 percent capacity for ideal operating conditions.
Instead of presenting facts in such a dry manner that presents information passively to your learners, try turning the tables so they're active participants in their training.
Here's Clark's example: "...show an illustration of two or three sales tickets and ask, "What three items must be included on all sales tickets?" (2)
And here's a different example: Show six rolls of paper towel--three rolls that pass QA test and three rolls that don't. Then ask the students to list 2-3 characteristics of acceptable paper towel rolls.
Because facts are somewhat random and the brain therefore processes them inefficiently, you'll want to provide lots of practice for using facts during your training.
Clark recommends four different methods of doing this:
You rarely or never want to train someone a fact for its own sake. For example, you wouldn't teach your learners what the bundler is just so they'll know. Instead, you teach them what they bundler so is they can go to the bundler and begin operating it at the start of their shift.
Or, to make the point more directly, you'll typically teach knowledge-based stuff like facts so that people can use those facts while performing some task on the job.
As a result, it's not so important to test your employees on the actual facts. Instead, test their ability to perform the skill or task that you want them to perform on the job. If they can do it, then they know the facts well enough.
Remember in some cases, it's easier to not train workers to remember a bunch of facts but instead to give them access to the facts through some form of job aid they can quickly reference where they need the information on the field, such as with the mobile training & job support app shown below.
One way to think of concepts is that they're nouns. Or, in other words, they're a set of things that share a number of critical characteristics. In Clark's example, she says that all chairs are intended for sitting and have a back, a seat, some form of support from the floor (3). In a more work-related example, all palletizers have a way to put an empty pallet into place, stack product onto that pallet, remove the pallet when it's full, and continue the cycle.
There are two types of concepts:
You're probably most likely to train people about concrete concepts. It's OK to train people on abstract concepts, but make sure you really know what you yourself mean (example: how exactly do you recognize "integrity"?).
In some cases, you'll want your employees to remember concepts, and in others, you'll want them to to apply those concepts. Let's see what we mean here:
Remembering a concept--employee can restate the key characteristics. For example, they could restate the three characteristics of a palletizer. However, that in itself doesn't mean they can identify a palletizer "in the field," if you will.
Apply a concept--employee can use the remember characteristics to identify the concept. For example, the employee can walk onto the work floor and identify the palletizers.
You typically won't train workers about concepts just so they can restate the key characteristics (meaning they "remember"). Instead, you'll want them to apply the concept. In some cases, that's the task they'll perform--like, identify defective products and remove them. In other cases, they'll need to identify one or more concepts in order to complete a procedure. For example, they may have to complete a procedure that involves five different tools or pieces of equipment, and as a result will need to know what each tool or equipment is and does.
Because you're most likely training workers about concepts because you want them to apply the concept, make sure your learning objective is some form of action: "identify defective paper rolls" or "use machine X, machine Y, and machine Z to perform Task A."
Clark recommends that you provide three things when teaching people about concepts (4). They are:
Analogies are an effective and helpful way to teach concepts. An analogy is something that's similar to but different than the concept. Clark gives an example of cutting up a pie into different-sized pieces to explain fractions of numbers. Analogies are helpful because they take something the learner is not familiar with and show how it's like something the learner is familiar with. As a result, analogies only work when they compare the new concept with something the learner already knows.
Like most all training, your learners will benefit from practice when they're learning a concept. Because you'll probably want them to be able to recognize when things "fit" or "don't fit" in a concept, you should set up scenarios in which they're given examples and non-examples of the concept and ask them to correctly identify each.
When you train employees about a process, you're teaching them how something works.
Some common types of processes that Clark describes are (5):
Employees can benefit from understanding processes for multiple reasons, and understanding how the employee can benefit can help you determine if they need a more superficial, high-level overview or an in-depth, detailed explanation.
Understanding a business process--understanding a business process can help your worker know why the steps he or she must perform are important and/or exactly what's important in each step (because they'll know how others later use that). In many cases, you can provide only a superficial overview of a business process--just enough so the person knows how their steps fit into the big picture.
Understanding a technical process--you might want to teach a person about an entire technical process so they'll know how the part they work on fits, which gives the employee a better chance of creating their part so it "fits in" well--the example that Clark gives in her book is of a computer programmer writing a piece of code that would be added to a larger code base. Another reason Clark mentions, and a key one in many industrial and manufacturing facilities, is that understanding how a process works is key for workers who have to keep that process operating within established productions goals and for others who are responsible for troubleshooting and fixing problems. Finally, having at least a superficial understanding of a work process at an industrial facility may improve overall morale.
You may want employees only to remember a process or know how to apply it.
If your goal is just to make the employee understand a process, then you can keep the training superficial and expect them only to be able to know or explain the process.
If your goal is to have them apply the concept, so their work fits into the overall product or so they can later troubleshoot a process, your training should teach them to apply (not just remember/restate) and you should assess your learners to use the knowledge of the process while applying the process (in troubleshooting, for example).
Clark provides the following tips for presenting a process during training with employees:
In some cases, it really won't be necessary to let your employees practice with their understanding of a process. If identifying the different steps of the process isn't something they'll need to do on the job, then don't bother setting up an opportunity for practice. For example, if you've explained a process just so they'll know how the paperwork they create is used by other coworkers in different departments later, there's no real need for practice.
In other cases, though, your employees WILL need to use their understanding of a process during their jobs. For example, if a maintenance worker has to troubleshoot a system to diagnose and fix a problem, he/she will have to use that process understanding to troubleshoot effectively. In that case, you should set up practice scenarios that allow the employee to practice using the process information to perform the troubleshooting (or whatever else they'd do on the job). Don't just have them list the steps of the process. (You'll read more about troubleshooting later in this article.)
The same points we just made about practice for concepts applies to evaluating employees' understanding of processes as well. So, if you want your employees to have a superficial, overview-level understanding of a process just so they understand how their work "fits in," you probably shouldn't evaluate them on the process. But, if you do have to evaluate them because they'll have to use their understanding of the process on the job, then don't just ask them to list the steps or explain the process, but evaluate them on their ability to perform the task(s) that requires them to understand the process (like evaluate them on troubleshooting exercises).
A procedure is a simple list of task of steps that a worker must complete.
It can be a little tricky to correctly identify all the steps of a procedure before you teach the procedure to employees. If you're not an expert on the procedure, this may be because you don't know the procedure yourself. If that's the case, talk with people who know the procedure well, and have them help you identify the steps. It can also be helpful to watch someone performing the procedure in the field, or to video tape them, so you can observe what they're doing.
Be careful if you're trying to learn the steps of a procedure from an expert performer. In many cases, experts like this know a procedure so well that parts of it become "automatic" to them. This means when they tell you the different steps, they may leave some out. Again, here's where watching in the field or videotaping can help.
When you're identifying the steps of a procedure, keep in mind the type of employees you will be training and their related knowledge. In some cases, something that's only a single "step" for an experienced worker will have to be presented as multiple steps for workers who are entirely new to the material. Clark gives a good example of logging on to a computer. For a worker who's familiar with computers, that's a simple step in a procedure. But for workers who aren't familiar with computers, that's multiple steps (turn on, press Ctrl-Alt-Del, enter username/password, etc.).
While identifying the steps of a procedure, you'll notice they may be of two types:
Make sure you know what type of procedure you've got--linear or branching--before you teach it to employees.
Remember that for job training, your goal isn't normally to have your workers be able to state the steps of a procedure. Instead, you want them to be able to perform the steps on the job. As a result, whenever possible, provide a job aid that explains the steps of the procedure and let them use that job aid during training and even in the field.
Clark explains that teaching your workers to perform procedures should include the following:
As is true with most of the other content types we've talked about (facts are the exception here), your employees can both know and be able to perform a procedure. Knowing means they can list the steps. Being able to perform means they can actually complete the procedure. In almost every case, what's important on the job is if the employees can perform the procedure.
As a result, you'll typically want to create assessments that evaluate if your workers can perform a procedure, not just list the steps.
It may help to take a moment to remind ourselves of the difference between a procedure, which we just learned about, and a principle, which we're about to learn about.
When you train a worker to perform a procedure, you're teaching them to perform a series of steps in the exact same order every time. The example that Clark gives is a cook at a fast-food restaurant who must prepare a burger the same way every time. Experts in learning and development sometimes refer to procedures as near-transfer tasks.
By contrast, when you're training a worker to apply a principle, things aren't going to be the same every time. You want your employee to follow or apply a set of guidelines to apply principles in a number of different circumstances, each of which will be different from the others. There will be no set order or exact duplication of steps. The example Clark gives is a master chef using the rules learned in culinary school to make an entirely different delicious dinner special night after night after night. Another example would be training a salesperson to apply principles to interact with a customer and close a deal--again, the situation will be different every time, and the sales person will have to think on his or her feet and do what's necessary at each moment to apply the principles within the set of guidelines. Experts in learning and development sometimes call principles far-transfer tasks.
What you'll be working with during this kind of training are:
It's harder, more time consuming, and generally takes more money to train people to follow guidelines and apply principles in shifting, dynamic situations on the job. That doesn't mean we shouldn't try to do it-ask any sales manager who's seen sales increase as a result of sales training. But it does mean we should make sure the principles we're trying to train are valid.
In short, don't waste a lot of time and money on training if the ideas you're pushing are half-baked or inaccurate.
To that point, Clark recommends checking professional literature and observing experts in the field to identify principles and guidelines.
As with the other types of training mentioned above, employees can either remember or apply guidelines and principles. But in most every case, because you want them to apply the principles on the job, you should write learning objectives that require them to apply the principles, provide training for application of the principles, and assess your employees' learning by evaluating their application of the principles. In general, you shouldn't be satisfied with whether or not they can restate the principles and guidelines.
When training your workers to apply principles within a set of guidelines, your training should include:
Provide demonstrations/examples of the guidelines being applied in different scenarios (make sure to provide these demonstrations within a realistic, work-like environment-as close to the conditions the employee will experience on the job as possible)
Ask your employees questions about what they see in your different example scenarios, including:
To discuss training employees to troubleshoot, we'll rely more heavily on the Foshay/Silber/Stelnicki book, because Clark doesn't give a chapter to it like she does the other types of learning.
However, before we begin, let's review a few things Clark does say about troubleshooting in her book:
Given what we've explained above, here are tips from Foshay/Silber/Stelnicki to teach workers to be more effective troubleshooters. These tips are for troubleshooting a particular system, but learning to troubleshoot well in general is a skill that can later be applied to other systems:
x
There you have it. By now, hopefully, you've seen that you train people at work on more than just "stuff at work." Instead, you train them on different types of materials, and these include facts, concepts, processes, procedures, principles, and troubleshooting. And, you've now seen that you can tailor your training methods to help your workers master these different types of materials more effectively.
1. Clark, Developing Technical Training, 106.
2. Clark, , 117.
3. Clark, , 82.
4. Clark, , 86.
5. Clark, , 126.
6. Clark, , 60.
7. Clark, 127.
8. Foshay/Silber/Stelnicki, Writing Training Materials that Work, pp. 153, 130-135.
