Category Archives: Timespan

Simple Contract

“Your bonus system creates mistrust?” I repeated.

“It’s weird. You think if you give someone a bonus, that it will make them work harder. Like they weren’t going to work hard in the first place. Do you remember that contract that Joe has with his crew. When he explained, it almost sounded silly.

My contract is simple, my team comes to work every day and does their best.

“But if I pay a bonus, it destroys that. If I pay a bonus, it’s like I am saying, ‘Come to work every day and do less than your best. And if you do your best, I will give you a bonus.'”

Beginnings of Mistrust

“And what else?” I asked.

“This is a tough one,” she started. “Our bonus system. I think our bonus system is causing some of the problems.”

“How so?”

“Well, we wanted to make sure we didn’t get into lawsuits based on construction defects, so we pay a bonus to our engineering manager when we have zero claims. It sounds noble, but that sets up someone to over-work against our operations manager, who is just trying to get the job done.

“To make matters worse, we diligently work the project schedules to avoid delay claims. Delay claims can do more than suck the profit out of a job. So we pay a bonus to our operations manager when we have zero delay claims.

“So, now I have two people on the same team who are working against each other.”

“What else?”

Alicia began with a blank stare, then a hint of something in her mind. “I think,” she replied, “the worst part about our bonus system is that it creates mistrust.”

Two Masters

“And what else?” I asked.

“That the problems I observed did not come from the idiosyncrasies of the people involved, but from the systems that I created as the Manager,” Alicia replied.

“Like?”

“Like assigning a project team with two leaders, giving neither the authority to make a decision that would conflict with the other. I thought there was a personality conflict, when it was my system drawing out the behavior. If you want to make people really schizophrenic, assign them to report to two different masters.”

Authority and Accountability

The room was empty except for the two of us. I turned to Alicia, “See it wasn’t that bad. How upside down was your stomach?”

“You know, in the beginning,” she started. “I was afraid that things would get out of control and create more of a problem. But, as the meeting continued, I finally realized that the very things that could blow my team apart were the same things that could weld it together.”

“What else did you learn?” I asked.

“I realized that I have to stop coddling people. My team doesn’t need coddling, they need leadership. And part of that leadership is that I am accountable for the results of the team.

“I am the one in position to know all of the changing circumstances reported by the individual team members. I am the only one with the authority to select and deselect team members. I am the only one with the authority to make or change task assignments. Most importantly, I am the one accountable for those decisions.”

Accountability for Results

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

“First of all, I have a great crew, 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 the leadership. It is leadership that determines the schedule, sets the pace, allocates the resources and makes the decisions that determine the outcome.”

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

The Silence Began

“I want to start the meeting by asking some questions about the project,” I continued. All eyes turned toward the two project leaders, but I started with Alicia, the Division Manager. “Alicia, what is your role, as Division Manager, related to the Phoenix Project?”

Alicia was a bit startled. She had expected the hot seats to be occupied by her two project leaders. “Well,” she took a deep breath. “My role is to put the team together, assign the leadership, make sure there is consensus and that the project stays on track.” Alicia stopped, hoping that was enough. She clearly wanted to shift the project delays to her project leaders.

“Okay,” I nodded. “Let’s hear from the two project leaders. Russ, you are from the engineering department, how do you understand your role?”

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 of the project.

“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,” I 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. –TF

Predictable Shifting

Eleven people sat around the table. Alicia, in her role as Division Manager, the two Project Leaders and the rest of the team. It was a big project.

“I want to thank you for inviting me to this team meeting,” I began. “I know most of you from other projects over the past few years. It’s good to see familiar faces.

“And I also want to thank each of you for your participation today. The Phoenix Project is important to this company and you are all well aware of its delays.

“The purpose of the meeting today is to resolve those delays caused by the project’s leadership.” I stopped to gauge the response. There was predictable shifting in the chairs. Everyone was very uncomfortable.

Whenever I see that much discomfort, I know we are dealing with a real issue. –TF

Not the Time to be a Superhero

“You have two out of five manager positions in place on a daily basis, so when you have a problem, you think you are fixing it when you are NOT fixing it,” I offered.

“What do you mean?” Derrick asked.

“When you have a problem, you think you are fixing it. In fact, you have a supervisor in play to make sure the problem gets fixed.”

“So, the problem is fixed,” Derrick insisted.

“No, the problem is fixed, but the system is still broken. You are missing three of five Managers, so you are not paying proper attention to your systems.

“You see, Derrick, when you have a problem, everyone scrambles to fix the problem. Even experienced Managers put on their superhero cape and leap in front of their biggest customer to save the day.

“What they need to focus on,” I continued, “is not the problem. They need to focus on the system. Why didn’t the system prevent that problem? Or at least mitigate the damage from the problem? Their role is NOT to fix the problem, but to fix the system.” -TF

Two Out of Five

We will be closing registration soon for our Online Leadership Program. For those who don’t get into this session, we will start a waiting list for next time.
__
Derrick located a copy of the org chart. “A little out of date,” he remarked.

“It’s time stamped only three weeks ago,” I said.

“Yeah, well, it’s still out of date.”

“So, if I think you have a system problem, where should I look on the org chart?” I asked.

“All these people are the ones who are doing the work, and the supervisors make sure the work gets done. You have to be looking at our managers,” Derrick observed.

“Yes, and I see you have five manager positions. Those are the ones responsible for creating the systems inside your company.”

“That’s why it’s a little out of date. One manager got promoted to Vice President and we figured he could still cover his old position. This manager, here, got an offer from another company, and we decided that we might be able to do without for a while. And this manager, our controller, wanted to move to the northern part of the state. And with the internet, she does her work from home.”

“Let me get this straight. You have five manager positions, monitoring your systems, yet only two out of five actually show up for work here?” -TF