Tag Archives: testing

To the Point of Failure

As a manager, how do we know a team member’s highest level of capability? Capability is invisible. We can only see the output of capability. For that, there is evidence.

We test people through project work. Step one is a quick assessment of their current applied capability. Look at the fruits of their labor. This is an intuitive judgment on the part of the manager.

Step two is to marginally increase the current complexity of the task, in the form of a project, with the promise of project debrief on completion.

If the project is successful, it’s a prompt for the next project, a bit more complex, with the promise of a debrief on completion. Continue. Continue until there is failure.

When a team member reaches the point of failure, we now have a better grasp of the individual’s competence. We know where they are successful and where they fail.

Give it some time and challenge them again. And again. As long as the team member is employed by the organization, it is a continual process of challenge to the point of failure.

Project Work

“Who is Marie? And why is she managing only one person?” I asked.

Esmerelda was silent, then spoke. “Marie has been selected to be a manager, but needs some experience, so we gave her a person to manage.”

“And, the impact on your organization is that you added an unnecessary managerial layer. Did you give her a raise as well, did you give her the corner office?”

“Yes, we gave her a raise, and she didn’t get the corner office, but, she did get an office.”

“Like eating an hors d’oeuvre rack of soft cheese, then drinking a glass of ice water. Not good for the digestion,” I said.

“But Marie needs to learn how to be a manager,” Esmerelda protested.

“If she needs to learn, send her to training. Give her project work.”

“Like what?” Esmerelda pushed back.

“Like making a schedule, leading a small project. Give her something of short duration. If your promotion fails, what do you have on your hands, imagine chocolate dripping through my fingers. But, if you give her a project and she fails, you only have a failed project, and you, as her manager, can manage the risk in the project.”

It’s a Test

“I don’t want to go through the same experience I had with John, promoting someone to a role only to find them flailing about,” Marissa said.

“So, what are you going to do differently?” I asked.

“There is a person in another department, I don’t know him, but his manager says he is ready for promotion,” Marissa thought out loud.

“So, what are you going to do differently?” I repeated.

“I am certainly not going to trust the situation when I don’t even know this guy. I will, at least, interview him.”

“In addition to the interview, because this is an internal candidate, what else do you have the opportunity to do? How will you test him before you get wrapped around the axle?”

Marissa nodded. She knew the answer. “Project work. Task assignments with the same elements in the new role. I had a failed promotion and a chocolate mess. A failed project is only a failed project, and I can manage the risk in a project.”

Difficult to Backtrack a Promotion

As a young project manager, Mario was successful at meeting deadlines and holding profit margins on each of the four projects he completed. Paul, his manager, wanted to give him a promotion, but was gun-shy.

“The last project manager I promoted did well on smaller projects,” Paul described. “But the accountabilities of longer timespan projects overwhelmed him. In the end, I had to let him go. It was almost as if the promotion ruined a good junior project manager.”

You don’t test a person by promoting them. Though not impossible, it is difficult to backtrack a promotion. Instead, test a person’s capability by giving them project work, longer timespan projects. Only if they are successful, do they get the corner office.

Don’t promote the person to test them. Test them with project work to earn the promotion.

Test With Project Work

Hiring Talent Summer Camp starts in two weeks.
___________
“What could I have done differently?” Joyce asked. “I thought Phillip was the right choice. I know now, that I was wrong, but how do you make the decision on whether or not to promote someone?”

“Why did you think he was a candidate for promotion?” I asked.

“Well, he has been with us for a little over a year. He knows the ropes. He was a team leader, had the respect of his team,” Joyce replied.

“And what level of work do you think he is capable at?”

“Well, based on what we have been talking about, his current capability seems to be about four weeks or a little more, but not a lot more.”

“So, how could you find out how much more?”

“Well, he was successful at four weeks. I could have given him a task that took six weeks to complete, or eight weeks.”

“Exactly,” I pointed out. “The best way to determine performance is with project work. The problem with project work, is that, until we talked about Time Span, you had no way to determine the level of work. With Time Span, you can measure with more precision. Your job, as his Manager, becomes more precise.”

A Decision Based on Hope?

Sylvia was perplexed. Difficulty trusting her judgment. “I have this gut feeling that Porter would make a good supervisor. But, he is our best technician. If I promote him and it doesn’t work out, I might lose my best technician.”

“Why do you feel Porter has the potential to be supervisor?” I asked.

“Intuition,” Sylvia replied. “The only thing I am concerned about is his people skills. As a technician, he is a good producer, and whenever anyone has a question, he is the lead guy. Whenever anyone has a problem, they talk to Porter. When anyone has a decision to make, Porter gets consulted. He has a knack for knowing what needs to get done next. I can see his planning skills, always looking ahead. He knows when materials are supposed to arrive, when we need to order, even for the longer lead time stuff.”

“Then what is your hesitation?”

“Sometimes, his people skills are a little rough,” she explained. “I don’t want to promote him and then find out he is a dictator.”

“Rather than assume, or guess, or hope that Porter has the potential to be a supervisor, how could you find out? How could you find out before you promote him? How could you confirm that he is not a dictator?”

“I guess I could talk to him,” Sylvia searched.

“And, so, he tells you he is not a dictator. Is that enough? Is that enough evidence to make a firm decision to promote him?” I pressed.

“Well, no.”

“Then how? How can we create tangible evidence that he has the potential to work effectively with other people?”

“I guess I could give him something to do where he has to work with other people in the capacity of a leader?” Sylvia tested.

“Not a permanent role assignment, but project work. Give Porter a project where he is the project leader for a specific task that requires him to use the resources of other people on a project team. If he fails, you have a broken project, big deal, you can manage that risk. If he is successful, you will have tangible evidence on which to base your decision. Not a hope, a wing and a prayer, but tangible evidence.”