Category Archives: Accountability

Who Owns the Problem?

1 Reply

“Why the long face?” I asked.

Meredith looked up. “I’m a bit overwhelmed,” she replied. “Ever since my promotion to manager, I can feel the pressure tightening around my head.”

“How so?” I prompted.

“My team runs into situations they can’t solve. One of two things happen. They either freeze and do nothing about the problem, or they line up outside my door where the problem lands on my desk.”

“Isn’t that why we pay you the big bucks?” I nudged.

“It’s not funny. It’s stressful. And, I feel like my manager is watching me to see if I can pick up the slack.”

“Details?” I wanted to know.

“Most of the problems are self-inflicted,” Meredith explained. “The team gets behind because someone was late to work. Or the work cell shuts down because we run out of a raw material with a one-week lead time. Or the schedule gets delayed because a necessary machine goes off-line for preventive maintenance. If it’s not one thing, it’s something else.”

“And, this causes you stress?” I pressed.

“Of course. I am supposed to fix it, but most of these things should never happen in the first place.”

“As you look at each situation,” I nodded, “can you identify a person, other than you, who should more appropriately own the problem?”

“But, I’m the manager,” Meredith pushed back.

“Did you ever consider that everyone on your team owns the problem, and they are simply engaging in behavior to shirk that responsibility? And, I am looking for more than individual competence, I am looking for organizational competence. It is not enough to have individually competent players, they must work together as a team. Whose problem is it when a team member is late for work? The problem may be created by one person, but the whole team bears the brunt of the problem. You accept responsibility for the fix, when it’s a team problem.”

“So, what am I supposed to do?” Meredith pleaded.

“You sound like your team members lined up outside your office,” I smiled. “You want my advice, my guidance and direction, but, this is not my problem to solve, this is yours. So tell me, what could you do differently so the solution is distributed to those most affected, who more appropriately should own the problem?”

Whose Plan is It?

Leave a reply

“I just finished working on my team’s Professional Development Plan,” Elena announced.

“Impressive,” I replied. “You identified the basic skills, advanced skills, initial training, advanced training, along with timelines. All necessary components in a plan.”

“Yes, I got tired of new recruits coming to work, doing only what is required not to get fired,” she lamented. “Maybe this will get them off their collective asses.”

“I see,” I nodded. “I don’t have a problem with defining the skill levels, the corresponding training available. But, I am curious about the plan. Whose plan is it?”

Elena stopped to think. “You’re right. It’s my plan, not their plan.”

“I mean, you can have expectations, performance standards and timelines, but those are yours. And, if they don’t meet your expectations, they may have to part ways. But the professional development part is on the team member. As the manager, you can communicate your expectations and timelines, but the plan, and the execution of the plan has to be theirs.”

Illusion of Control

Leave a reply

“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.”

Wrinkles, Bumps and Calamities

Leave a reply

“Tell me, Madison,” I prompted. “When you think about your team, what are the characteristics you find most valuable in a team member?”

“That’s a tough one,” she replied. “I have a pretty good team. I could look at it by who produces the most output, but I manage the incoming work and spread it out evenly, so no one person gets overloaded. I could look at it by who produces the highest quality work, but we have a defined set of performance standards that every project has to meet. And, these are not mediocre threshold standards, but identify the quality that sets our company apart from our competition.”

“I understand, pace and quality are good measures of output, but still, you have team members you lean on more than others. Step through your team, one by one, what are the characteristics you look for?” I pressed.

“When things run smoothly, there is little difference,” Madison pondered out loud. “But, you know things never run smoothly. There are always wrinkles, bumps in the road and the occasional calamity. My best, and there are only a couple on my team, are those who take the wrinkle in stride, hurdle the bumps with a little adjustment and gather themselves to meet the occasional calamity. It’s when things go wrong that the best people shine.”

“Example?”

“When things go wrong, meaning something unexpected happens, most people tense up. Their logic narrows. They force solutions that don’t work, rely on old fixes that didn’t really fix. My best team members feel the same tension of uncertainty, but open alternate solutions. In fact, my best team members think about alternate solutions before the wrinkle occurs. It’s as if they are in flow in ambiguity. They remain calm. Their focus narrows, but their logic opens up to see underlying causes to the bump in the road. When they fix something, it addresses the specific situation AND provides a lesson in anticipation. In short, they make wrinkles, bumps and calamities go away. Those things still happen, but I rarely hear about them until we debrief the project.”

Shortstop or a Line Backer?

Leave a reply

“I got this from HR,” Nancy explained. “It’s a role description, talks about what kind of person we need. It addresses things like good communicator, detail orientation, team player, integrity, goal oriented. I am going to pair these up with some interview questions, and then we should be good to go.”

“Okay,” I nodded. “But let me ask, in what way do we describe the work? If you were recruiting for a baseball team, would you recruit for a wide receiver or a linebacker?”

“I’m not much of a sports fan,” she replied. “But, I think you have your metaphors mixed up. Baseball teams don’t have linebackers, that’s football.”

“So the mission of the organization will determine what roles we need?” I pressed.

“Of course,” Nancy was quick to clarify. “The output of my team is welded assemblies. So, I don’t need someone who is an expert in electronics.”

“Where does your role description talk about that?” I wanted to know. “It makes a difference. An organization designed as an airplane will never travel under water. And, an organization designed as a submarine will never fly.”

Fog a Mirror

Leave a reply

“It’s really hard to find good people these days,” Miranda lamented. “I don’t need a nuclear scientist, I just need someone to show up and follow some simple directions.”

“Over and over?” I asked.

“Well, yes, it’s a pretty repetitive job,” she replied. “I think that’s why I have a lot of turnover on my team.”

“So, anyone could walk off the street and almost immediately perform the tasks to your satisfaction?” I wanted to know.

Miranda nodded. “Yes. If we had a budget for some robots, well, we don’t have a budget for robots.”

“That’s right, no budget for robots, you’re stuck working with people. And, those people turn over. But, it seems like a simple enough job. Success does not look complicated. So, why do you have the turnover?”

“Look,” Miranda’s face tightened. “In about 30 minutes, I can get someone up to speed. You’re correct, the work is not hard. I think they leave because there is no forward path in the company, no real skills for them to develop, no innovation in the process. It’s just the work.”

“Do you think you may not expect enough from your team’s performance? If someone can just walk in off the street and immediately do the job, what is the point in that? In what way could we describe the role, to expand its decisions and problem solving, to challenge each team member to their highest level of capability? I submit, it is for you, as the manager, to ask these questions.”

Is Paying Attention a Skill?

1 Reply

“Meeting, after meeting, after meeting,” Addison lamented. “If it’s not a meeting about this, it’s a meeting about that.”

“Management is about meetings,” I replied. “If you stood back from all the meetings your company has, what is the big subject area for most?”

“That’s easy,” she nodded. “Most meetings are about some shortfall, some underperformance, a debrief on why something went wrong, a meeting to fix something next time. If you listed all the meeting subjects, you would think we were a company of incompetent stooges.”

“When there is a meeting about underperformance, how would you characterize the conversation?” I asked.

“Again, that’s easy. It starts by looking for the reason why. It ends up attempting to blame someone or some thing. It gets defensive right away, everyone CYA. No real accountability for the consequence.”

“You described the play as a group of incompetent stooges. Setting aside the stooge part, is it a problem of competence?” I wanted to know.

“Yes, you could say it that way,” Addison stopped her thought. “The blame conversation usually describes someone not paying attention, or someone skipping a step, or someone too lazy to double-check. But, I don’t know if its just an unwillingness to pay attention, or a lack of skill in paying attention.”

“Is there a skill in paying attention?”

“If you break it down,” she explained. “What should catch your attention? How often do you pay attention? What distracts you from paying attention? How do you know when you are paying attention?” A few seconds of silence lingered. “We train on the steps. We train on the sequence. We train on the quality standard. But, we never train on paying attention. And, not paying attention causes most of our problems.”

A Day of Gratitude

1 Reply

I started this blog in November 2004, so, by my count it looks like 21 laps around the circuit. For that longevity, I have to thank you, my readers. It is my hope that, not only do you read, but you shift the way you think about things related to your roles as managers and owners of organizations.

In the United State, this is a holiday week to celebrate gratitude in a day of Thanksgiving. Thank you for the opportunity, for me to think out loud. I raise a toast to you. I think I will have a beer. -Tom

State the Problem

Leave a reply

“You have a decision to make,” I said. “You looked at some new technology that has the potential to dramatically accelerate the pace of production and simultaneously ratchet up the quality of your product.”

Leo nodded in agreement. “You are correct. But there are two things I have to think about. This new technology is expensive, not related to the increase in output and quality, but its initial investment. And, once we make this investment, the second thing I have to think about is whether the team will adopt the new technology, or will they kill it. Believe me, if they want to stiff arm the project, they can kill it.”

“So, acknowledging the investment and the risks,” I wanted to know, “what steps do you need to take to mitigate the risk?”

“I think there is an order in what needs to happen,” Leo thought out loud. “I think I need to know how the team will respond to the new technology. That’s first. If they don’t embrace it, doesn’t matter how good the technology is.”

“And how will you find out?”

“I have to schedule an exploratory meeting to look at this new technology. I need to gather some data and put it in front of the team, see what they think.”

“Why do you have to gather the data?” I asked. “You have some engineers on the team, why don’t you have them gather the data?”

“But, what if they reject the new technology before we even get to first base?” Leo answered my question with a question.

“Do you think the way you state the problem has any impact on the way people approach the solution?” I pressed.

Leo nodded again. “Yes,” he stopped. “I know, I know. You want to know how I am going to lay out the problem statement in the project to get the best response from the team.”

“Yes,” I smiled. “What does that problem statement sound like? And is it really a problem statement, or a statement that points to a solution?”

Leo thought, not out loud at this point. Finally, “In what way can we explore new technology in our industry, that will dramatically accelerate our pace of output and step up our quality spec?”

“Good,” my smile turned to a remarkable grin. “Practice that, and then call a meeting.”

The Right Questions

Leave a reply

“Your team has its old method of solving the problem, but with this client, with this project, the old method is not working?” I asked.

Simon nodded in agreement.

“Your team has its own reasons for continuing the old method, even when it doesn’t work?” I continued. “What are those reasons?”

“I don’t know,” Simon suggested. “I suppose because that is the way they have always solved the problem before.”

“If you don’t know, then you are surprised when they don’t follow your direction,” I observed. “How are you going to find out?”

“Okay, okay,” Simon relented. “I have to ask them.”

“You have a goal, a target, a problem solved and a project complete,” I said. “How do you draw the team to productive behavior in solving the problem? They have their old way, you have a new way, but there is still a gap. How do you draw the team to your new way?”

“That’s the problem. If I ask, we will likely squander the precious time we have to fix the problem. They are likely to come up with unproductive solutions,” Simon was convinced.

“If you are not getting the response you want,” I smiled. “Are you asking the wrong questions?”