The Big Derailer

“Tell me what you accomplished so far with the pattern we talked about?” I asked.

“We met, everybody, same room. I acknowledged the heated exchange between Fred and Jim from the week before, that there was an issue of underperformance on a project. I asked everyone to write down how they felt during the exchange, then once around the table, everyone speaking only for themselves. No one was allowed to say -we all felt this, or most of us felt that, everyone can only speak for themselves,” Ron started.

“Okay,” I nodded. “We know what the issue is, that we are attempting to resolve underperformance on the project. We were clear to acknowledge the emotional load that went with it. Fred and Jim are now aware of the impact of their heat on the team. Now we get curious.”

Ron furrowed his brow. “What do you mean get curious?”

“I mean, questions and only questions,” I said.

“Who is asking the questions and who is responding?” Ron wanted to know.

“Everyone on the team is asking the questions. Fred and Jim get to respond. Here is a quick list –

  • Working on the project, what did you observe? What did you see, what did you hear?
  • What was the impact on the project? What were other impacts on the project? How did that make you feel?”

“Whoa, whoa,” Ron stopped me. “We keep talking about feelings. What do feelings have to do with this?”

“That’s easy. First, it is out in the open that there was underperformance on the project, which is what we are trying to fix. Fixing the problem got derailed by the emotions in the exchange. We can avoid those emotions, we can stuff them down, we can ignore them, but they will come back, they always come back. Let’s get the emotions out on the table now, so we can acknowledge them, check them with reality, so we can get on with fixing the problem.”

What Would Happen?

“But, Sue, Tony and Ricardo were just bystanders in the exchange between Fred and Jim,” Ron was puzzled. “Shouldn’t I keep them as bystanders and just deal with the two primary actors?”

“Sue, Tony and Ricardo are as involved in the fracas as Fred and Jim. They may not have actively participated on the front end of the exchange, but they were certainly impacted on the back end. Fred and Jim need to hear about that. So, yes, everyone gets a turn in the discussion, but, only speaking for themselves. And you, you are not exempt, just because you are the leader. How did you feel when the back and forth between Fred and Jim got heated?”

“I felt threatened, my stomach got a little knot in it,” Ron replied. “I wanted it to be over, I wanted it to stop.”

“And, what else?” I asked.

“I felt like the team was going to explode, or fall apart.”

“And, what else?”

“I felt if Fred and Jim continued their animosity, it might turn violent and they would never be able to work together again.”

“Good,” I said. “I assume you will hear similar things as you go around the table.”

“And, that’s it?” Ron stopped.

“No, now it is time to get curious. What was it that contributed to the heat? Now is the time for questions.”

Hall Pass

“If you are not going to pretend to be in control of the emotional exchanges in the meeting, what do you need to allow yourself to do in the meeting?” I asked.

“I need to allow myself the ability to listen to each side before I judge the conversation off limits,” Ron replied.

“Can you give yourself a hall pass to do that?”

“A hall pass?” Ron chuckled.

“Yeah, a hall pass. Write that down. Give yourself a hall pass to listen to each side before you judge the conversation off limits,” I smiled.

“I feel like I am writing a permission slip from my parents.”

“Call it what you like,” I nodded. “Now, what do you need from the team to make that happen?”

“When Fred and Jim got into it, in the meeting, they were trash talking each other,” Ron’s turn to nod.

“So, what do you need from the team to give yourself permission to listen without judgement? And, remember, it’s the emotions that made you uncomfortable, not the fact that Fred and Jim were calling each other out on performance. What do you need from the team, including Fred and Jim?”

“If I were brave enough to ask, as the leader,” Ron started, “I would ask each of them, in the face of a shortfall in expectation, what is the impact on them, personally, and how does it make them feel. And, that they should only speak for themselves. No speaking for someone else. Fred cannot speak for Jim and Jim cannot speak for Fred.”

“And, don’t forget about Sue and Tony and Ricardo, they need to speak for themselves as well.”

Pretending

Ron took a moment to reflect on the way he felt during the heated discussion the week before at the management team meeting. “We have already established that there was a knot in my stomach. When Jim and Fred went after each other, at first I was surprised. Then, I went into self protection mode, wondering if the expressed emotions would swing around to me. As the leader, sometimes I feel like everyone depends on me to control situations like this, especially if they are out of control.”

“That’s a good start,” I said.

“Oh. I wouldn’t tell the team that, I thought this was just between you and me,” Ron replied.

“Right now, it is just between you and me. What version of that would you consider sharing with the team?”

“Well, I wouldn’t want them to see me as some sort of a weak leader,” Ron reflected. “So, I would probably leave out the part about me not being in control.”

“Do you really think you were ever in control,” I asked. “Control is a funny thing, sometimes just an illusion. Do you think it is important that the team always sees you in control, even when you are not?”

“Can’t I at least pretend?”

“You can, but how will the team come to some resolution if you pretend to be in control?”

How Did You Feel?

“So, there will be a little knot in each team member’s stomach,” I said. “They will remember the discussion at the team meeting last week that was none too friendly, so you quickly adjourned. What are you going to do differently this week, assuming you are not going to avoid the discussion?”

Ron had to think. “I don’t want to avoid the conflict, but I do want to manage it.”

“And, how do you intend to manage it?” I asked.

“We need some sort of ground rules for the meeting when people disagree. I want to keep the emotions out of it,” Ron replied.

“What if emotions are all part of the conflict?” I smiled. “Because if there is a conflict, there are usually emotions attached.”

“But, it’s emotions that caused the conflict,” he insisted.

“Think about this shift,” I probed. “Emotion is part of the conflict, not necessarily the cause. And, if we don’t acknowledge the emotion, it will get stuffed down. Stuffed down emotion causes people to armor up, get defensive and go into self-protection. Could you ask a question to the group that would require each person to just check-in on what they were feeling last week during the altercation and how they feel today as we work toward resolution.”

“You mean like ask them to talk about their feelings?”

I nodded. “Yes. Like this. How did you feel last week during the discussion between Jim and Fred when things got heated?

“Is that a question for me, right now?”

I nodded again. “Yes.”

A Little Knot in the Stomach

“In the heat of the moment,” I started, “you may not have had the words or the stomach for it, so you adjourned the meeting.  But, this team will have to gather again.  When?”

“Wednesday,” Ron replied.  “We meet every Wednesday.”

“And, the team had an entire week to ruminate about the conflict last Wednesday. What do you think their mental state will be when you reconvene the group?”

“Well, I hope things will have settled down between the two managers, we can let bygones be bygones and get on with the agenda,” Ron said.

“Does your team have that short of a memory?” I asked.

Ron was quiet. “No, they will all be thinking about the altercation last week.”

“An altercation which has not been discussed since, at least that is what you hope.” My turn to pause. “But, you can bet there has been plenty of discussion outside of that conference room. They are not unspoken words, they are just unspoken in public, with the group. What are you pretending not to know?”

“I don’t know how the team will respond if we bring it back up. We might get a repeat performance and be right back where we were last week,” Ron grimaced.

“And, how will people’s stomachs be feeling if you bring it back up?” I asked.

“My stomach is in a knot right now, just thinking about it.”

“Then, you know you are dealing with a real issue.”

Kicking the Can

“Things didn’t get nasty,” Ron reported, “but, I think it’s because I put the brakes on the meeting, and simply adjourned it pretty quickly.”

“What happened?” I asked.

“Two of our managers went after each other in the meeting. One complained about the other in front of the rest of the executive team. That immediately turned into defensiveness. I stopped the conversation from escalating and told everyone we would pick this up next Monday.”

“Timeouts are not necessarily bad, especially when the emotions speak so loudly that we cannot even hear the words. But, tell me what impact this had on the rest of the team? What did this exchange teach them about how things work around the company?”

“Well, for one thing, it clearly communicated that I will not tolerate rude or insulting behavior,” Ron explained.

“And, what else did it teach them?”

“That if the behavior persists, I will shut it down. I won’t tolerate it and I will take action.”

“And, what else?” I pressed.

“You have something in mind when you ask the same question three times,” Ron chuckled.

I nodded yes.

“Okay. The team learned that when things get rough in a management meeting, where emotions surface in the conversation, we will avoid the confrontation and kick the can down the road.”

“Now, we are getting somewhere,” I said.

Storming is Stormy

From the Ask Tom mailbag –

Question:
Our company is growing. I used to make all the decisions, but I delegated some decisions to my newly formed executive team. I made it clear which decisions I would retain as President, and which decisions I expect them to make. The team knows the guardrails I set and my expectations of discussion that would occur in the team prior to their decisions. But, what I am seeing from them looks more like a land grab with hidden agendas. There is posturing, hints of passive-aggression, smiles and promises without delivery, ass-covering, ass-covering for each other. They are a team of very bright people, who make good decisions within their own departments, but just having difficulty working together.

Response:
First, this is all normal. Organizationally, this is moving from S-III (single serial system, or at least a focus on one or two core systems) to an organization at S-IV (multi-system integration). It’s easy to talk about the content at S-IV, looking at work hand-offs, outputs that become inputs to the next function, optimizing output capacity of each function as it sits next to its neighboring function. That’s the highbrow stuff above the surface. But, underneath the surface is “how” that stuff gets done. Underneath the content is the process.

If we skip the process stuff, because it takes time away from the analytic content stuff, we may never get to the analytic content stuff. Pay me now, or pay me later.

As a team forms, from a group with disconnected goals to a team with a common goal, there is a predictable process that must occur. We can spend a reasonable time up front dealing with the process, or we can spend an unreasonable time on the back end trying to manage dysfunctional behaviors.

That process always starts with trust. Much of the behavior you describe indicates the team has not learned (yet) how to trust each other. When each member of this new team was solely accountable for their function and their function alone, you gave them marching orders to be internally focused, efficient, internally profitable (to their own budgets). You now expect them to lift their eyes and see the other parts of the organization they have to integrate with. It requires a subtle shift from an internal focus to an external focus. Each has to keep their eye on the ball with a peripheral vision on and responding to neighboring systems.

There is risk to each individual on this new team. The risk is, working in this new way, their own department (function) may suffer for the benefit of the organization (total throughput). When managers are first put in this new situation, their first response is to armor up. There is a very real lack of trust and likely evidence to prove that lack of trust.

The first step to create trust among the team members is to create a context in which they allow themselves to trust. This is messy. In the sequence of forming-storming-norming-performing, this is the storming stage. Windstorms, gusts, occasional lightening. As the President, it is your job to convene the team and create a safe space for this to happen, and it cannot be skipped. On the other side of the storm, the team will learn, set its own guardrails, determine what is okay and what is not okay (norming) and then get on with the work.

A Process and a System

From the Ask Tom mailbag:

Question:
What’s the difference between a process and a system?

Response:
A process is the way we get something done. A process is a shift from the haphazard, often the backbone of a discipline or a set of instructions. A process can take the form of a checklist, often has an order or sequence to its steps, like do this first, then do that.

A system is more robust than a process. A system has a defined start and a finish. A system also has a series of steps, but there are different relationships between the steps. In a system, some steps can be done at the same time (concurrent steps). Some steps depend on other steps to be completed first, before the current step can begin (dependent steps). Some steps run at different speeds and can bottleneck other steps (constraints). Some steps may only be required under specific conditions (conditional steps). Some steps may loop back to previous steps and repeat (iterative steps). A system looks at specific conditions, finds the similarities and, by treating them the same, produces a consistent outcome. A system looks at specific conditions, finds the differences and, by treating them differently accommodates a range of variables.

Looking at levels of work, a process may more accurately be used at S-II, while a system is more likely required at S-III.

Whose Plan?

“You have a team meeting,” I describe. “Someone has to talk and it’s not you, because no one listens to you. So, who talks?”

“My team?” Gordon answered slowly.

“Yes,” I nodded. “You describe the essence of the vision and the performance Standards. The team sets out the action plan.”

“But my team may not know what steps to take and besides, it will take too long to get them all to agree,” Gordon protested.

I nodded and smiled. “I didn’t say that your team would get there quickly. Sometimes you have to go slow now, so you can go fast later. You need your team, involved, engaged, thinking, solving problems and making decisions. You are not going to get there by telling them what to do.”

Gordon was skeptical, “But, what if I am not getting what I want?”

“If you are not getting what you want, then you are asking the wrong questions.”