Tag Archives: manager

The Killing Fields of the Project

“I know you are right, that I should challenge my team to solve its own problem with its inability to work together in support of each other, but it is a very uncomfortable conversation,” Miriam wondered out loud. “Everyone’s stomach will be upside down, so, in your words, the threat of a real issue exists. I am just afraid that the whole thing will blow up in my face and I will be the one left to pick up the pieces.”

“It is a risk,” I replied, “and, not​ greater than the risk that mid-project, the team will reach the same impasse for this same reason. And, the higher the pressure of the project, the more likely the impasse. Do you want the team to confront the issue now, while things are calm, or meet the problem in the killing fields of the project?” -Tom

A Manager’s Stomach

“Every time you, as the manager, take a team problem behind closed doors, you participate in a grand collusion that cripples the team from solving ANY problem,” I said.

“What do you mean collusion?” Miriam asked.

“Faced with a problem the team doesn’t want to deal with, they panic and engage in non-work behaviors, so they don’t have to deal with the problem themselves. Remember your team of independent technical contributors, all very competent on their own, but they butt heads when they are required to work together?”

Miriam nodded.

“You give them a difficult project where they have to work together,” I continued. “What is the first problem they have to solve? And here is a hint. It has nothing to do with the project.”

Miriam was quiet for a moment, then, “You are right. The first problem they have to solve is how to work together. But are you suggesting that, as the manager, I put them in the same room and talk about their inability to work together?”

“Yes. And what is the reaction when you say, ‘Gentlemen, I called this meeting today to discuss how difficult it is for the three of you to work together. We are going to talk about your behaviors that derail projects and what behaviors need to change.’ Then you stop talking. How is your stomach feeling right about now? How are the stomachs of each of your team members?”

“Are you kidding? It makes me feel queasy just to think about saying that to the group,” Miriam admitted.

“Then, you know you are talking about a real issue. When everyone in the room has their stomach upside down, you know the team is dealing with a real issue. High performance teams get comfortable with discomfort. Low performance teams go into non-work and want you, as the manager, to solve the problem for them.” -Tom

Weasel Wisdom

“This is a team problem, not your problem to solve. Understand, you are accountable for the output of this team, but only the team can solve this problem. Your role is to name the problem, put it on the table, in front of everyone, and outlast the panic,” I repeated.

“I don’t know if I have the courage,” Miriam replied. “Besides, I always heard that you should praise in public and scold in private.”

“Weasel wisdom,” I nodded.

“I heard you say, there are weasel words, but now you say there is weasel wisdom?”

I continued to nod. “Yes, weasel wisdom. If it is an individual’s issue, you speak directly to the individual, and if it is a team issue, you speak to the team, in front of the team. Yes, you are right, it takes courage.”

“And if I don’t have the courage?” Miriam questioned her own confidence.

“What does that say about your belief? Remember, what we believe drives behavior. What is your belief?”

Miriam struggled. “If I don’t confront the whole team with the team problem, it says we don’t believe the team can solve the problem. It says the team cannot talk about the problem. It says the team can only deal with the problem behind closed doors.”

“And every time you, as the manager, take the team problem behind closed doors, you participate in a grand collusion that cripples the team from solving ANY problem.” -Tom

Not the Manager’s Problem to Solve

“Timing?” Miriam repeated. “I don’t wait for the team to struggle. I don’t wait for the panic when the problem emerges?”

“As soon as you put the problem on the table, the panic will ensue. Let’s say you have three head-strong team members, individually, they are all very competent in their roles. But, whenever they have to work together, the three butt heads, with their own opinions about the direction of the project. In this state, emotions run high, cooperation and support disappears, there is passive agreement in public and aggressive backstabbing in private. As the manager, on this project, you need mutual support and cooperation. What do you do?”

“When I see the misbehavior, I would sit them down, individually, and communicate my expectations. I would explain that I would monitor their behavior and that I would not tolerate disagreement and shouting.” Miriam stopped. “I think you are going to suggest something different.”

“This is not your problem to solve. Understand, you are accountable for the output of this team, but only the team can solve this problem. Your role is to name the problem, put it on the table, in front of everyone, and outlast the panic.” -Tom

Watching, Observing, Assessing

“You can still feel an allegiance to the project,” I said, “and, you are correct, as a manager, you have to solve the problem in a different way. You have to move the team. What are your levers?”

“What do you mean?” Miriam looked puzzled.

“It’s one thing to say you have to move the team, but what do you do? Where is your leverage? If your role is NOT to solve the problem, but to get the team to solve the problem, what do you control?”

Miriam stopped to think, then finally replied, “I get to pick who is on the team, team membership. I decide on training. I decide who plays what role on the team. I specifically assign tasks. And, I get to watch, observe. I can coach, but I have to stay off the field. Ultimately, I have to assess effectiveness in the role. It’s either more training, more coaching, more time or de-selection.”

“And, at the end of the day, who is accountable for the output of the team?” -Tom

No Longer the Glow of the Project

“Management is not all I thought it was,” Miriam explained.

“How so?” I asked.

“I started in the marketing department, working on projects by myself. It was satisfying. I would finish a project and I could stand back and look at it. My friends could admire the project. The project had a glow and it was me.”

“That’s because you are a results oriented person and the results were close at hand and tangible. What it different, now?”

“Now, it is slower,” Miriam started. “As a manager, I don’t get to work directly, I work through other people. The results of the project are the results of the effort of my team. I don’t get the glow out of the project, the team gets the glow. What do I get?”

“And this is frustrating?” I prompted.

“Yes, most of my problems, now, are not project problems, they are people problems. I can get the people problems resolved, but the glow is elusive. It is hard to put my finger on the result.”

“So, in your brief experience as a manager, where is the glow?”

“Sometimes, the glow doesn’t take place right away, and it is subtle, in the background,” Miriam stopped. “The glow for a manager is in the development of the team, learning, tackling tough issues and moving to tougher issues. It’s a very indirect glow. I used to have passion for the output of the project, now, it’s a matter of placing value on the development of other people.”

“Congratulations, you have discovered the true role of a manager. You thought being a manager was so people could report to you. Management is about bringing value to the problem solving and decision making of the team.” -Tom

Level of Work of a Team Lead?

From the Ask Tom mailbag –

Question:
I run a private industrial disaster recovery business. We respond to natural disasters and clean up the mess. We are very hierarchical, but I am having difficulty understanding the level of work in the teams that we dispatch.

Is it possible to have a supervisor in stratum level one? For example, we deploy teams of three people consisting of two technicians and a team captain. The two technicians are obviously working at S-I, one or two day time span, while the team captain works on a day to week at the most. The team captain directs the activities of the two technicians, but is he their manager?

We have several three person teams supervised by a single Project Manager. The Project Manager role, for us, includes team member selection, coordination of support resources, equipment, machinery, consumables as well as training for technicians and team captains. Our Project Manager clearly works at S-II, 3-12 month time span.

My question is, what is the level of work for the Team Leader?

Response:

You describe a classic case of a First Line Manager Assistant (FLMA). Elliott was very specific about this role. You are correct that the role is an S-I role and illustrates that within a single stratum level of work, we have different levels of work, illustrated below –

S-II – Project Manager, supervision and coordination, manager of the entire S-I team.
————————————————
S-I-Hi – Team Captain, directs on-site, assigns tasks, but is not the manager of the team.
S-I-Med – Technician, works under the on-site direction of the Team Leader
S-I-Lo – Technician trainee
————————————————

This works for project teams, deployed field units, multi-shift operations where the S-II Project Manager or Supervisor is not physically present at all times. The First Line Manager Assistant (FLMA) has limited authority to direct activity and assign tasks within the larger authority of the S-II Supervisor. The FLMA has recommending authority for advancement and compensation, but those decisions remain with the S-II Supervisor.

When to Promote

From the Ask Tom mailbag –

Question:
I have a technician in an S-I role, but he shows promise to be a supervisor. Shows promise, he’s not there yet. If I promote him, he will fail. Yet, he is clamoring to be promoted. If I promote him and he fails, he will likely quit OR I will have to fire him. What to do?

Response:
Your instincts are solid. I divide each stratum level of work into three parts (Lo-Med-Hi). For example, Lo-S-II would be an emerging supervisor, may not have earned the title of supervisor yet, but is still in the learning and testing phase.

Med S-II is someone with the competence to be effective in the supervisor role, certainly has the role title.

Hi-S-II is someone, extremely competent and a candidate for consideration at Lo-S-III (emerging manager).

So, Hi-S-I would be your best technician, could be called at “team lead.” If the S-II supervisor is out for the day, this guy is in charge. He will struggle in most areas as a supervisor, but given time (couple of years) he may grow and become more effective at Lo-S-II accountabilities.

Let’s take safety as a key result area (KRA), for example.
S-III designs a safety system.
S-II selects elements of the safety system to focus on each day, coached by S-III manager who designed the safety system.
Hi-S-I may deliver a 3-min safety talk to the team, on a topic selected and coached by the S-II supervisor from the S-III safety system. Hi-S-I would be the role model for the rest of the team to make sure they all go home with fingers and toes.

As time goes by, Lo-S-II projects are assigned to the Hi-S-I team member. This will give the Hi-S-I team member low-risk experience making S-II decisions and solving S-II problems. At some point, everyone will realize the Hi-S-I team member is effectively completing task assignments at S-II. That’s when the promotion happens, not a minute sooner. -Tom Foster

A More Accurate Judgement of Capability

I do not judge a person’s capability. I am not that smart. I have no authority to try to climb inside the head of a teammate, a colleague or a spouse (careful!). While I took a course of study and a minor in psychology, I have no degree, am not certified nor licensed by the state to practice psychotherapy or psychoanalysis.

People are complicated, tough to figure out. So, stop.

But work, work I understand. I understand the decisions that have to be made and problems that have to be solved. As managers, we are all expert at the work. Don’t play amateur psychologist, play to your strengths, as a manager.

I do not judge a person’s capability. I do, however, judge effectiveness, effectiveness in a role that I have selected them to play. Either the person is effective, or not. That, I can judge.

So, get out of the people judgement business and get into the role judgement business. -Tom Foster

If We Had Only Known

“But, how could I possibly know, a year in the future, what my team members will do?” Melanie asked. “I don’t even know what I am going to do a year from now.”

“That’s an interesting question,” I replied. “What questions could you ask? Think about the two supervisors you just lost, who graduated from night school. What questions could you have asked?”

“Well, I could have asked them if they were going to night school.”

I smiled. “You already told me you knew they were going to night school, so somehow you managed to ask that question. Think deeper. Think further into the future.”

Melanie’s mind began to crank. “I could have asked them what they were studying. I could have asked why that interested them. What they hoped would happen as a result of going to school.”

“And if you had known the answers to those questions?” I prompted.

“I guess I would have found out if what they wanted was something they could find here, in our company.”

“But you didn’t get that chance, did you?” -Tom