Tag Archives: decision making

Good and Bad Advice

Who do you listen to for advice? There is good advice and bad advice. Some advice leads to abject failure, some advice leads to success. What is the difference?

Between failure and success is average. What advice leads to average success? Action that leads to high performance is different than action that leads you to average performance.

If you know the difference between good advice and bad advice, maybe you don’t need advice at all. Perhaps you need an analytical process that allows you to truly understand the problem, to understand the drivers of the problem. Part of analysis is to determine what you want, what the best outcome could be. In the middle is the collection of alternatives. And somewhere in there is the best alternative, one that avoids the contributors to failure and opens a pathway to a reasonable chance of success.

Accountability and Authority

I made sly reference to these two concepts last week. Accountability and authority. These are inseparable.

To be accountable for an output, one must have the authority to determine the variables around that output. Do not hamstring a team member by handing them accountability without the authority to control variables. Bifurcating the two leads to well articulated excuses and blaming behavior.

Simultaneously, do not give someone the authority to control variables without the concomitant accountability. Government oversight committees are famous for wanting to have all the authority without accountability.

These two concepts go hand in glove, not either-or, but AND-and.

Focused

“You are right,” Byron continued. “The things that hurt us now, are decisions we made a couple of years ago when times were good. It seemed like a good idea at the time. We didn’t think very hard about some of our bone-headed moves.”

“And, now?” I asked.

“And, now we have to get lean. Maybe really lean. It may get worse. We have to be able to take a couple more punches and still be able to maneuver, be able to take advantage of opportunities, but it’s difficult.”

“What is so difficult about it?”

“Well, now, everything has to be focused on a result. If it doesn’t produce a result, it has to go. It’s not pleasant. In many cases, we have to learn to say NO! In the past, we tried to figure out what TO do. Now we have to make decisions on what NOT to do.”

It’s Not About the Button

Vicki was stumped.

“Your team member is in the break room, having a soda, thinking about a problem in his work area that needs to be solved,” I repeated. “Would you call that work?”

“I want to say no,” Vicki struggled. “He is not at his work station working, so he can’t be working. I know, he is not being productive, so even though he is thinking, he is not being productive, so he is not working.”

“And if he does not solve this problem he is thinking about, his productivity will stop,” I continued.

“You want me to say yes, he is working, but it feels like no,” Vicki insisted.

“Vicki, do you pay your machine operator to move a piece of metal into position and to press a button to cut the metal? Because, if that was it, you could hire a robot. Or do you pay your machinist for his judgment of how raw materials are organized to enter the work area, the cleanliness of the scrap produced by the machine, the attention paid to the preventive maintenance to keep the machine operating?”

Vicki finally responded in a long slow sentence. “I pay him for his ability to solve problems and make decisions, not to push the button.”

Arms Folded Behind My Head

“Perhaps we should define the word, work. That might help us better understand why people need to work. What is work?” I asked.

“This is going to be a trick question,” Vicki replied.

I nodded. I had known Vicki for a couple of years. She was used to my trick questions. “It’s only a trick question because you really have to think about the answer,” I agreed.

“If you caught me at my office,” I continued, “leaning back in my chair, arms folded behind my head, feet up on the desk, how would you describe my activity at that moment?”

Vicki grinned, “I could say that you were goofing off, but I know better. You would be thinking.”

“And what would I be thinking about?”

“I don’t know, your next project, how to solve a problem, perhaps thinking about a decision that needed to be made?” she floated.

“Yes, so would you call that work?” I stopped as Vicki nodded in agreement. “And if one of your technicians goes outside to the picnic area for a break, and he isn’t goofing off, what would he be doing?”

I could see Vicki looking for the trick in the question. “Okay, if he is not goofing off, then he is probably thinking.”

“And what is he thinking about?” I asked.

“Well, he is probably thinking about his next project, how to solve a problem.”

“Yes, and so, would you call that work?”

At Every Level of Work

The biggest problem in performance management, for most companies, is focusing on the work. Many managers focus on personality characteristics or communication breakdowns thinking if someone has the right information and the right personality, performance management is a no brainer. What is missing is an understanding of the work. What is the work?

Work is not completing a task. Work is the decision making and problem solving related to the task. The most important conversation between every manager and team member is, “In completing this task, what decisions do you have to make and what problems do you have to solve?”

And, there is appropriate decision making and appropriate problem solving at every level of work.

Discretion in the Quality of the Data

“You describe the role as entry level. The output must conform to strict guidelines, which creates the quality standard. What are the decisions that must be made in connection with the work?”

Arlene was shaking her head from side to side. “We don’t allow a lot of latitude with this work. Sending prescription drugs by common carrier is serious business.”

“You think you don’t allow latitude. In fact, you tell your team members there isn’t a lot of latitude, when in fact there is. There are a ton of decisions that must be made.”

Arlene was quiet.

“Look, most of the prescribed duties involve collecting data from your customers to determine their qualifications. While it seems cut and dried, there are many decisions that must be made about the quality of their responses, the accuracy and completeness of the data.

  • Is the customer address we have on file their current mailing address?
  • Is the customer mailing address the same as the shipping address?
  • Is the telephone number we have on file a mobile number we can send a confirmation text message to?
  • Will the shipping priority we have on file assure the product reaches the customer on time?
  • If the customer does not answer the door, is it okay to leave the product on the front porch, or is there another more secure location?

“The difference between ok performance and outstanding performance is not in filling out the forms, but in the decisions related to the quality of the data that goes on the forms. The job may be completing the forms, but the work is the decisions that must be made.

“An important discussion between the manager and the team member is not about the forms, but about those decisions.”

Entry Level Work, Not Cut and Dried

“I still don’t know what you are getting at,” Arlene shook her head. “It’s entry level work. You are right, it’s not that interesting.”

“Don’t be so swift,” I reprimanded. “Let’s talk about this entry-level work. First, what is work?”

Arlene was looking up, retrieving the answer planted in her mind some weeks ago. “I remember. Work is making decisions and solving problems.”

“Okay. And what decisions must be made in connection with this entry-level work?”

“It’s pretty cut and dried,” Arlene related. “Our work is highly regulated. Everything we do has to be within very specific guidelines.”

“And what if it’s not cut and dried,” I challenged. “You see, the guidelines you work under only set the quality standards for the output. Let’s ask the question again. What decisions must be made in connection with this work? And as we answer, I think you will find this work is quite a bit more than entry-level.”

Interest in the Work (Not the Job)

“What’s missing in this young recruit’s career?” I asked.

“I don’t know,” Arlene replied. “All she seemed interested in was how many vacation days she is going to get.”

“Why do you think she is focused on her vacation days? What’s missing? What was missing in her work before she came to your company two months ago? And perhaps is still missing in her work?”

“I don’t know,” admitted Arlene. “It is pretty basic, entry level work. Perhaps there really isn’t that much to focus on, except how much vacation comes with the job.”

“You might be right be right about the job,” I agreed. “But what about the work?”