Wednesday, August 31, 2011

Training - The Panacea to Organisation Pain? Part 1

“Members in the Communications Team write poorly. We are getting many angry customers ringing us to complain about the emails they are receiving from us. Can you organise a training session for the Communications Team?”

“We are giving far too much money away as compensation. Can you put a training programme to teach our staff how to negotiate better over the phone with customers?”

“Our customer service level has gone from back to worse. I think we need a training session to get our guys back on track.”

Most people think training is the panacea to all organisational problems. Of course, this is never the furthest from the truth.

The above comments were requests that I received when I was doing training. The easiest, and probably, the most painless and least heartache way to accept the diagnosis of issues by the line managers and design the training programmes. But that would effectively reduce the training professional into a ‘post-box’ function; very scary. Years ago, when I was attending a workshop at the American Society of Training & Development’s annual conference, a couple, Dana and James Robinson, challenged me to move beyond merely being a Training Professional to that of a Performance Consultant. They articulated convincingly that most perceived training problems were actually performance issues that needed attention. 

There is never a single cause to a problem. It is always easy to blame the people doing the job. Or attribute it to their lack of training. In the first instance involving a bunch of communication staff members, I took some time to visit the team and understand their issues. This was what I found. The staff members were originally working in the frontline answering phones. However, because they were turning customers off through their rude replies, Management, for good measure, decided to move them to some backend job, in this case, answering letters from customers. The only problem was that while, in theory, the staff members were now not talking to customers, they were still interacting with them. And they were writing how they were answering over the phones. 

The big issue lied in the fact that when a customer wrote, s/he was likely to be extremely upset. Now you can well imagine the explosive combination of customer’s frustration and staff member’s rudeness! It was not funny.

What if we have gone down the communication route and train the staff to reply politely? Would that have worked?


Whenever there is a problem, there are many possible causes. ‘People’ is but one of the elements. Ishikawa-san, the creator of the Root Cause Analysis diagram, simplified possible causes to four main elements, all beginning with the letter ‘M’; that of Man, Method, Material, and Machine.

Only when we satisfy ourselves that ‘Man’ or ‘People’ is the root cause, should we consider ‘training’ as a real option. The next challenge is to understand what exactly is ‘wrong’ with our people. Here is where we tap a doyen of educational psychology, B S Bloom.


When looking at a ‘People’ issue, Bloom further sub-categorised that into the elements of Knowledge, Attitude, and Skill as seen below:
  • Knowledge can either be cognitive or mental;
  • Attitude is generally considered the emotional element;
  • Skill is generally the psychomotor or physical elements.

For example, why are our staff members having a problem? Is it a ‘Knowledge’ issue? An ‘Attitude’ challenge? Or a ‘Skill’ gap?

To illustrate, let me demonstrate with a real case. The problem relates to the Faults’ Department of a telephone company. Just like in my various cases, I was approached to investigate as the Faults Department’s frontline telephonists were perceived to be giving poor services based on the number of complaints going to Management. “We need a training programme,” barked Ron Saxby, the General Manager of the Centre. 

As usual, the first action I took was to visit the place, observe, and talk to the staff. Here is what I gathered in terms of my observations based on ‘needs’:
  • The Faults’ Department had 150 staff consisting of both new and ‘old’; the ‘older’ ones had been around for a long time,
  • Over time, the staff members had been given many different forms of training. Business rules and processes had changed but adoption had not been streamlined,
  • Staff tended to keep their notes after induction,
  • There were inconsistent practices across the department since different batches of staff members were trained differently (regarding rules and processes),
  • Some staff members were unfamiliar with how to read an NTS chart (NTS chart is a tool to help staff members to know whether there is a problem on the telephone line. For example, staff members were unfamiliar in reading ohms, kilo-ohms and mega ohms. These were critical concepts,
  • Some staff members did not know what key diagnostic questions to ask when conversing with the customer (What noise do you hear when making calls? When receiving incoming calls?),
  • There were different NTS reading guidelines given over time. Different staff members have different versions,
  • Some staff members were unfamiliar with what and when to tell the customer at the end of the conversation regarding access and technician diagnostic charges (These were important conversations),
  • Some staff members did not put in sufficient information into their end notes. As a result, technicians did not understand what they need to do when they received a work ticket.
Now, you might like to pause here for five minutes and try and offer some solutions. When you have done that, please carry on.

Here is what I did next. I distinguished these observations into Bloom’s elements of Knowledge, Skill or Attitude so that I could devise a set of learning objectives for creating our training modules.

Here is my attempt at asking the ‘why’ question and analysing these statements. I have used red’ to represent ‘Knowledge’, green’ to explain ‘Skill’, and blue’ to indicate ‘Attitude’.

  1. The Faults’ Department had 150 staff consisting of both new and ‘old’ staff members; the ‘older’ ones had been around for a long time – possibly an ‘Attitude’ issue,
  2. Over time, the staff members had been given many different forms of training. Business rules and processes had changed but adoption had not been streamlined,
  3. Staff tended to keep their notes after induction,
  4. There were inconsistent practices across the department since different batches of staff members were trained differently (regarding rules and processes) – You might like to note that this was a System issue as well. It demonstrated that the Department lacked a single source of truth and people were using whatever information that they were taught,
  5. Some staff members were unfamiliar with how to read an NTS chart (NTS chart is a tool to help staff members to know whether there is a problem on the telephone line. For example, staff members were unfamiliar in reading ohms, kilo-ohms and mega ohms. These were critical concepts,
  6. Some staff members did not know what key diagnostic questions to ask when conversing with the customer (What noise do you hear when making calls? When receiving incoming calls?),
  7. There were different NTS reading guidelines given over time. Different staff members have different versions,
  8. Some staff members were unfamiliar with what and when to tell the customer at the end of the conversation regarding access and technician diagnostic charges (These were important conversations),
  9. Some staff members did not put in sufficient information into their end notes. As a result, technicians did not understand what they need to do when they received a work ticket.
From a problem-solving perspective, Points #2 to #4, #7 – Multiple Sources of Truth – had to be arrested quickly. So, one of the first solutions immediately agreed by Ron was to create a new up-to-date and accurate knowledge base (Single Source of Truth) in the intranet (how we create the knowledge is another story for different time) while getting rid of all existing ones post-training; the latter was vital as it eliminated confusion, information mistreatment and different versions of truth.

BS Bloom also created a ‘Learning Taxonomy’, affectionately called the ‘Bloom’s Taxonomy’ to help us create learning objectives. He classified them from ‘Basic’ to ‘Complex’. For example, under ‘Knowledge’, the most basic level was ‘Recalling Data’ with the ability to ‘Evaluate Data’ being the most complex level. In effect, it is saying that the greater the ability of a staff member to answer the ‘Why’ question, the greater the achievement in a ‘Knowledge’ learning outcome since to ‘evaluate’ will mean that the learner will have to know why the data is there in the first place.

The BS Bloom’s Taxonomy of Learning is found here:


Now we are ready to design a set of learning objectives to meet our observed needs as follows:
By the END of the Training, staff members of Faults should be able to:
   Understand all critical concepts including ohms, kilo-ohms, and mega-ohms (Knowledge – Comprehension),
   Apply the relevant physical diagnostic questions to the Customer (Knowledge – Application),
   Study a NTS’ Parameter Table and evaluate the data before coming to a conclusion with regards to the status of the telephone line (Knowledge – Evaluation),
   Complete a Ticket with all relevant fields (Knowledge – Application),
   Internalize the importance of completing a Ticket with all relevant information (Attitude – Internalization),
   Develop consistent practice to ensure that we have covered the relevant information of Access (Gaining Access into the house), Diagnostic Conversation, and Commit Time (Time when the technician finishes the job) (Skills – Precision).
Most training professionals would be happy to get to this stage as training outcomes get articulated. However, there is yet another level that we can progress further and here is where we have to turn to another well regarded expert, Donald Kirkpatrick

Dr. Kirkpatrick came up with a way of evaluating training successes at 4 levels in 1959. The four levels of Kirkpatrick's evaluation model essentially measure:
  1. Reaction of student - what they thought and felt about the training, or you may term this as a ‘Happy Sheet’ evaluation,
  2. Learning - the resulting increase in knowledge or capability. Most times, a test can determine this element,
  3. Behaviour - extent of behaviour and capability improvement and implementation/application
  4. Results - the effects on the business or environment resulting from the trainee's performance. Sometimes, you may be able to include ROI (Return of Investment) into the mix, something that accountants love.
If we combined Bloom's approach and Kirkpatrick's targets, then we can truly design a training programme while effectively measuring our results.
Coming back to our example at Faults, we can include in the following goals:
  • Reduce rework by xx%
Conceptually, I have provided a way of helping you to understand that training is only a solution if it is a ‘People’ issue. Also, in identifying a training programme, it is critical to understand the issues around Knowledge, Attitude and Skills. Once you have this information, you are ready to design the training programme. Here is a model that you might like to use:


So far, I have only explained the ‘Green’ rectangle as well the ‘Yellow’ triangle. In another article, I will expand on the ‘Blue’ triangle.

For now, let me return to the story of the communication department. How can we help these staff members who could not write politely? It is true that this was a staff issue. However, the solution that we adopted was a very non-staff one. We identified the typical type of letters coming through and we developed company endorsed templates for these staff members to cut and paste, thus removing the need for them to be wordsmith.

From a purist perspective, this looked like an attitude issue relating to the staff that we can perhaps train. But ‘Attitude’ or ‘Mind-set’ is really the toughest thing to train. Hence, for a failed safe solution, templates were considered more predictable and better managed.

Hopefully, you would have by now picked up that training is not a panacea of all pain, including the ones involving the ‘People’ factor. Even if training is favoured, the toughest programmes are those that involved mind-set shift. The next article on ‘Design and Development’ will demonstrate more. Happy reading.

Wednesday, August 24, 2011

What are Business Rules?

“Rules are guidelines to the wise and obedience to the fools.”
                                                                                                          – Derek Powell

Nobody likes rules, especially so in New Zealand. Not least even me – after all, I left a country that is enchanted with rules (Singapore) and moved to one that detest any. Let me relate two incidents of how ‘business rules’ came into my world.

The Case of Xtra
Many years back, I was with the NZ Telecom Xtra contact centre offering internet support services to the public. At that point in time, Xtra was just starting up its broadband support. The team consisted of a diverse group of individuals who were keen to provide excellent service.

There was an inherent problem with providing services of the computer nature – computer technology was changing at an astronomical speed; people were upgrading from Win 95 to Win 98 and then to Win XP. Some were using Apple computers. However, when Xtra was training the frontline staff, it could not even catch up with the speed of change.

So, the ‘older’ staff members (the longer serving ones) were trained in Win 95 and Win 98. They were brought in to upgrade their knowledge in Win XP. Newer staff members were trained in Win XP as it was the most popular model. Then, we would spend an extra two days to skill people in Apple.


When a customer with a Win 95 problem rang and was dealt with by an ‘older’ member, the person could walk the customer through the entire issue. But if the customer rang and spoke with a ‘newer’ member, s/he was simply flicked away with a “Sorry, we cannot help you. Why don’t you upgrade to a …..” This resulted in inconsistent service level. And customers started to complain.

As a process, they knew how to resolve the problem. But what should they support? Everything? Ever expanding technological systems – Win 95, Win 98, Win XP, Win 2000 …. The list went on.
Here is where rules became critical. And this is where my journey started.

Driving on the Road
Ever been to Waiheke Island (An island off Waiheke where the ‘rich and famous’ resides)? Well, I did although I have to admit that it had been some years since I did.

I was told that Waiheke Island had one traffic light and it was meant to distinguish a JAFA (an uncomplimentary term for an Aucklander) and a Waihekian. You see, that traffic light actually does not work but a JAFA will stop there J


Now, if we are in Auckland, we cannot live without traffic lights. Because it would be an utter chaos as you can well imagine. Why? Because of the sheer size of our population of 1.4 million people.


Think of Business Rules as a set of highway road codes with ‘how to drive’ as the process. That is what it really is.


Xtra - Continued
Xtra was growing bigger. Everyone wanted to provide good customer service. But everyone had their own view of what good service ought to be. The result? A confusing delivery of service.
The issue was not one of ‘good service’ as defined by each person’s definition. It was one of ‘consistent service’ as a company, a Telecom standard; one that Telecom could live with and that the customer would not mind.

We got together and went through some analysis and, using statistics, we knew what percentage of customers had Win XP, 98, and 95. Using that statistics, we decided that as a company, we would only support Win XP and 98 for that point in time and not Win 95. When we studied the stats more intensely, we realised that there was only a small percentage (actually a very, very small percentage of the population) with Apple although these customers were what was termed as ‘early adopters’, people that we might not be able to ‘offend’ as they could influence the larger market.


Hence, we took the following actions:

  • Established a business rule for the contact centre only to support Win XP and 98 so that customers could have reliable and consistent service (a Telecom standard),
  • Continued to support Win 95 but not via the phone. We directed such customers onto the Telecom website as well as mailing out instructions (if they were ‘stuck’ with no internet support)
  • Created a specialised team to deal with Apple issues and stripped the two-day training out from the original induction module.
  • Establish a set of business rules to ensure consistency of behaviour across the Department.
  • Change-managed the contact centre members to accept the concept of business rules through a fun-and-game storytelling using the concept of highway road code as well as getting them to complete a test online. NOTE: Explaining the ‘why’ was critical as well.
  • Quality checked members based on phone conversations (Telecom had a quality control centre and listened in to all phone calls, scored and feedback to all staff during their one-on-one).
The end result was that 200 staff members adopted this stance. The initial response from the customers were some degree of frustration but, over time, customers understood and they were getting consistent responses from every staff on the centre. The customer engagement score went up.

That became the start of business rules across Telecom which is now the established norm.


The Story of the PAC Team
The People Advisory Centre Team of a bank had quite similar issues. The PAC team had to work with the hiring TAT (Talent Acquisition Team) team. There was lack of clarity in regard to what the PAC and TAT teams could support.
For example:  who is an employee – A permanent staff? A contract staff? What about a ‘Forced Rehire’?

Both sides had different views of the same things. It was like two persons looking at an elephant from a different angle. So, they were great misunderstanding. That became a real struggle.


As a result, a document was created to establish clarity in regard to definitions and also when did work start for PAC and end with TAT. We created an initial 11 rules for the latter and here is Rule #3:

All key information found in the RFA (Requisition for Agreement) must be completed correctly by TAT. Emails to PAC to request for inclusion into the incomplete RFA will not be accepted.
Does it sound like a procedure? If we say, “emails to PAC to request for inclusion into the incomplete RFA will not be accepted”, then it becomes a rule. It is to make the obvious even more obvious. Nonetheless, before we implemented, we made sure that there was maximum involvement on both sides to engage the teams so that we could change-managed these without any difficulties.

The best change management is when change occurred without staff members even realising (because it was ‘their’ idea after all). Involvement was the crux in the PAC-TAT success. Now, staff members worked well without even knowing the background to the alignment attempt.


What is Business Rules?
In the classical article, Defining Business Rules – What Are They Really, by the Business Rules Group (this article was created by a diverse group of professionals including a few IBM staff members , rules are divided into four main categories as follows:
  • Definitions,
  • Facts relating terms to each other,
  • Constraints, and
  • Derivations.
Definitions would be simple enough because it ensures that both sides talk the same language.
Let us look at a car rental company.
Business Rule “Fact” –
  • A rental class is composed of car models.
  • A car model (e.g. Honda Civic) is in the Class C category.
  • Cars can only be rented out in a legal, roadworthy condition to our customers.
Business Rule “Constraint” –
  • “If any lights are not working, the bulbs should be replaced. If tires are worn, they should be replaced.” – constrained by the need to rent out in a ‘legal, roadworthy condition to our customers.”
Business Rule “Derivations” –
  • “Rental charge is based on base rental price, optional insurances and refuelling charge.” i.e. Rental charge = Base rental price + Optional insurances + Refuelling charge.

Business Rules and Procedures
Now, business rules are NOT procedures. ‘Procedures’ tells you how to do your work. ‘Business Rules’ tells you what is acceptable while you are doing your work, i.e. what is our standard.

Nobody likes rules but because we are working for a company, we need these “rules” to bring about consistent behaviour so that our customers can enjoy a reliable service, i.e. same service everywhere. For example, can you imagine McDonald serving a different Big Mac in different outlets?


Franchisors are especially stringent on rules and they audit each outlet and their suppliers based on them because they know that these ‘rules’ represented the concept of ‘quality’ to their customers. I know because I worked for a McDonald’s supplier. Believe me, McDonald was not very forgiving when we failed their ‘quality rules’.


Staff members are then trained according to these ‘rules’ because that is the ‘McDonald’s Way’ or the ‘Disney Way’; because that is how we do things around here. Disney is as strict as anyone that I can think of.


OK, we don’t need rules down to the fine detail but we need to tell people what we expect. At the end of the day, it is managing the expectations of our internal customers so that we can manage the expectations of our external customers so that we can have consistent service.

While ‘rules’ are a must for technologists as they put up programmes so that computers know what and how to interpret situations, they should not be ruled out for us too. Even just basic things like ‘definitions’ will shape our ability to communicate better.

Rules are NOT STATIC
“Rules” are, of course, not static. What is ‘the rule’ today can change tomorrow based on the changing needs of customers.

Hence, I can partially agree with Derek Powell’s statement: “Rules are guidelines to the wise and obedience to the fools”.


If they are good guidelines, then the wise must follow. But if they are not good, then the wise must question and make them better. There is a time for everything, “Time to follow and time to question.”


Hope I have clarified why I am so passionate about this simple topic re ‘Business Rules’.