Tag 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.

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

Didn’t Leave for Better Wages

The resignation letter stared at Adrian. His best team member, Eric, had just quit. Eric was employee of the year last December and just received a raise two months ago. He was in line to become lead technician in his department. What could be better? What else could Adrian, his manager, have done?

I inquired about the exit interview conducted by the HR coordinator. The form stated that Eric left for better wages.

Adrian was worried. Three years ago, Eric entered the company as an inexperienced recruit among a group of seasoned veterans. Over time, his personal productivity outpaced the entire team. In Eric’s absence, Adrian feared the overall output of the team would falter. Eric often carried the whole group.

I called Eric, already gainfully employed (at a lower wage) in another company. Happy with his decision, Eric shared his story. On a crew of six, Eric had consistently accounted for 50 percent of the output. The other team members were slackers riding on his coattails. I asked what Adrian could have done differently. The advice was quick and simple. “Cut the dead wood. Release the poorest performers and productivity would have increased, even with a reduced headcount.”

Adrian is left with the remnants of a mediocre team. But before he can heed the advice, he has to find another Eric.

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

Group Accountability?

“At first, this group dynamics stuff looked interesting, you know, everyone together under a team incentive bonus. It sounded exciting in the seminar, but in real life, this is painful,” Naomi explained. “The worst part, is we’re not getting any work done.”

“So, who is accountable?” I asked.

“I think everyone has to take a small part of the responsibility for the team not cooperating,” Naomi replied.

“No, I don’t mean who is responsible for the mess. I mean, who is accountable for the goal?” I insisted.

“The goal? We’re not even talking about the goal. We are just talking about cooperating better together, as a team.”

“Perhaps, that’s the problem,” I suggested. “You are spending so much time trying to cooperate as a group, that you forgot, we are trying to get some work done around here.

“Is it possible,” I continued, “that you have been misdirected to think more about shared fate and group dynamics than you have about your team. A team is not a group. A group may be bound together by shared fate, but a team is bound together by a goal. Stop thinking about group dynamics and start thinking about the goal. That’s why we are here in the first place.”

The Manager is Accountable

“Roger, the reason we are having this conversation is that I don’t believe your accountability on this project is clear. As the manager on the Phoenix project, you are accountable for the output of your team. You have been working with this project team for more than two years. You are accountable for who is on the team and off the team. You are accountable for monitoring the pace and quality of the team’s output. You are accountable for the work environment.” I stopped, so Roger could catch his breath.

“I know, I know I am accountable. But, if I have team members who are slow walking the job? I mean, I set the example. I am here early. I stay late. I’m engaged,” Roger defended.

“So, let’s say the pace is not meeting what the client expects, or what you expect, as the manager. What could be happening?” I asked.

Roger’s eyes flew to the ceiling, searching for answers in the back of his brain. His head began to nod.

  • “Could be an attitude problem.
  • Or, could be that the expectations are out of line.
  • Could be that the work instructions aren’t clear.
  • Maybe the training wasn’t effective.
  • Maybe we don’t have the right tools available.
  • Or, the way we have the work layout isn’t efficient.”

I could see a clearer understanding infecting Roger’s take on the problem.

“Roger, everything on your list could be valid. Which of those could you have influence on, as the manager of your team?”

Roger’s nod stopped, his eyes intent. “I can impact all of them.”

“So, I expect to see this list written. Then some analysis, which are you going to tackle first? What steps will you take, as the manager, to inspect the work instructions, check out the traininig, look at the work layout.

“This meeting is adjourned. Let’s meet tomorrow morning at ten, and you can tell me your intentions.”

It’s Not My Fault

“The subject for this meeting is our progress on the Phoenix Project. Looking at our project time lines, we are behind schedule and the client’s QC person is complaining that some of our work is sub-standard,” I explained.

“Yes, I know. I looked at the reports before I gave them to you. I have to tell you, I think I know where the problem is,” Roger backpedaled.

“We have a morale problem with one of our production teams. Some don’t show up on time. The pace of the work is taking longer than it should. I had hoped the problem was only temporary, isolated. We may have to do some housecleaning.”

“So, should I start with you?” I asked.

“What? Me?” Roger turned white, then red in the face. “But, I have been busting my backside on this project. You see me here, early, every day. My car is the last to leave after 5:00. I’ve been giving 100 percent? It’s not my fault. You want some names, I will give you names. I know who has been coming in late. I can point out the slow walkers. And besides that, the customer has made four significant design changes since we started. How could you possibly hold me accountable for things out of my control?”

I leaned back, watching Roger sputter through his defense like a kettle just shy of boiling. Sure, he had a point—latecomers and sluggishness were part of the issue—but the storm brewing in this project wasn’t entirely weathered by external factors. Sometimes, it’s not about who stays late; it’s about what actually gets done while the clock ticks. If the gears are grinding, no matter how early you oil them, maybe it’s time to clear out the old grit. Housecleaning, after all, isn’t just a figure of speech—it’s a strategy. A reset. A fresh sweep.

That’s why I’m starting from the ground up—literally. While the crew gets a wake-up call, the floors, desks, and shared spaces are getting their own kind of attention. I’ve brought in Crystal Cleaning Services, and not just because the name sounds poetic. These folks know how to deal with buildup—be it dust, grime, or dysfunction. Sometimes, a clean space signals a clean slate. And maybe, just maybe, seeing a little order restored around here will remind everyone what discipline looks like, even if it starts with a mop.