Posted by: Dr. Barb, aka Dr. Barbara Austin
Congratulations! Your call center has terrific new-hire training using online procedures to help them learn their jobs. So why aren’t they using the procedures? Even worse, why do your experienced CSRs tell the new ones not to even bother with the published procedures?
We spend a ton of money training new hires on online operational procedures. I once overheard an experienced rep tell a new hire, “Forget what you learned in that class, I’ll teach you what you need to know.” I could have screamed. Why would the experienced rep tell a new person this?
DR. BARB’S ADVICE
Procedures housed on an online reference (OLR) system can be very powerful performance and training tools, IF the user has confidence in the OLR. Your experienced rep may be telling the new hire that something is wrong with the procedures or the system doesn’t work well. Let’s investigate your procedures.
Are the procedures correct?
Without question, the biggest reason CSRs fail to use online procedures is a lack of confidence in the accuracy of the procedure. For example, the CSR searches the OLR for a procedure. The search results in out-dated or inaccurate information. Just a few of these instances will guarantee that your CSRs will find alternative methods to locate information. Bad procedures on your OLR are the death knell for continued use. Generally these bad procedures are on your system for several reasons.
Old, out-dated procedures were uploaded just to have a procedure online – better to have something than nothing – right? In this case, having something, i.e., bad procedures, is worse than having nothing because users won’t waste their time searching for procedures they can’t use. No confidence = no search.
Someone has written the procedure without using a systematic subject matter expert (SME) review process. The procedure lacks “best-practice” perspective if only one person writes and reviews it. Also, the user does not buy in to the value of the OLR because they weren’t involved in the development process. Procedures are rapidly changing, and rewrites are not keeping up. Now we’re back to the out-dated dilemma.
30,000 feet or ground level?
Six Sigma’s horizontal flowcharts turned into procedures depict a systematic flow of tasks, not steps within a task. While these maps are very valuable for evaluating overall processes, these flowcharts add extraneous information to procedures, such as which database information flows through. Frankly, users don’t care. CSRs need accurate, step-by-step procedures to complete the task at their level. They want to know which screen to use and what information to input. High-level flowcharts are useful for managers to view the overall flow of tasks, but procedures must be written with users’ needs in mind.
I'm a proponent of Lean over Six Sigma, but more about that in a later blog.