process

Find the root cause and you’ll really make the problem go away.

On March 14, 1757, the British admiral, John Byng, was executed by firing squad for failing to win a battle against the French Navy in the 7 Years War. It turned out that his punishment was unfair, he had lost the battle because his ships were in a poor state of repair, the result of logistics issues.

Portrait of Admiral John Byng by Thomas Hudson, 1749

Portrait of Admiral John Byng by Thomas Hudson, 1749

It’s not uncommon for some contact center managers to adopt a similar principle for resolving issues. An employee is found, made responsible and dismissed. The unfortunate employee is not always the cause of the problem.

In the name of both fairness and effective problem solving, other methods of investigating issues have been developed. A common practice in industrial quality management is root cause analysis. The principle behind this is that the cause of an issue is likely to be a process rather than an individual. There are many techniques, but two can be easily applied to the world of contact centers.

The first is to create a detailed timeline of the events leading up to the issue. Where issues are related to calls or customers, the specific calls can be identified easily and played back to see what was actually said to the customer. At this point it makes sense to look back at training materials and coaching records. This may contain clues to explain aspects of agents’ behavior that contributed to the problem.

The second technique is often called the “5 Whys” technique. Let’s imagine a case where a number of agents have knowingly registered an outbound sales call as being a sale, even though the customer made no commitment. The first “why” would be asked of the agents: “Why did you register the call as a sale when you knew it wasn’t?” The agent’s answer might well be: “To get the commission.” The second “why” might seem obvious, but it serves a purpose: “Why did you risk losing your job to get the commission?” The agents might well answer: “Because we don’t get paid a basic salary.”

The third question might then be to the contact center management: “Why don’t you pay the agents a basic salary?” The contact center management might answer: “Because we have a risk and reward contract with the client.”

The fourth question would then be to the senior management: “Why did you agree to a risk and reward contract with the client?” The answer to this might well be: “The client told us this is what they were offering, it was a “take it or leave it” situation.”

The fifth question at this point would be: “Why did you take on a contract at such disadvantageous terms?” The answer might then be: “Because we needed the work.”

The fundamental root cause of the issue is the risk and reward contract the contact center agreed with the client. This cannot be changed at short notice, if at all. What can be addressed is the fact that the agents don’t get paid a basic salary. They have no incentive to be honest. Failing to sell will have the same result for them as being dismissed from the company, a loss of income.

There is no doubt in this case that the agents should be dismissed. They deceived their employer in order to get paid. To reduce the chance of the issue recurring however, the organization would be wise to look into how their agents are paid.

Next time you face an issue in your contact center, it might be worth finding out the root cause before dismissing someone.

Bookmark and Share

Does anyone like writing down processes?

Contact centers are process driven environments, yet frequently, documenting processes is one of those jobs that has to be done, no-one wants to do it and everyone has an opinion about it when someone else does it. It’s also a job that needs to be done slowly and carefully, but is usually requested at the last minute. So what is the fastest way to document a process at a fairly high level while retaining enough information to make it useful?

One approach is called the SIPOC chart. This is an acronym that translates into “Supplier, Input, Process, Output, Customer.” The basic principle is to create a chart with each of these five headings.

Sample SIPOC

Sample SIPOC chart showing inbound call process

It’s best to start with the process itself, which can be expressed as a series of events in bullet points (a maximum of 10 for very high level overview). On the left hand side, we then complete the inputs column. This contains everything that the process requires to run. To the left of this column, we complete the suppliers column. This contains the names of the people and organizations that supply these inputs. On the right hand side of the process column, we fill in the outputs which the process produces. This should include not only the final product, but any documentation or data produced and also any by products. To the right of this, we have the customer column. here we fill in the names of the people and organizations that receive these products.

In one document, you will not only have a simplified account of the steps of the process itself, but you will have identified many of the drivers and products of the process and the people who affect and will be affected by the process.

This is a very high level approach. Engineers, analysts and computer programmers will need something that is a lot more detailed. In this case, the SIPOC chart would be a starting point to generate the questions and discussions needed to describe a process in more detail.

One mistake many people make in documenting processes is to mix what the boss would like to happen with what really happens. If you are planning to improve an existing process, it is essential that you document the process “as is”, talking to the people who are the closest to the process as it happens. Doing anything else is like treating a sick person in hospital without knowing what he is suffering from.

Any document is only as good as the information it contains, so consider your sources carefully, and you will write a more accurate and therefore more useful document.

Bookmark and Share