Category Archives: Accountability

Pace and Quality

From the Ask Tom mailbag:

Question:

I manage a drafting department of 12 people and have been quite successful over the past 5 or 6 years in improving the quality of our output and the morale of our team.

I have one team member with good skills but he takes forever to get anything done. In my effort over the years to make him more productive, I’ve afforded him the opportunity to become skilled at many different tasks, each time hoping that this would be the one that “clicked”. His production level, however, never improves even after the “learning curve” of any new skill is overcome.

I’m finally facing the fact that this guy will not ever make the pace we expect. Letting him go is difficult for me though, since I’ve acted all this time as his “enabler”. I probably should have realized his limitations a lot sooner and avoided the situation that I’m in now, that being, having a multi-skilled individual who ironically, is too slow.

What’s your take on this?

Response:

Some people master a skill quickly; others may complete a task only after some hard work (which takes time). Your response (training him in many skills) to the amount of time for task completion may have been misguided, making matters worse, even slowing his production time. Two critical components for every role are pace and quality. Pace and quality.

1. Determine what you need this team member to do. This should be based on what the company needs from him. What is his role? Write this down. Instead of training him on many different tasks, focus on the essentials of his deliverables. Don’t create a role around him. Determine the role and determine his capability to fill that role.

2. Baseline evaluation of the “candidate.” This is a very serious conversation. You have had conversations before, this one is different. Your prior conversations have been searching for something he might be good at. This conversation will focus on what the company needs from him in his role. This is a focusing conversation. The next conversation will be your evaluation, after one day, of his baseline performance in that role.

3. Improvement metrics. Rather than looking to train him on many different skills, the focus should be on throughput speed in the essential deliverables the company needs from the role. Examine each step in the process that speeds him up or slows him down. We don’t need him to learn a whole bunch of other skills, we simply need to get him faster at the essential skills.

4. Evaluate his long term contribution. After a period of three weeks, as a manager, you will know whether his behavior is becoming more effective or staying the same. As his manager, it will be time for you to make a judgment. It will be time for you to make a decision. Is the candidate becoming more effective in the essential role that we have for him? This is a yes or no question.

5. If the answer is yes, then you have a contributing member. If the answer is no, inform your manager that you are de-selecting this person from your team. If your manager has another role which might be suitable, turn this person over to your manager for placement. If your manager has no other role, it is time to release this person to industry.

Every part of this should be explained to the candidate. There should be no secrets. The candidate should understand the consequences of underperformance. At the same time, underperformance does not make him a bad person. It is likely that he will be relieved that he can look for a position more appropriate to his speed level, rather than live in the shadow of underperformance and constant scrutiny.

A Little Compromise, Give and Take

“What happened?” I asked.

“It was amazing,” Sean described. “We changed the name of the meeting from the VPs Meeting, to the President’s Meeting.”

“How was that different?”

“It was now clear that, as the president, I would be accountable for the decisions of the group. Before, the group was accountable as a group, sort of, but not really. Now, it is crystal clear. I am accountable for the decisions in the meeting.”

“What happened?”

“The tone of the meeting was completely different,” Sean continued. “Before, everyone was tactful and compromising, give a little here, take a little there. It was quite an agreeable bunch, and they arrived at quite agreeable decisions.”

“And?”

“And, now, without the need to compromise, knowing that I will listen to best advice and the decision is mine, there was quite a difference of opinion. The group uncovered problems that had always been swept under the rug. Some issues surfaced that had been off limits before. The discussion was actually uncomfortable.”

“Uncomfortable?” I said.

“Yes, and whenever the discussion is uncomfortable, I know we are talking about something important.”

The Clarity of Accountability

“it’s funny,” Byron thought out loud. “You always ask me, as the manager, about my contribution to the problem. Immediately, I always think – Who? Me? I didn’t contribute to the problem.”

“And, what have you discovered when you deny accountability?” I asked.

“I just have to stop. I have always confronted my team with blame-colored glasses. When I realize that I am the one accountable for the output of my team, everything changes. When I realize that I am accountable for the output of the team, I take ownership. Ownership is a powerful stimulant for caring about my team. Constructive coaching automatically follows, not because I have to, but, because I am accountable.”

“And your team?”

“They change too. They are no longer on the receiving end of blame, but are now, part of a team, supporting me, as their manager,” Byron nodded.

“And did that change happen because you circled the team to sing a song?”

“No, it happened because we got clear about accountability.”

The Electrifying Subtle Shift

“So, it turns out that the ten percent reject rate was caused by a burr on a threaded plastic part. Your inspection system failed to sample a new vendor at a higher rate and their sub-standard parts were co-mingled with good parts from your current vendor?” I nodded.

“That’s about it,” Byron agreed.

“And, yet, you yelled at your team for not working hard enough, until you discovered the defective parts?”

“I did,” Byron fessed up.

“Yet, your team was doing their very best already.”

“I know, but we were still getting the ten percent reject rate. I had to do something,” Byron protested, again denying responsibility.

“Don’t get defensive, this is important. You had a ten percent reject rate and you responded in two ways, one effective and one not.

  • You yelled at your team (not effective).
  • You inspected your system, ultimately focusing on receiving inspection, and sample rates of inspection (effective).

And where did you find the problem?”

Byron understood half the problem. “It was only when we looked at the system,” he said.

“And the other half of the problem is this. Your team is only accountable for full commitment and doing their best. When you yelled at them, you were holding them accountable for the ten percent reject rate. As the manager, you can ONLY hold them accountable for doing their best. It is you, as the manager, who is accountable for the output of the team.

“You solved the problem only when you examined your own contribution to the problem. As the manager, you are accountable for the system. It was a system problem.

“What did you accomplish by yelling at your team, holding them accountable for output?” I challenged.

“The only thing it did,” Byron admitted, “was to crush the team. I think I described it as down in the dumps.”

“And, what did you accomplish when you examined your system? You solved the problem. This subtle shift in accountability is electrifying. The team is accountable for full commitment and doing their best. It is the manager accountable for the output.”

Whose System Is It?

“You were right,” Byron admitted. “I took a look at the system. The ten percent reject rate was caused by a small burr on a threaded plastic part. The part didn’t seal right and the cylinder wouldn’t hold the pressure.”

“So, your team could have worked harder, stayed longer, given it all their might and the reject rate would have stayed at ten percent?” I floated.

Byron nodded. “I was sure it was the team. I am actually sorry I yelled at them. They just seemed down in the dumps, lackadaisical, you know, unmotivated.”

“Why do you think they were down in the dumps?” I pressed.

“Probably my fault. They were, in fact, doing their best. I thought their best wasn’t good enough. I was too quick to lay blame. In the end, it was my fault. I ordered some surplus parts from another vendor. Our original supplier was so good, we only sampled one in a hundred parts in receiving, they were always good. The new vendor parts had a 50 percent failure rate, but the samples we pulled, one in a hundred, didn’t pick up they were out of spec half the time. It was the system that allowed the failure rate.”

“And, whose system was that?”

Byron almost choked, but managed to get it out. “Mine.”

Somewhere in the System

“I know I am accountable for the output of my team, but we still have a ten percent reject rate. If my team would just try harder, the reject rate would come down,” Byron protested.

“Really? Just try harder means what?” I asked. “You told me your team was doing their best. Are you telling me, now, that they are not doing their best?”

“They seem a little down, discouraged. I know I have been on them. We need a 100 units of production each day and with a ten percent failure rate, that means we have to run 115, on average, to get our 100. If they would just try harder, they would get there.”

“I am going to make an assumption,” I said. “I am going to assume that your team shows up every day to do their best. If your team is doing their best, then there is something else in your system that is causing the failure rate. You are a smart guy. Get a big white board, draw out your system, get your team together and find it.”

Missing Targets

“We are still missing our targets,” Byron said, shaking his head. “My team just doesn’t seem to be able to do what is necessary. We produce enough in volume, but our reject rate is ten percent.”

“What are you going to do?” I asked.

“I don’t know. We have been over and over this from the beginning. I even tried a stern lecture.”

“Are they doing their best?” I prompted.

“Yes, I believe they are doing their best.”

“They are doing their best, with full commitment?” I pressed.

“Yes,” Byron nodded.

“Then, you have to look in the mirror. You picked the team. You provided the training. You provided the tools for the team to use. You provided the materials, the process, the work instructions. You provided the inspection methods. You control all the resources around the work. You are accountable for the ten percent reject rate.”

How to Interview for Soft Skills

From the Ask Tom mailbag –

Question:
How do you create interview questions about individual initiative?

Response:
Interview questions about individual initiative use the same model as any attitude, characteristic or soft skill.

  1. Identify the behavior connected to the attitude or characteristic.
  2. Identify a circumstance where we might see that behavior.
  3. Develop questions about the behavior.

Behaviors related to individual initiative –

  • Appropriately beginning a project without being told.
  • Continuing a project without being reminded.
  • Finishing a project (all the last steps) without being reminded.

Behavior – Appropriately beginning a project without being told.

  • Tell me about a project that needed to get started before your manager knew about it?
  • What was the project?
  • Who was on the project team?
  • What was your role on the project team?
  • How did you know what needed to be done without your manager telling you?
  • What were the first steps in the project?
  • How did you know those steps would be okay to complete without specific direction from your manager?
  • Did your manager ever review the initial work on the project?
  • What was the result of starting the project before your manager knew about it?

Behavior – Continuing a project without being reminded.

  • Tell me about a project you worked on, where the flow of the work was interrupted by other work, perhaps a long project that had stages to it?
  • How were the stages of the project planned?
  • How long was the project?
  • How did you know you were at a stopping point in the project and it was okay to complete other work?
  • How did you know it was time to pick the project up where you left off?
  • What flexibility did you have to decide where to stop and where to pick up with all of your other work?
  • How was your work scheduled?
  • Did you have your own schedule that you created?
  • How did you remind yourself that you still had uncompleted work on a project that you stopped?

Behavior – Finishing the work (all the steps) on a project, without being reminded.

  • Tell me about a time when you worked on a project that never seemed to end, that when you thought the work was done, there were still more steps to complete?
  • At the end of the project, what kind of items popped up, still undone?
  • At the end of the project, how did you find out about those undone items?
  • At the end of the project, how did you keep track of those undone items?
  • Did you personally have to complete those undone items, or were there other people working on those items with you?
  • How did you track what you got done and what others got done?
  • At the end of the project, when ALL the items were finally completed, how did you know there were NO uncompleted items left?

You can interview for any attitude, characteristic or soft skill, as long as you can connect it to behaviors.

The Feeling of Family

“So, you want your team to feel like a family, at least an extended family?” I asked.

Andre was thoughtful. “You have heard the expression, familiarity breeds contempt? That is the behavior I see. Petty grievances. Subtle discord. You would think that, as a family, they would get along better and, in turn, be more productive. I want them to work together, collaborate, support each other, you know, real teamwork.”

“All, noble ideas. But, could there be a paradox? Could it be, that effective group collaboration, teamwork, does not stem from a feeling of family, but rather a clear recognition of individual team members, each with individual accountability in clearly defined working relationships? Could it be structure that creates the feeling, not the feeling that creates the structure?”

What is Work?

“Max, I know how you feel about your team’s attitude toward work. You believe they only show up for the paycheck. You believe, as a manager, you have to incentivise them above their normal pay, with a bonus or spiff to get them to pay attention, or otherwise engage in discretionary effort. Your belief is in line with many employee studies that say most are NOT engaged with their work. So, let’s not talk about your team. Let’s talk about you.”

“Alright, I’m game. But, understand that I am here for the money, too,” Max clarified.

“Yes, you are right, we do have to pay competitive. More importantly, we have to get money off the table. As long as people focus on money, or, because of their circumstance, have to focus on money, employee engagement will be fleeting, at best.”

“Okay, but understand that I am still here for the money.”

“Are you really? I could show you a number of ways that you could make a great deal more money than you are making right, now,” I teased.

“I am all ears,” Max replied.

“If you were willing to sell marijuana, which is now legal in some states, you would make more money than you are currently making.” I stopped to gauge his reaction to this unusual suggestion.

“Yeah, but.”

“But, what?” I interrupted. “You see, it’s not all about the money. People, even you, want work where you can make a contribution to something larger than you. You want work where you can bring your full capability, spread your wings AND receive fair compensation for that work. You want work where your contribution is recognized as important, work that does NOT need a carrot-or-stick for you to get on with that work.”

Max was quiet. He was thinking.

“Max, you are the manager of your team. You get to design that team, select that team and create the environment that team works in. As the manager, you DECIDE the culture of that team. What will be your foundation? Will it be built around spiffs, or accomplishment? I have never known a person to be more competent in their role because they were paid a bonus.”