All eyes settled on Alicia. “My role is to put the team together,” she started, “assign the leadership, make sure there is consensus and that the project stays on track. Until today, this has been the Project Team Meeting.”

Alicia stopped. “I attend these meetings as part of this team, because there are often conflicting priorities based on the specific agendas each of you have. At the end of the day, I am accountable for the Phoenix Project, resolving the priority conflicts based on the latest data each of you brings to the meeting.”

Again, she stopped and looked around the room. “As the Division Manager, I abdicated my 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?”

There was shifting in the chairs as this meeting was getting closer to the truth.

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?”

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.

Alicia turned back 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.”

“Tell me more, Joe. When you are given conflicting direction from Russ and Corey, how does that impact your driver crew?” Alicia asked.

“First of all, I have a great crew,” he replied. “They are dedicated and very serious when the going gets tough. They know, at the end of this project, based on delays, there is going to be hell to pay. They know the excuses will fly and part of the blame will land on logistics.

“They also know,” Joe continued, “that, during the project, they have no control over priorities and sequence. They make recommendations, but they are not in a position to know the overall impact or changes in scope or changes in schedule. They are only in a position to move our heavy equipment as instructed.

“I keep it pretty simple. My only contract with them is that they do their best. And if, at the end of the day, the goals aren’t met, then the accountability for the shortfall must be with leadership. It is leadership that determines the schedule, sets the pace, allocates the resources and makes the decisions that determine the outcome.”

Russ made his point, that the contract called for certain technical specifications. He also declared his bias, that his bonus was based on the absence of litigation related to project specifications. Alicia 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.”

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

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

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.

Alicia turned back to Russ. “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.”

Alicia surveyed the room. Still no eye contact. The silence building like a threatening rogue wave.

“The purpose of the meeting today,” Alicia broke the silence, “is to discuss the conflict between Russ and Corey and determine what is going to change to get the project back on track.”

She had no idea what was going to happen next. This was not a move behind the woodshed, this was a move in public.

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

There were blank stares as the focus shifted to the team. Joe was the first subject. He was in charge of heavy equipment scheduling and logistics.

“Joe, do you ever receive 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 relieved at the question. He was afraid he would be asked 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 heavy stuff in place. When I have them start and stop, I immediately know there is a problem with the leadership.”

Alicia tried not to show her anxiety. She was about to conduct this meeting in a way that was unfamiliar, against the best advice she was ever taught in a leadership class. Eleven people sat around the table. Alicia, furthest from the door. Next to her, the two Project Leaders. It was a big project.

“I want to thank you for showing up today,” she began. “And, for your participation. The Phoenix Project is important to this company and you are all well aware of its delays.” Stony silence, the team waited for Alicia, after all, she was the Division Manager.

“The purpose of the meeting today is to resolve the delays caused by this project’s leadership.” She stopped to gauge the response. There was predictable shifting in the chairs. Everyone was very uncomfortable. Not a single person made eye contact with anyone else in the room.

Finally, they were dealing with the real issue on the project.

“I want to start the meeting by creating some context,” Alicia continued. “My role on the Phoenix project is to put the team together, assign the leadership, make sure there is consensus about its purpose and mission. Then, check to make sure the project stays on track.” Alicia stopped, hoping that was enough. Her focus turned to the two project leaders.

“Russ, you are the project leader from the engineering department, how do you understand your role on this project?”

Russ was quick, prepared and in less than a minute outlined his role to make sure the customer’s technical requirements were followed. There were close to 150 design specifications that would be evaluated at the end.

“And Corey, you represent the production department. How do you understand your role?”

Corey gave a brief overview of the strict time deadlines, including an example of how production decisions sometimes required substitution of materials or a change in sequence.

“And sometimes, there is a conflict in Russ’s quality agenda and Corey’s production agenda,” Alicia stated flatly. “And that is what we are here to resolve, today, the conflict between Russ and Corey.”

And that is when the silence began.

“But I was always taught, praise in public, criticize in private?” came the question from Alicia.

“Of, course, that is what the team would like you to do,” I replied. “And when you take the two project leaders out of the room, you cripple the team from dealing with the problem. The next time it happens, they will look to you to rescue them.”

“But, isn’t that my job?” Alicia pushed back.

“Is your job to make the team comfortable, or is your job to grow the team where they can solve increasingly more difficult problems? They cannot do that, when you solve their problems for them. They can only do that, when you help them solve their own problems.”