Category Archives: Teams

Pay Attention

“I have to change. Me?” Vicki asked, not sure if she could believe her ears.

“I am going to hold you accountable for the results of your team,” I said. “What do you have to change?”

Vicki was not pleased. “Well, if you are going to hold me accountable for the results,” she stopped. “I have to pay attention.”

“Yes, you do. As a Manager, what do you have to pay attention to?”

“I may have to be more hands on,” Vicki replied.

“Yes,” I nodded.

“I mean if someone is out sick and you are still going to hold me accountable for the results of the team, then I might have to fill in.”

“Only in an emergency. You are a Manager. I expect you to drive a forklift only in an emergency. Come on. You deal with statistical fluctuations of many elements all the time. What are you going to do?”

“Okay, so we are talking about cross training, maybe borrowing a member of another team, considering overtime. You know, 30 is really an arbitrary number. If we were short one day, we can likely make that up over the next couple of days, as long as there were no late ships.”

“I want you to think carefully. Are any of those decisions within the scope of your team members.”

“No.” Vicki shook her head slowly.

“And yet, those are the decisions that produce the results. That’s why I hold you, as the Manager, accountable. What else has to change?” -TF

Statistical Variability

“It’s not your fault that your most valuable team member is out sick, but I will still hold you accountable for the results from your team. What has to change?” I repeated.

Vicki was still stumped.

“Vicki, let’s look at all the variables that could have an impact on production. You are focusing on the team’s manual assembly. Do they work at different rates on different days?”

“Well, yes, sometimes, they work better when there is loud music playing, awful loud music,” she replied.

“So, some days are up and some days are down. I call that a statistical fluctuation. What other elements could cause a statistical fluctuation?”

“Oh, well, there are a number of things. Sometimes our tooling or tools get worn and they just can’t do the job at the same rate, until we change them out. Sometimes our raw materials aren’t quite the same and we have to stop and make small adjustments to accommodate. Heck, sometimes, too much humidity can affect the setup time.”

“So, all of those things, including the manual assembly can create statistical fluctuations in production?” I noted, making a small list on a sheet of paper.

Vicki nodded her head. A smile crept across her face. “You are right. Those are the things that create havoc in my day.”

“And who is responsible for solving those problems and making decisions, making adjustments to build 30 units a day?” I was looking straight at Vicki. “What has to change?” -TF

Not My Fault

“You’ve talked about this before, but I want to make sure I understand it. We need to get 30 units out of this team every day, 15 in the morning and 15 in the afternoon. Right now, if they don’t make it, as their Manager, I get pissed. If it happens two days in a row, double-pissed,” Vicki stated flatly.

“And if that’s the way you see it, then, your system will create behaviors that don’t help,” I replied. “Thirty units a day is your goal. You are responsible for the results from your team. If I hold your team accountable for doing their best and I hold you, as their Manager, accountable for the results, what changes?”

“But what if they show up late for work, or take too many breaks, or slow walk the line? That’s not my fault. If they do that and I don’t reach my goal, how is that my fault?”

“You are still fighting it,” I responded. “If I hold you, as the Manager, accountable for the results of your team, what changes?”

Vicki was stumped. She drew a deep breath. “If you are going to hold me accountable, then I have to make sure my team all shows up for work. I have eight people and with all the cutbacks, it takes full effort to reach my goal.”

“And, what if, one day, your most valuable team member is out sick, truly sick, and I hold you accountable for the results from your team?”

“But if someone gets sick, it’s not my fault!”

“It is not your fault that someone got sick, but I will still hold you accountable for the results from the team. What has to change?” -TF

More Than a Suggestion

“They know I will be upset and I will want to know why they failed to produce the desired result, I guess,” Vicki winced. “If I don’t find out about an order that’s late, I can’t get angry. At least until the customer calls. That’s when emotions flare up.”

“And how many of your customers don’t call when you are late?” I asked. “If you are using your customer as your QC system, is that where you really want to be?”

“I know, I know,” Vicki replied.

“So when you hold your team accountable for your result, as a system, it creates behavior that is not ideal. You don’t truly find out about production pacing until there is a visible breakdown. What can you shift to make that change?”

“You are suggesting that I am the one accountable for the team’s results?”

“I think I am making more than a suggestion.” -TF

Fixing Accountability

“Have you abdicated your responsibility, as a Manager, to a watered down decision making protocol called consensus, in an effort to appease everyone and get everyone to play nice?” I repeated.

“That’s not a fair question,” Alicia protested.

I smiled. “You are right, it’s loaded with assumption and exaggeration, but it makes a point. Who, on this team should be making critical decisions about the Phoenix Project? Critical decisions based on the excellent engineering recommendations from Russ’ department, and based on the realities of production confronted by Corey and his team?”

“But I wanted to empower the team. I wanted to get buy-in,” Alicia protested, sitting at the head of the table, each team member listening intently.

“Alicia, this team is empowered to do what they do best. This team has bought in. There is a ton of commitment around this table. What they need is a decision.

There was silence.

Paula raised her hand. “You know, this meeting has always been called the Project team meeting. Maybe it should be called the Division Manager’s Meeting?”

Alicia had not been promoted to Division Manager because she was slow. I nodded to her. My work was done. It was Alicia’s turn.

“Tomorrow morning, we will convene the Division Manager’s Meeting. We have a very important decision to make about the Phoenix Project. The meeting will last for 60 minutes, during which time I will listen to presentations, arguments and discussion about this decision. At the end of the meeting, I will make a decision as to the direction. Based on my decision, it will be up to each of you to carry on, giving it your best.

“As conditions change, we will meet each week to discuss new critical issues. I expect each of you to handle the details. We will only talk about difficult decisions.

“Thank you all for your attention and participation in this meeting. Let’s get back to work.”

Abdicating Responsibility

All eyes settled on Alicia. “Alicia, tell me again, what you believe your role is as Division Manager on the Phoenix Project?”

I had asked this question before and I could tell Alicia had practiced the answer. “My role is to put the team together, assign the leadership, make sure there is consensus and that the project stays on track.”

“And what is the name of this meeting?” I continued.

“Well, this is the Project Team meeting,” she replied.

“And do you attend these meetings?”

“Yes, at the end of the day, I am responsible for the Phoenix Project.”

“And, as the Division Manager, have you abdicated your responsibility, as a manager, to a watered down decision making protocol called consensus, in an effort to appease everyone and get everyone to play nice?”

I think I detected a bit more shifting in the chairs as this meeting was getting closer to the truth.

Who Should Make the Decision?

Paula, one of the team members from administration, raised her hand. “It seems to me that no one can make a decision around here. Russ has his engineering agenda, and it’s important, but if we don’t get the project done on time, that’s a problem, too.”

“Paula, do you think Russ should fight less hard for project specifications that he believes in?” I asked.

Paula shook her head, “No.”

“And do you think Russ should fight less hard to keep the project on track?”

Paula continued to move her head from side to side.

“So, who should make the decision?” I watched each team member look down and then look at Alicia, the Division Manager.

Not a Personality Conflict

Russ made his point, that the contract called for certain technical specifications, and also declared his bias, that his bonus was based on the absence of litigation related to project specifications. So I turned to Corey.

“Corey, the team gets confused when they get conflicting direction from both you and Russ. Russ stated a good case that we have to stick to the specs. How do you respond?”

Corey’s face was terse. “It is my responsibility to make sure this project stays on track and on schedule. Sometimes we have to make a change to prevent delays. If we don’t make our schedule, we take it on the chin with a delay claim. By the way, I get a bonus at the end of the year when we have zero delay claims against us.”

I looked at both Russ and Corey, then at Alicia, then at the team.

“So, we have conflict here. This conflict was first described to me as a personality conflict,” I began. “But, this does not look like a personality conflict to me.” I looked straight at the team, one by one. “So, what is the problem, here?”

Taking It on the Chin

Joe explained it well. The contract with his crew was to do their best. If goals weren’t met, the accountability for the shortfall must go to their leaders. It is only the leader who is in a position to make the decisions that determine success or failure.

So, I turned back to Alicia, the Division Manager, and to both Russ and Corey, the project leaders.

“So, Russ, you represent the engineering department, how do you respond?”

Russ had been quietly turning a brighter shade of red, and it wasn’t from embarrassment. “Look, it is my job to make sure that the technical requirements of the customer are met. If we make any material changes to the specifications and there is a component failure, we will take it on the chin in a lawsuit. By the way, I get a bonus at the end of every year that we are not involved in litigation.”

Speak for Yourself

I surveyed the room. No one on the team, not Alicia, the Division Manager, nor Russ or Corey, her project leaders, was making eye contact.

“The purpose of the meeting today, is to discuss the conflict between Russ and Corey and determine what is going to change to get the project back on track,” I continued. Alicia finally looked over. The blood was draining from her face.

“One ground rule in this discussion,” I continued. “I am going to ask some questions. When you respond, you may only speak for yourself.”

There were a couple of blank looks as I focused my attention, now, on the team members. I started with Joe, who was in charge of heavy equipment scheduling and logistics. “Joe, do you ever observe conflicting directions from Russ and Corey?”

Joe hesitated, but nodded his head affirmative.

“Speak only for yourself, Joe. What impact does it have on your work, when you observe these conflicts?”

Joe was a bit relieved at the question. He was afraid I was going to ask him to take sides. “Sometimes, it’s confusing,” he began. “I get started on one thing and I have to stop. I supervise a crew of drivers who move the heavy stuff in place. When I have them start and stop, I immediately know there is a problem with the leadership.” -TF