Category Archives: Accountability

Missed a Deadline

“I don’t see it,” Lindsey grimaced. “As a company, it is certainly not our intention to pit management against team members.”

“Yet, you feel a growing divide, and you are blaming the economy,” I replied.

“Well, yes, if it weren’t for the economy, I don’t think this would happen.”

“Let’s take a look at managerial accountability. Who do you hold accountable for the output of any of your teams? They have a goal, the goal is not reached. Who do you hold accountable?”

“You’re right. Just last week, our Memphis project team missed a deadline that cost us the opportunity to land a project. It wasn’t my team, but anyone could see from a couple of weeks before, that they weren’t going to meet the time constraints.”

“Who did you hold accountable for missing the deadline?” I asked.

“Well, it was the Memphis project team.”

“Wrong, it’s not the team we should hold accountable for the result.” -TF

Procrastination Killed It

“We have an ISO process audit coming up in two months and we have to get all the documentation updated before it starts. So, that makes it a two month Time Span goal,” Olivia described. “I am not sure I understand. This is a very complex project. The documentation is very detailed and technical. It will require someone at my level to supervise, to make sure it is correct. If we fail this audit, it puts several contracts in jeopardy. But a two month Time Span looks like Stratum I work.”

“There are two kinds of complexity. One type is created by the amount of technical detail. The other type of complexity is created by uncertainty,” I replied.

“Okay, I understand that if something has a lot of technical detail, it will take a long time just to parse through it. That might make a project’s Time Span longer. But I cannot get over the fact that this project has to be complete in two months, but the level of work is definitely higher than Stratum I.”

“Don’t be fooled. Because you only have two months, a great deal of uncertainty is gone. While you may think this is a tough project (detailed complexity), the limited Time Span forces this to be a simpler project.

“In two months,” I continued, “you don’t have time to start your documentation over from scratch. You don’t have time for massive overhaul, no in-depth analysis. You only have time to perform a quick review, observe a limited number of examples and make some relatively minor changes. Here’s the rub.

“The real Time Span of this project started the moment you finished version one of your current documentation. The true Time Span of the project is closer to one year than two months. Unfortunately, no manager took this assignment. No work was done. Procrastination killed its true purpose, and likely, the quality of the end product.” -TF

Goals Without Deadlines?

From our Working Leadership Online program:

Question:
I need help with my field work. I met with my manager to discuss my goals. I can list several specific goals that are interrelated but my issue is that they are mostly on-going. It is difficult to nail down the Time Span.

For example, my biggest goal is to manage the backlog so that we maintain 100% Due Date Performance. This goal, like most of mine, will never be complete. My goals are measured daily, weekly, monthly, quarterly, and annually. However, they are dynamic and I am struggling to put them in QQTR (Quantity, Quality, Time, Resources) terms.

Response:
In many environments, your work may not be project oriented with specific due dates. In some cases, the Time Span connection has more to do with evaluation periods. In your case, you describe daily, weekly, monthly, quarterly and annual Time Spans.

I am most interested in the longest Time Span goals, or those goals which are judged in longer Time Spans. I am certain you look at metrics on a daily, weekly and monthly basis to capture data so you can make adjustments. Those short term metrics measure production performance. And production performance is important.

But, for you, as a Manager, I am looking for those longer Time Span goals, not measuring Production units, but measuring your system that drives Production. I am looking for metrics about your system and the way it manages efficiency, throughput, scrap, waste, safety, slowdown and acceleration to meet order flow.

Let me take a stab in my imagination.

Prior to the end of each year (Time Span), the Due Date Performance of our backlog will be measured for the previous 12 month period. During that time, the average on-time delivery will deviate no more than 5% from the specified Due Dates.

As time goes by, that 5% goal might be reduced to 4%, then 3%, then 2%, then 1%, then 0%.

Or, if due dates are always consistent and more accurately described as lead times, your goal for a twelve month period might be to reduce the lead time delivery for every order from 40(?) days to 30(?) days. or even shorter.

In your position, as manager, I am not looking for production goals with one or two day Time Spans, but performance measured in longer Time Spans that would indicate production systems maintenance, or production systems improvement.

Let me know if this helps. By the way, thinking about goals, in this way, is different than you may have ever thought about. But, then, that’s the point. To think about your role in a new way. -TF

Goals Don’t Stay the Same

Krista had a sheepish look on her face when I asked to see her list of goals for the next three months.

“I don’t really have a list,” she said. “I mean, I know what I am supposed to do. I keep it in my head.”

“Then how do you organize your list, if you don’t have it written down? How do you share your goals with other people? How do you change and update them? Most importantly, how do you make decisions about goals?”

“Well, when I started this job, my manager explained things to me. I had a job description and I signed off on it. Is that what you mean?”

“How long ago was that?” I asked.

“About two and half years ago,” she replied.

“Your customers have changed, your market has changed, technology has changed, regulations in your industry have changed, your team has changed. Do mean that your goals have NOT changed in two and half years?”
___
The option of learning online at my convenience is a great benefit. The course was excellent – I learned many things that I can apply as a manager. -Arlene Breitkreuz

Working Leadership Online. Register Now.

  • Feb 16 – Decision Making – Using Facts and Intuition
  • Mar 2 – Planning – Creating the Future
  • Mar 16 – Delegation – Ultimate Leverage
  • Mar 30 – Control Systems and Feedback Loops
  • Apr 13 – Managing Time – Managing Yourself
  • Apr 27 – Team Problem Solving – Power of Team
  • May 11 – Coaching – Two Powerful Models
  • May 25 – Coaching – Underperformance and Misbehavior

We have 8 week subscriptions and annual subscriptions.

Uncertainty of Events

Torrey took a long breath. “So, I am responsible for the output of my team members?”

“That is what I will hold you accountable for,” I replied.

“Even if they get sick, or a machine breaks down, or materials are late,” Torrey was looking for a way out.

I nodded my head. “Torrey, the reason we selected you for this project, is that you have been successful on other projects, six months in length. I expect you to manage the uncertainty of events that could happen and will happen during a project of this Time Span. I expect you to make contingency plans, schedule redundancy where it’s appropriate, inspect for quality, anticipate schedule changes, vacations and prevent accidents. I don’t expect you to make excuses. I expect you to anticipate, modify, readjust and meet the deadline.” -TF
__
Working Leadership Online kicks off next Monday. Register Now.
Feb 2 – Goal Setting and Time Span (2 weeks)
Feb 16 – Delegation (2 weeks)
Mar 2 – Planning (2 weeks)
Mar 16 – Decision Making (2 weeks)
Mar 30 – Control Systems and Feedback Loops (2 weeks)
We have 8 week subscriptions and annual subscriptions.

Heading Off Excuses

“Don’t you think you are being a little hard on me?” Torrey floated.

“Not at all. I am just heading off the excuses I expect to hear when your team doesn’t meet your goal,” I replied.

“My goal. But it’s not really my goal,” Torrey protested. “It’s the team’s goal.”

“No, the project goal is your goal. It is you, the Manager, that I hold accountable for the project goal. Regarding your team, I only expect them to do their best.”

“But, but,” Torrey sputtered.

“But, what? You signed off on the project budget, based on the resources and the schedule. You signed off on the Goal, the What by When. I will judge your effectiveness, to manage the project resources and the schedule along the Time Span of this project.”
__
Working Leadership Online kicks off next Monday. Register Now.
Feb 2 – Goal Setting and Time Span (2 weeks)
Feb 16 – Delegation (2 weeks)
Mar 2 – Planning (2 weeks)
Mar 16 – Decision Making (2 weeks)
Mar 30 – Control Systems and Feedback Loops (2 weeks)
We have 8 week subscriptions and annual subscriptions.

Time Span Appropriate

Ruben was stumped. “You are right. Just because we give Edmund a new title, doesn’t mean he is going to change his ways.”

“Edmund will always be Edmund, and we have to redefine his role. It’s not a matter of giving him new rules not to do this or not to do that. You have already tried that in his role as supervisor. As Lead Technician, what will be his new goals? How will you re-direct him?”

“It sounds obvious,” Ruben replied. “It starts with his job description.”

I nodded affirmative. “This is critical fundamental stuff. It’s the stuff you ignore because it sounds so simple. It’s the stuff you ignore that gets you in trouble. Stuff like setting goals, performance standards and holding people accountable for performance.”

“I think I have a job description around here that might work,” Ruben hoped.

“Why don’t you start from scratch. As the manager, you have time span goals of approximately one year. Your annual plan has stuff in it that you are held accountable to deliver this year, and next year. If you had a supervisor, which Edmund isn’t, you would drive some of those goals down to that level, in time span appropriate chunks. For the time being, you are going to have to step into that role, review those supervisor outputs and determine the time span appropriate goals for your new Lead Technician.”

Ruben was quiet.

“Look, do you want to lose Edmund?” I asked.

“No way,” Ruben replied. “He’s a great technician.”

“Then you have some management work to do.”

Just Because He Has a New Title?

“Our system creates predictability,” Ruben explained. “It creates predictability without stress. It allows us to do our maintenance at the best times, allows us to properly inspect our raw materials, test our setups accurately. Everything runs.”

“What are you going to do with Edmund?” I asked.

“He should never have been promoted to supervisor. He is a great technician, a great operator, our go-to guy. We don’t want to lose Edmund, but he cannot continue as supervisor.”

“What are you going to do with Edmund?” I repeated.

“I am going to assign him to a new role called Lead Technician. He won’t like it, but right now, he won’t quit. The job market is too thin.”

“How are you going to keep him from screwing things up, just because he has a new title?”

Not a Hero

“So, in your mind, Edmund is not a hero?” I prodded.

Ruben shook his head. “No, and what’s maddening is that Edmund, as a supervisor, keeps describing his behavior as results oriented. It’s all about the results, he says. So, maybe he delivers, but there are body bags all over the place.”

“So, notwithstanding the results, how would you describe his effectiveness, as a supervisor? Thumbs up? Or thumbs down?”

Ruben laughed. “You know, that’s it. Effectiveness. If I can judge his effectiveness, it’s thumbs down. A supervisor is not effective when he ignores the metrics, skips steps in the process, then works overtime to save the day when the system breaks down.”

Proud of the Chaos

“How do you involve Edmund in the decision making about solving the problem?” I asked.

“As soon as we have the project specs,” Ruben explained, “when we know the outputs and the deadlines, we call a meeting. Edmund is the supervisor, so once we get into production, he is the one to call the shots. So, he is there, at the meeting. He sees all the elements we see, he just cannot connect them together.”

“And?”

“We have developed a very thorough system that identifies the constraints and keeps them productive. The metrics are easy to follow and the system makes our throughput very predictable. But Edmund fights the system, ignores the system and almost weekly causes a production snafu that could have been prevented.”

“How does he explain the snafu?”

“Usually he manages to jump in and pull the project out of the fire, but not without some overtime and not without putting the project in jeopardy. It’s almost like he is proud of the chaos and being the hero.”