Morgan handed me a stack of the files which contained copies of previous performance reviews.

“I see here that you are using a 1-5 scale with 1 = poor and 5 = exceeds expectations.” Morgan nodded. I continued, “Scanning down the list, I see that you have tons of 3s and only an occasional 2 or a 4, never a 1 or a 5.”

“That’s easy to understand,” said Morgan. “We don’t have to explain a score of 3. If we rate a 2 or a 4, we have to provide a written explanation. And even if someone deserves a 5, we never give it, because then they might ask for a raise.”

“And, tell me again, what is the purpose of this review?”

“Well, our HR person says that if we have to fire someone, we need to have a bunch of 1s and 2s in the file. Something about avoiding wrongful termination.”

“Morgan, have you ever been up against a labor attorney in court?”

“Not really,” Morgan replied.

“Morgan, have you ever had to explain to an attorney exactly what a 2 means?”

“Not really.”

“Morgan, with all due respect, this little form is not going to get you very far in a wrongful termination suit. There has to be a better purpose for this performance review process.” -TF

I let Morgan puzzle for a while. I had just questioned the Holy Grail of management processes, the annual performance review.

Finally, I broke the silence. “Tell, me, do you really look forward to this annual tennis match all based around this form you bought at the office supply store?”

Morgan had begrudgingly conducted performance reviews for 15 years. He had never considered that this process might be counter-productive to performance.

“Not really,” he replied. “I just thought it came with the territory of being a manager.”

“You are right, it does come with the territory, but I want you to think about a whole new way of conducting this conversation.” -TF

“I can’t believe this list. Look at this. I have 14 performance reviews I have to conduct in the next three weeks. And I just used the last form off of the pad this morning, so I have to send someone out to the office supply store to pick up some more. I wonder if all this is worth it?” lamented Morgan.

“What would Dr. Deming say?” I continued, answering my own question, “I believe Dr. Deming would say, NO. In his research related to TQM, he found no real correlation between performance reviews and productivity. Sometimes, I wonder if performance reviews don’t work against the intentions of a performance feedback loop.”

Morgan was puzzled. The last thing he thought he would hear from me was that I might question the entire performance review process. -TF

“Let me see the projects that you put in for review,” I said, as Sean handed over the list. I scanned down the page, “I see you selected six, tell me, how did you decide which ones for the group to do a post mortem on?”

Each quarter, Sean’s team spent four hours going over significant projects for the quarter, looking for lessons learned. “Oh, that was easy,” Sean replied, “these were the eight biggest money losers.”

It is always tempting to debrief a project where things have gone wrong. Once you have corrected all those problems, where are you? My guess is, you are back to even steven. No loss, no gain, no harm, no foul.

If you really want to make progress, you also have to analyze where things went right. Pick two or three winning projects to debrief. Find out why you were able to make significant margins. Where was the advantage in those projects? Where can you find more projects like those? -TF

“We seem to get so many customer complaints that I feel like I am just putting out fires all day. I am afraid to take time off. Thank goodness we shut the phones down on Sunday,” lamented Bryan.

The reason we create customer service departments is to deal with customer complaints. If you are in business, you will get complaints from customers.

Have everyone in the customer service department meet ten minutes early and make a list of all the complaints from the day before. Next, from the customer perspective, rank them from bad to worse.

1. The delivery was ten minutes late.
2. The delivery was one hour late.
3. The delivery was two hours late.
4. The delivery never arrived.
5. The wrong item was delivered and customer had to return item.
6. The item was delivered damaged and the customer had to file a claim.

The next day, repeat the process and co-mingle the priorities from bad to worse. The pattern created is what Michael Basch (former Federal Express guy) calls the “Hierarchy of Horrors.” With this patterned list, you can now systematically make improvements in the areas that require the most attention. This list is valuable for management meetings where other departments might be able to help.

Make your list. What is your customer’s “Hierarchy of Horrors?” -TF

“I told him he needed to pay more attention to the quality of his work.” Henry was describing a conversation from the day before. “He actually started yelling back at me, right there in front of everyone. We weren’t toe to toe, but we were close.”

At some time, with some people, it doesn’t take much to make that person feel like they have their back against the wall. Here is the bad news. When someone feels that way, they have only three choices, none of which are positive. Fight, flight or paralysis.

As a manager, you still have to provide corrective feedback, but you have to find a different way. Here is one. Talk about your own mistakes first. At some time, in your work experience, you made a similar mistake or created a similar quality problem. Talking about your own mistake first, allows you to explore the details of how and why. This approach should open the other person to talk more about what may be causing their own underperformance. This underlying cause is the issue that has to be resolved for the work quality to improve.

Talk about your own mistakes first. -TF

Susan was adamant, “My people do not like role playing.” We had been discussing a training program for her team of Customer Service Reps. She had a litany of reasons. “It makes them freeze up. They are uncomfortable. They would rather be poked in the eye with a sharp stick.”

She continued to describe a typical scene in the conference room where unprepared team members are met with a slick trainer, intent upon mild embarrassment.

“I agree with you,” I responded. “I would hate that, besides, I don’t think anyone learns anything valuable. Let’s try role playing in a different way.”

The major benefit of role playing is having team members practice predictable scripts and behaviors so they can consistently repeat them in real life. This means role players should be completely prepared knowing exactly what to say, following a pre-determined script or checklist. The point is to have them practice the words you want them to say, over and over.

Most role play scenes should be short, 90 seconds or less. They should have a very specific objective and create repetition. I don’t want participants to be cute or funny. I don’t want them to think on their feet. I want them to respond in a way that has been proven (by testing) to be effective. I want them to solve problems by the book and make sales with predictability. -TF

“If it doesn’t show on the screen, it is wasted effort.” I grew up in the television production business and that one principle helped us make the most important decisions. If the element did not make a visual impact on the screen, we passed on it.

What does this mean for your team? What defines your “tv screen?” I will lay odds that your “tv screen” is defined by your customer. If your customer does not value your “value added” service, then stop doing it.

How do you know when your customer values your “value added” service? You know, when your customer is willing to pay for it. If it doesn’t show on the screen, it is wasted effort. -TF