Tag Archives: capability

Just Try Harder

Emily was nervous as she entered the classroom. She knew that I would not allow her to be a passive observer, but front and center in the crucible. I turned to greet the other folks streaming in.

“I would like everyone to meet Emily. She has an interesting problem at work. With our help, she is going to walk us through some solutions.” Emily looked at me sideways. It would take her a bit to trust this group.

Up at the front, Emily stood. “I really don’t know what kind of problem I have,” she started. “Our manufacturing line is not meeting its daily quota and the reject rate is at 11 percent.” Emily continued to describe the circumstances, considering morale, motivation and working conditions. Then the questions came from the group.

“Who decides the daily quota?”
“How is the daily target communicated to the line?”
“Who tracks the number of completed units?”
“How does the line know if they are falling short or getting ahead of the target?”

Emily responded crisply, “The daily quota is determined by the sales forecast and what we need in stock, but the people on the line don’t need to know that. They just need to build the units faster. When the QC people pick up the units for inspection at the end of the day, they count them and it’s on my report the next day.”

Ernesto raised his hand. “So, the line doesn’t know how far they missed Tuesday’s quota until Wednesday?”

“Not exactly,” Emily replied. “I don’t want to discourage them, so I just tell them they were a little short, that they are doing good job and to try harder. I am worried about morale getting lower.”

Ernesto tilted his head to directly engage Emily. “You are treating this issue as a morale problem. Morale is only a symptom. You have to treat the root cause of the problem, not the symptom.”

Randy dragged a chair up front for Emily to sit. We were going to be there a while.

Name the Problem

It was early. Early, meaning we were the only two people on the plant floor. Emily drew a flow chart of how materials were received, then assembled and carted off to QC for inspection. She defended the competence of her workers in the assembly process.

“The issue isn’t assembly,” I said. “The issue is speed and accuracy. Have you ever counted rejects off the line?”

“Well, no,” replied Emily. “That’s what our Quality Department does.”

“So, when units leave this line, we have no idea which ones meet spec and which ones are defective?”

Emily searched in her mind for a better answer, but she couldn’t find one. “No,” she replied.

“Emily, we are talking about competence. The biggest reason for failure is incompetence. Most managers will accept all kinds of excuses. The problem is not that the line is running too fast or too slow or that it is too hot or too cold, or that we don’t have great health insurance or that the team isn’t motivated. The problem is incompetence. Most managers won’t call it incompetence, because they don’t know how to solve that problem. The problem you name is the problem you solve. The issue is speed and accuracy. The problem is incompetence.”

“So, what should I do?” Emily asked.

“Funny, you should ask. Tonight, in class, we are going to talk about control systems and feedback loops. Why don’t you come, as my guest? I will help you teach the subject.”

Did Not Do It, Because I Couldn’t

“But, I just told you that my people are competent,” Emily protested. “They have been working on the line for several years.”

“You said, the problem was reject rates. Yes, your team is competent at the task, but not competent at accuracy and speed,” I explained. “I used to work in an accounting firm. When I started, I thought I was great at adding up numbers. And I was. I was extremely competent at adding numbers (after all, I did manage to graduate from second grade). But I was incompetent at accuracy and speed.

“Never in my life, was I taught to error-check a column of numbers by adding the column twice and comparing the totals. That practice never occurred to me. And if it had occurred, I would have immediately concluded that it would take twice the time to add the numbers twice. Logic told me so.

“I had to learn a new skill. I had to become competent at using an adding machine without looking. I never did it before, because I couldn’t.

“Before, I would add numbers up with an occasional mistake. Now, I add them up twice in less time, virtually error-free.

“Your people on the line are competent at the task, but not competent at accuracy and speed.”

Emily was silent. Finally she spoke, “Okay, I think I get it. But I am not sure what to do. How do I bring up their competence in accuracy and speed?”

“First, we are going to have to count some things.”

We Never Fix the Real Problem

I was getting major push-back from Emily. She appreciated the logic, but, still, there was an internal struggle.

“My guys on the line have been putting these units together for years. They have the experience. They are competent at the assembly,” she said.

“Then what are you dissatisfied with?” I asked.

“Well, we still get too many rejects and they always fall short in unit count at the end of the day,” she replied. “But they know how to do their job.”

“Then, what do they say the problem is?”

“Well, first, they say the daily target is too high. Some say the line runs too fast. Some say it runs too slow. It’s too noisy. For some it’s too hot, others, it’s too cold. You want more? I got excuses as long as my arm.”

“So, they say the cause of the problem is always an external factor, never because of their incompetence?”

“Oh, absolutely. Don’t even go there,” she cried.

“Then, let me go farther and substitute a word for incompetence. Much failure is caused by stupidity.” I stopped. “We don’t talk much about stupidity in the workplace. The reason we don’t talk much about stupidity, as the cause of failure, is that, as managers, we don’t know how to fix stupidity. So we try to fix all kinds of other things. We speed up the line, we slow down the line, we change the temperature. But we never address the real problem, stupidity.” I could see Emily’s eyes grow wide.

“Emily, I use the word stupidity because you get the point in a nanosecond. Now, put the word back, think about incompetence. Much failure in the workplace is caused by incompetence. But we, as managers, don’t know how to fix incompetence, so we try all kinds of other things. We never address the real problem, incompetence.”

Competence Trumps Fear

“It sounds too simple,” protested Emily. “People do things because they can? It sounds like circular logic.”

“It is what it is,” I laughed. “Emily, think about it. If you do not have the competence to perform a task, what is your confidence in your ability to perform?”

“You mean, if I can’t sing, I don’t sing?”

“Right. Why don’t you sing?”

“Well, I really am not a very good singer, so except in church (where I am a virtuoso), I am embarrassed to get on a stage or behind a microphone.”

“Fear drives a lot of behavior. It is a very powerful emotion and prevents us from much achievement. But competence trumps fear. That is why competence is a critical link in success.

“Incompetence creates most failure. But most people want to blame their failure on some external circumstance. Most people are unwilling to see their own incompetence. Most people are unwilling to look inward for the key to their success.”

Why Does a Manager Manage?

“Emily, why does a race car driver press the metal in excess of 200 mph to win a race?” I asked. “Why does a singer perform on stage? Why does an ice skater reach their peak in international competition? Why does a manager manage?”

Emily knew there was a very specific answer to this question, so she waited.

“They all do those things because they can. They spent great periods of their life creating habits to support the skills that drive them to the top. They reach high levels of competence because they practiced, tried and failed, got better and practiced some more, with a discipline to master those skills. They perform at a high level because they can. The people who did not master those skills, who were not competent, were eliminated in the first round.

“Those who achieve mastery are a select few. And that includes effective managers.”

Too Hot? Too Cold? Just Right?

“So, how do we measure Hector?” Eduardo asked. “I’m all ears. I understand how to measure the time span of the tasks that Hector is responsible for. And, the longest task is three months. But, how do we measure Hector?”

“It is really very simple. You now know the time span of the longest task in the role that Hector plays. Here is the question.

“Does Hector, in your judgment as his manager, have the capability to perform the tasks in his role as freight supervisor? Or does he fall short in his capability to perform those tasks? Or does he have the capability to perform tasks with a longer time span?

“It’s like Goldilocks and the Three Bears. Is the porridge too hot? Too cold? Or is it just right?”

Eduardo squinted, “That’s it? Too hot, too cold or just right?”

I nodded, “Which is it?”

“Well, Hector does most of the job okay, but when it comes to the more complicated stuff, he falls short.”

“So, to recap your judgment, as his manager, Hector falls short?” I repeated.

“But, I knew that already,” Eduardo complained.

“Yes, you did, but you did not have a way to measure what you already knew. Now, you know that Hector falls short in capability at three months. If you define the time span of the shorter tasks he completes, you will have a very precise measure of his capability.”

Eduardo was quiet, then spoke. “Hector handles the one month stuff well. But falls short on the three month stuff. Hector’s time span is on the up side of one month, but the short side of three months.”

“So, now, is the question. How is this helpful to you as his manager?”

What’s the Level of Work?

“Where do we start?” Eduardo asked.

“Where do you think we should start?” I replied.

“We are trying to measure Hector’s capability. Is he big enough for the role. That’s the goal of this session,” Eduardo established.

“So, what unit of measure have we talked about when it comes to defining the tasks involved in his job?”

“We talked about time span,” he said.

“And, what was the measure of the longest task in Hector’s job?”

“We said, one month. Hector is in charge of shipping, but it’s more than just getting freight out the door. He is responsible for proper crating, working with vendors to select the proper crating materials, collecting information about product damage in transit. It is really a big job. Some of the problems that have to be solved involve testing in-house, you know, crash testing and then field testing.

“So, I don’t think one month is accurate. I think, to be successful, the longest task is three months. It takes that long to solve some of the material damage issues in that department,” Eduardo concluded.

“Okay, three months is the longest task required. To be successful running the shipping area requires the ability to work three months into the future, without direction, using his own discretionary judgment?”

Eduardo nodded, “Yes, I need Hector to carry the ball the whole way. I may check up on him more frequently to see if he still has the ball, but I need him to supervise the resolution to some of these issues without me. If I really have to get involved, then Hector is not doing the necessary work.”

“So, success in the job requires a time span of three months?” I asked.

“Yes.”

“That is step one. Firmly establishing the time span of the longest task, establishing the required time span for the role.

“Are you ready for step two? The next part is to measure Hector.”

Why Time Span is Important

From the Ask Tom mailbag –

Question:
Why is Time Span important? I don’t see how the length of time it takes, to complete a task makes a difference in writing the role description.

Response:
Calibrating the level of work in the role description is absolutely critical for the manager to gain insight into the decision making and problem solving required for success in the role. If the hiring manager cannot determine the level of decision making and problem solving, the successful search for a candidate will mostly be based on luck.

Intuitively, we can agree that some problems are more complex than other problems. Intuitively, we can agree that some decisions are more complex than other decisions. But, intuitive understanding does not help us measure that complexity.

And I am not talking about detailed complexity. Engineers love detailed complexity. They write computer software to handle all the detail in scalable databases. That is not the complexity I am talking about.

The complexity I am talking about, is the complexity created by the uncertainty of the future, the complexity created by the ambiguity of the future. That complexity can be measured by identifying the target completion time (Time Span).

Do you remember Murphy? Murphy has a law. Anything that can go wrong, will go wrong. How long do we give Murphy to play? That is Time Span.

The Time Span of a problem or the Time Span of a decision will give the hiring manager insight into the talent (capability of the candidate) required to be effective in the role.

  • Short term problems can be solved through trial and error.
  • Medium term problems may require experience (documented experience).
  • Long term problems (problems we have never solved before) may require root-cause or comparative analysis.

The Time Span of the problem will indicate the method (and capability) required to solve it.

Remember the BP oil spill in the Gulf of Mexico? The Time Span of the problem at hand was short. The problem required an emergency solution. We watched on television, in real time, as engineers cobbled together trial and error solutions. We did not need a sophisticated well thought out solution. There was no time for longitudinal studies of hydraulic pressures in geological fissures. We just needed a mechanical wrench to choke off a hole in an underwater pipe.

But longer term, when drilling rigs are designed, to simultaneously get to the oil AND safely protect the operating crew AND protect the long term environmental impact, well, that solution will require a bit more than choking off a hole in a pipe.

The Time Span of a problem or the Time Span of a decision gives us insight into the talent required to be effective in the solution. And the person selected out of the candidate pool makes all the difference.

The solution is seldom a matter of WHAT, more often a matter of WHO.

Role Mis-Match?

From the Ask Tom mailbag –

Question:
How do you deal (humanely) with someone who clearly is holding an S-IV role, but only appears to have S-III capability?

Response:
First, understand that this person is doing their best, and the mistake was made by the manager (I assume that is you) who promoted this person into that role without proper due diligence.

Now, what to do?

Pull out the role description and carefully examine those Key Result Areas that describe decision making and problem solving at S-IV (multi-system analysis and system integration). Using the role description, you can either manicure the role to reassign those accountabilities to someone else or choose to transfer the person to another role which better matches their capability.

The most important part of this managerial move is to understand, the discussion centers around the tasks, activities, decisions and problem solving. The discussion does NOT center around the stratum level capability of the person. This is an important nuance.

As the manager you have the following authority –

  • Determine the level of work in the role.
  • Determine the effectiveness of the person in the role.

As the manager, you do NOT have the authority –

  • To guess the stratum level of capability of the person.
  • To guess the potential capability of the person.

As the manager, you may have an intuitive judgment about a person’s capability or potential capability. You may take action related to that judgment ONLY by testing the candidate against effectiveness in the role (or testing the candidate with project work similar to the level of work in the role). It’s all about the work, not about a number.