Category Archives: Accountability

More Problems Than We Had Before

“Let’s look back at your org chart,” I suggested. “You have 110 employees and twelve layers of supervision and management. Two people quit yesterday, so your org chart is already out of date. What do you think you need to change?”

Sydney’s mood had turned from generous to perplexed. “Our intention was to make sure everyone had someone appropriate to report, and to make sure no manager was overburdened.”

“And you ended up with?” I pressed.

“And we ended up with people in positions, creating more problems than we had, before we announced this new reorganization,” Sydney explained.

“I want you to shift your approach to this problem. Instead of trying to figure out who should report to who, determine which manager is accountable for the output of which team. And for this exercise, I want you to reduce from 12 layers to four.”
____

A friend of mine in Buffalo NY, Michael Cardus, published a short piece on the impact of role-crowding, too many layers. Take a look.

Too Many Layers

Sydney thought for a moment. “We just promoted Justin to Team Leader. The rest of the guys on the crew say he is breathing down their necks. He is obviously not ready to be a full supervisor, and we are losing his productivity as a machine operator.”

“And?” I prodded.

“And I really don’t know what to do,” Sydney replied.

“Let’s look again at your instructions to Justin. You said if a team member has a problem, help them solve it, if they have a question, answer it and make sure all the work gets done by the end of the day. And yet, you said he was not ready to be a supervisor? Sounds like you gave him supervisor tasks, but you already know he is struggling with those tasks.”

“Yes, but, if we are going to have the team report to Justin..” Sydney stopped. “So, I took my lead technician and tried to make him a supervisor, even though we already have a supervisor. It looked good on paper.”

“Actually, it didn’t look good on paper. You have 112 employees and twelve layers,” I observed.

“I know, I said 112,” Sydney explained. “Now it’s 110, two people quit this morning.”

Looks Good on Paper

I was looking at Sydney’s org chart. I could see a familiar pattern.

“We have been working really hard on this,” Sydney explained. “Every manager knows who reports to them, so there should be no confusion. And every direct report has a manager.”

“I am just looking,” I said, “how many layers, or levels do you have on this chart?”

“That’s what took so much time,” Sydney replied. “We have 112 employees, in twelve layers. Pretty good job, neat and tidy.”

“Well, it all fits on one page,” I observed, “even though it’s a big piece of paper. Where did you get this printed?”

Sydney laughed. “The problem is, it looks good on paper, but not so good in reality.”

“Oh?” I said, with a diagnostic look on my face.

“Yes, like the guys on the shop floor. They all report to a Team Leader, Justin, best equipment operator we have. We told Justin, from now on, if they have a problem, you help them solve it. If they have a question, answer it. And at the end of the day, all the work needs to get done.”

“So, what’s the problem?”

Sydney took a breath. “The guys are now complaining that Justin is breathing down their necks. They say they already know how to do their jobs and that if they have a real problem, Justin is no help, they have to go to the supervisor, anyway. What’s worse, even Justin’s productivity is suffering, eight out of the last ten production days have been short to the work orders.”

“So, what do you think you are going to do?”

Identifying KRAs – Quick Exercise

From the Ask Tom mailbag:

Question:
Okay, you sold me on the importance of writing better Role Descriptions. In your workshop last week, you referred to Key Result Areas several times as part of the Role Description. I am curious about how you establish KRAs.

Response:
Indeed, Key Result Areas are the framework of the Role Description. When you took English Composition in high school, your teacher always told you, before you write your paper, you should always write the outline. (No one ever did it, but that’s another story.)

Identifying the Key Result Areas (KRAs) in a role is like writing the outline. For every role, there are between 4-8 Key Result Areas, depending on the complexity of the role.

For the Role of Plant Floor Supervisor, here are typical KRAs

  • Raw Material Inventory
  • Personnel Scheduling
  • Equipment Scheduling
  • Production Output
  • Production Output Counting and Reporting
  • Equipment Maintenance

But your question is “how” to identify these Key Result Areas? Here’s a simple exercise. Take a sticky note pad and on each note, write down one task related to the role. Don’t stop until you have at least 50 sticky notes, more if you want.

Now, look at the sticky notes and figure out which ones go together. Put them in groups. You will likely identify 4-8 groups. Once you have all the sticky notes divided into groups, give each group a name, like the names above. Those are your Key Result Areas.

Here is how they work in the context of a Role Description –

Role Description
Role Title –
Purpose for the Role –

Key Result Area #1
–Task and Activities
–Level of Work
–Accountability (Goal)

Key Result Area #2
–Task and Activities
–Level of Work
–Accountability (Goal)

Key Result Area #3
–Task and Activities
–Level of Work
–Accountability (Goal)

Key Result Area #4
–Task and Activities
–Level of Work
–Accountability (Goal)

Key Result Area #5
–Task and Activities
–Level of Work
–Accountability (Goal)

If you would like an template for this Role Description, in MS-Word, just Ask Tom and I will send you one.

Chocolate Mess, Related to a VP

From the Ask Tom mailbag:

Question:

I was hired into the company six months ago, in a managerial role. One of my team members, a supervisor, was promoted beyond his capability. It’s a mess, but a mess that I inherited. This guy is not a bad person, he means well, just over his head. Oh, did I mention, he’s related to one of the Vice-Presidents?

Response:

You are doing no one favors by leaving this person in a role where they consistently underperform, no matter who they are related to. This person may be doing their best, but pace and quality suffers.

The fix is managerial work for you. Your options range from modifying parts of the role to a complete reassignment to a different role. If you intend to modify the role, you will need to break it down into Key Result Areas and determine which parts of the role are done well, reassign the rest to someone else. In your assessment, take a look at the history of this person, what were their previous positions and how well did they do? Everyone has competence, somewhere, you just have to find it.

The political part, being related to a current VP, will require some finesse, but will likely be easier than you think. If you truly have a chocolate mess on your hands, everyone already knows it, they just don’t talk about. And yes, the VP knows it, too. You will be doing the VP a favor if you can determine a more suitable position.

It’s Not About Project Buffers

Sharon was perplexed. “We missed the deadline,” she explained. “And my Project Manager doesn’t seem to understand why.”

“What do you mean?” I asked.

“I wanted to know what caused the delay in the schedule that put us behind, and he just shrugged his shoulders. ‘Not my fault,’ he says. ‘Circumstances outside of my control.’ I mean, I know the customer changed the spec on the project, and that we had to go back for another permit, but I expect my Project Manager to anticipate things like that.”

“How so?”

“Projects of this length always have changes, customers always change their mind, that’s why we use project buffers in the schedule,” Sharon sorted out.

“What could you have done differently?”

“Me?” she quizzed. “I’m not the Project Manager, it was his job.”

“Who assigned this project to this Project Manager?” I pressed.

Sharon stopped. She had overlooked that one small detail. “You are right,” she began. “I hold my Project Manager accountable for the output of the Project Team, but I am accountable for the output of my Project Manager. I should have had more interim meetings with him to see how we were using the project buffers, to help him make decisions and solve problems.”

Shift to Efficiency

“You were more organized, but you almost went broke?” I pressed.

“Yes, we managed to get all the orders out the door, but it cost more to produce, than the revenue could cover,” Arianne replied.

“So, you needed to raise your prices?”

“Not that simple,” she explained. “We had competition. Our competitors price-to-the-customer was 15 percent below our cost to produce the same product. We waited for two years for them to go out of business. There was no way they could sustain that loss. But after two years, we figured out they weren’t losing money after all. They had found ways to be more efficient and productive.”

“What did you do?”

“It wasn’t enough to be organized. We had to examine every step. Turns out there were more efficient ways to work. We changed the sequence of some of the steps. Some steps could be done at the same time by different teams, increasing throughput. It was amazing. We cut our lead time from six weeks to four weeks. Higher throughput with the same number of people, with the same equipment, in the same facility, we lowered our cost. We shifted from just getting the orders out the door, to a consistent, predictable system.”

“Problem solved?” I asked.

“Not really. That’s when our troubles really began.”

His ASAP, Your ASAP

Sondra finished her project over the weekend.

“Last week, you assigned this task to Dale, but you ended up doing it,” I observed. I could tell she was very pleased with the project result, but miffed that she spent the weekend working when Dale had all of last week to work on it.

“I thought a lot about what you said about being more explicit about my deadline. Next time, I will try to remember that,” Sondra replied.

“More than that, the target completion time is essential to the task assignment. Dale gets all kinds of assignments. To complete them, he has to use his own discretion, primarily about pace and quality. Most of the decisions he makes are about pace and quality. Without a target completion time, he has no frame of reference in which to make his decisions. His ASAP will ALWAYS be different than your ASAP. ASAP is not a target completion time.”

Sondra smiled. I took a look at her project. It was really very good. She will make her client meeting today and life will go on.

By When?

Sondra was holding her head between her hands, staring directly down to the surface of her desk. I tapped the door and she looked at me over her glasses.

“Why the long face, said the bartender to the horse?” I asked.

She smiled through her temporary state of mind. “Gotta work tomorrow, Saturday,” she replied.

“Not the end of the world, what’s the matter?”

“I assigned a project, a major project to Dale on Monday. He asked when I needed it. I said ASAP. Today is Friday. He hasn’t started it and he is leaving town for the weekend.”

“So, what does ASAP mean?”

“It means it’s important and I need it right away. The client meeting is first thing Monday. Another communication breakdown.”

“Oh, it looks like a breakdown in communication,” I replied. “But the responsibility lies with you, the Manager.”

“What do you mean? I told him it was important and that I needed it as soon as possible.” Sondra had pushed herself back from the desk, arms extended.

I shook my head. “This is basic goal setting and you have committed the classic mistake. When you assign a task, any task to achieve a goal, what are the elements in that assignment?”

“Well, I tell them what I want them to do, you know, how many of whatever, and any important details.”

“And what else?”

Sondra was stumped. But in all fairness, her mind was thinking about Saturday. I am sure by now, she just wished I would go away.

“How about when you want the project completed by?” I prompted.

“Well, if it has a deadline, but if I just need it done, it’s going to take whatever time it takes.”

I shook my head. “No,” I said slowly. “Every task assignment ALWAYS has an expected completion time. The classic mistake most managers make is ignoring the importance of the expected completion time. Tell you what. You come in tomorrow, on Saturday, finish your project, that should have been finished yesterday and on Monday, we will talk about the importance of expected completion times.”

Who Is Accountable for the Goal?

“Our goal, their goal? What’s the difference?” Brent retorted.

“The difference is your relationship with the team, their relationship with you and your understanding of who is accountable,” I replied. “When they don’t meet your goal and you come down on them, how do you think they feel? What is their attitude toward you?”

“They know I am disappointed in them.”

“No, they get pissed at you.”

“Pissed at me?” Brent sat back. “I am not the one who is supposed to be selling, they are.”

“You are right. As the leader, I expect you to devote full attention to the management of this sales force. Which is why they are pissed at you.”

“I still don’t get it. Why are they upset with me?”

“Assuming they are doing their best, and you are still falling short of your goal, who is the only one who can hire more salespeople? Who is the only one who can schedule overtime? Who is the only one who change the assignment of leads? Who is the only one who can change their collateral literature? Who is the only one who can set selling margins?”

Brent was silent, then finally spoke, “That would be me.”