Category Archives: Decision Making

Illusion of Control

“You say that the best on your team, given a wrinkle, a bump or a calamity simply make it go away,” I nodded. “But, you said, you only had a precious few. What makes the difference?”

“When I first started out as a manager, I thought I was in control,” Madison started. “I thought I was the one who brilliantly solved all the hard problems. I thought I was the one who made all the hard decisions.”

“And?”

“My first realization is that control is simply an illusion. I was never in control,” she replied. “Oh, I could plan, I could train my team in our best practices. I could speed up our output, increase our quality standards, but I was never in control.”

“What was the lesson and how did it arrive in your lap?” I asked.

“Easy,” Madison replied. “The harder I tried to control, the worse things got. Even things like pace. I would try to control the pace, increase the rate of output, but the more I leaned in, the slower things got. I would see someone on the team do something stupid, so I would take away their authority to do it. So, instead of leaping on a problem, the team would hang out waiting for me to solve it. It was definitely passive-aggressive on their part, but I am the one who created the monster.”

“So, what was the tipping point?” I wanted to know.

“One day, everything stopped,” she said. “We ran out of a raw material and production ground to a halt. I was out visiting a customer, so I didn’t find out until the next morning.”

“No one thought to call you?”

“They were scared to call me. I was such a control freak. Bottom line, we had more material received on our shipping dock, but the paperwork hadn’t been processed, so no one dared open the crate.”

“And so you yelled at them?” I laughed.

“That’s when I realized I had to delegate. And, I don’t mean delegate in the classic sense of getting stuff off my plate. I mean delegate decision making. I got the team together and asked what would have solved the problem and kept the line going? Two people raised their hands with suggestions. I gave those two people expressed authority to open an unprocessed crate.”

“But, wouldn’t you lose control of inventory on hand?” I pressed.

“For an afternoon,” Madison was clear. “Our Bill of Materials system would have backed into the number based on finished assemblies, we could reconcile with the paperwork that would eventually be processed and we would not have lost an entire afternoon of production. More importantly, I now had two people on my team who could make the decision without me. Forever.”

Disabling the Team

“I’m stuck,” Remi flatly stated. “When I was first promoted to manager, things were okay. I could sit in my office, get my work done, the team knew what to do already. You know, do the same thing as yesterday.”

“Sounds like a cush job,” I replied.

“But, then, people started stopping by with a question here and a question there. Still not too bad, but then the floodgates opened. Sometimes, there is a line outside my door with people needing an answer, more direction, solving a problem. It’s a constant stream of distraction.”

“Why do you think your team has come to depend on you for answers to their biggest unsolvable problems?” I asked.

Remi shrugged her shoulders. “You got me?” she said.

“No, your team has you,” I smiled. “In a few short weeks, you have trained your team to bring all their unsolvable and solvable problems to you. And you were happy to help. We are always happy to help. But, what did you train them to do?”

“I get it,” Remi shook her head. “But, I’m the leader. I’m supposed to support my team. But, they seem to need support for everything.”

“Yes, you are the leader. But, the best form of leadership is self-leadership, and you have, by your good intentions, stripped that away from them. In a way, you have disabled your team from thinking for themselves.”

“So, what am I supposed to do? Not help?”

“The most effective managers are not those who tell people what to do. The most effective managers are those who ask the most effective questions.”

It’s a Box on a Checklist

“What’s the name of the movie that said – What we have here is a failure to communicate?” Nolan asked.

“You are way too young to have seen Cool Hand Luke,” I replied. “So, what’s the problem?”

Nolan nodded, “We have a communication problem.”

“I don’t believe in communication problems,” I nodded back. “A breakdown in communication is only a symptom of the problem. So, again, what’s the problem?”

“The first part of every project is a demolition phase, to tear down what was already there. The crew shows up, tears things down, but there are no dumpsters to haul away the debris. The project manager says the estimator left the dumpsters off the bid package. The estimator says the project manager should have known because we have dumpsters on every project. Looks like a communication problem to me.”

“I don’t believe in communication problems and I don’t think you have one. What you have, is an accountability and authority issue. In the working relationship between your project manager and your estimator, they have a handoff meeting at the beginning of the project. That meeting is so predictable that you have a checklist to make sure that everything is covered. I would bet that somewhere on that checklist is the word dumpster.”

“You are right,” Nolan said. “But they didn’t talk about it, AND it wasn’t included in the bid package.”

“Look,” I stared at Nolan, “you have an estimator, a project manager and a checklist in a meeting. In that meeting, what is the accountability of the estimator and what is the accountability of the project manager?  It is up to you to define that.”

Not-So-Intelligent

“That makes sense,” Luke said. “It was a little outside our normal behavior, giving nurses the authority to question a doctor about hand washing.”

“That’s the problem with normal,” I replied. “Normal is just repeated behavior regardless of the outcome. It’s the desired outcome we have to pay attention to, not what is normal.”

“I agree,” Luke nodded. “Likely, we would never make that decision without looking at mortality rates. It was only when we asked the nurses, that things became clear.”

“When you examine systems, you have to figure out how that system emerged. Was it designed to produce an outcome, or did it arrive out of repeated behaviors, ingrained as habits, without regard for the outcome?” I stopped. “A not-so-intelligent system makes even competent people (surgeons and nurses) look dumb. Eventually, competent people will overcome a not-so-intelligent system, if you give them permission, better yet, ask them.”

Is It the People or the System?

“You are saying,” Luke started, “that if I see friction in the system, I should look at the system, rather than trying to fix the people?”

I nodded affirmative. “You can have intelligently designed systems, if you create them. But, most systems emerge as a set of outcomes created by random behavior. Worse. Those random behaviors get repeated and become the norm.”

“But, we have standards,” Luke protested. “This is a hospital. We have to inspect and comply with those standards.

“Tell me,” I prodded. “A few years back, you made a change at your hospital. You had a not-so-intelligent system in your operating theatre that created a problem. Mortality rates in your surgical area were statistically above the norm. Even your doctors scratched their heads trying to figure this out. So, you asked your nursing staff what could be the problem. They recommended that you change your system, to make it more intelligent.”

“I remember,” Luke nodded. “We had to change our system of authority. Often, our surgeons were not washing their hands sufficiently prior to surgery. Of course, in the hospital, the surgeon has the authority for most all decisions. We changed our system to give the nursing staff the authority to question a surgeon related to hand-washing. We brought all the nurses and all the surgeons in the same room to discuss and create this new authority for nurses.”

“What happened?” I asked, already knowing the answer.

“Mortality statistically came back in line within seven days,” Luke replied.

I nodded. “You didn’t change the people, you changed the system.”

The Friction Inside

“Two people, working together, are likely very nice individuals apart from each other,” I continued. “As the manager, when you put those two people together, you place them in a system. Most often, that system is not defined and dysfunction emerges.”

“I always hope they can figure it out, the working together part,” Luke nodded. “And, most of the time, these teams get along, but there are always things that create friction.”

“As the manager, you notice these things,” I said.

“In an instant,” Luke agreed. “But even when I point things out, and get nodding agreement from everyone, the instant I leave, they go back to the friction-way of doing things.”

“It’s often a matter of telling, or rather not-telling,” I replied. “You tell, you talk, and they pretend to listen. Your team has difficulty making sense of the friction, until they discover it for themselves. Any parent, faced with the same dilemma usually tries these two things with the same result. They speak louder and with more frequency – if I told you once, I’ve told you a thousand times.

Luke nodded. He had two children, he was familiar with the parental response of louder and more often.

“There are two things we have to define,” I smiled. “In this working relationship, who is accountable for what? And, in this working relationship, who has the authority to make what decisions? Then stand back and simply ask questions.”

“Questions?” Luke looked at me sideways.

“Questions. The best managers are not those who tell people what to do. The best managers are those who ask the best questions, to help the team make sense of the friction, to help them discover it for themselves.”

Permission and Competence

“That makes sense,” Nadia agreed. “I have been guilty of empowering my team to do things they did not have the capability to do. Didn’t turn out so well.”

“Yes, that weasel word of empowerment has very little to do with granting permission,” I replied. “Empowerment, or rather authority to make a specific decision has more to do with competence. It is competence that creates authority, not permission.”

Authority and Competence

“So, accountability and authority go together?” Nadia asked.

“You cannot have the accountability for an outcome, unless you have the authority to make the decision that goes with it,” I nodded. “You cannot have the authority to make the decision without the accountability for the outcome. So, yes, they go together. One more element, however. Do not give someone the authority to make a decision for which they do not have the competence to make.”

“What do you mean,” she asked.

“Do not give a shipping clerk the authority to make the decision on an engineering spec for a raw material. The shipping clerk may receive it from a vendor, but it is likely the competence to determine the correct specification for the part lies with someone else. Be careful who you delegate authority to.”

Permission?

“But, I want to empower my team,” Nadia explained. “They shouldn’t have to ask permission for every little thing they do.”

“Do you think empowerment is all about permission?” I asked. “Empowerment is such a weasel word. What are you really trying to accomplish?”

“I just want them to know that I trust them, that I have good intentions toward them,” she replied.

“That you trust them in general? Or that you trust them with something specific?” I pressed.

“Trust them in general I guess,” Nadia shook her head. “To trust them with something specific, I would have to know what the specific thing was.”

“Now, you have clarity,” I chuckled. “Trusting someone in general is what makes empowerment such a weasel word. It is only operative under specific circumstances. I would rather replace the word empowerment with two other words, authority and accountability. Under a specific circumstance, you, as a manager and at your discretion, delegate the authority to make a decision. When you delegate the authority, you also delegate the accountability that goes with the decison. You can’t have one without the other.”

Bitter Solution

“It turned out to be a slippery slope,” Noah described. “We had the answer right in front of us. The entire team saw it, but they hesitated.”

“He who hesitates is lost?” I asked.

“I’ll say,” he replied. “The solution to the problem was going to be expensive, with no real way to push off the risk. So, we sat with the problem, we argued about it, complained about it, we pointed fingers at the enemy. All of that, instead of solving the problem.”

“In the end?” I wanted to know.

“In the end, a competitor, who was willing to do the work, swooped in and snatched the contract from our fingers.”

“And your analysis?”

Noah took a breath. “It was like we would rather argue, complain and blame. We would rather sit with the problem than come up with the painful solution we didn’t like. It may have been a bitter pill for our competitor, but they got the contract, and the margin that went with it.”