Author Archives: Tom Foster

About Tom Foster

Tom Foster spends most of his time talking with managers and business owners. The conversations are about business lives and personal lives, goals, objectives and measuring performance. In short, transforming groups of people into teams working together. Sometimes we make great strides understanding this management stuff, other times it’s measured in very short inches. But in all of this conversation, there are things that we learn. This blog is that part of the conversation I can share. Often, the names are changed to protect the guilty, but this is real life inside of real companies.

Skills Training, Necessary but Not Sufficient

“Look at this,” Phil exclaimed. “We just had the training on this last week. And I just pulled samples from the prototypes. Thank goodness this isn’t a production run. I ought to fire the whole lot of them.”

I winced. “Yes, I guess you could fire them, all eight of them. But then you would have to run the line yourself. I don’t know if you could keep up.”

“You know what I mean. I’m not going to fire anybody. I’m just frustrated. Maybe it’s our training department. Maybe we need to look at the training program.”

“Perhaps,” I said. “You know, when people acquire a skill, I mean really acquire a skill, it takes more than a training program.” Phil looked at me, like I was from Mars.

“When you were a kid, did you ever learn how to throw a ball?” I continued. Phil nodded. “So, someone showed you how to throw, and you threw one ball and then you were an expert?”

Phil laughed. He suddenly knew where I was going with this. “Of course not. I had to throw a hundred balls. I had to practice. My mom was my coach.”

“So, what do you think is missing from your training program?”

Phil’s eyes narrowed. His head began to nod. “Practice and coaching.” And with that, he scooped up the samples, turned on a dime and headed for the production floor.

Could Have Been Fired

“So, you were surprised that you didn’t get fired?” I asked. Kim and I were talking about her near disaster with a forklift.

“I was certain I would get fired. It was a boneheaded move on my part. But my manager used it as leverage. He knew he had my undivided attention over the forklift. He also knew that I was motivated to make things right. So he got someone (me) to run the safety program, where it benefited the most.” Kim replied.

“How did that bring value to your thinking and your work?”

“Well, he could have fired me, he could have yelled at me. He could have embarrassed me in front of the team. He could have called me out to his boss. He could have suspended me. But what he did was to make me think.

“He had me motivated to sit down and learn more about how serious this safety stuff really is. It was one of the most important lessons in leadership that I ever learned.”

Learning From Mistakes

A good bit of the morning had passed when I met Kim in the coffee room.

“Okay, I came up with a list,” she said. “It’s not a long list, but I was able to think about some specific things that were helpful to me when I was a supervisor. It’s funny. At the time, I didn’t realize how helpful it was, but now, I can see it clearly.”

“So, what’s the biggest thing on the list?”

“We were under some pressure to get a big order pulled for shipping. I was supervising the crew. Things were hectic. I commandeered a forklift that had been pulled out of service. One of the buckles on its safety harness was being repaired. I was thinking, how stupid, not to use a forklift for a few minutes just because it didn’t have a safety harness.

“Big mistake. I told one of my crew to use it anyway, just to move some product about ten feet over in the staging area. That part was okay, but when I wasn’t looking, the crew member took the forklift over and started moving other stuff. He figured it was okay to use the machine, since I said so. He was turning a corner and ran over something, his load shifted and he came right out of the machine.

“I was lucky. No one was hurt, nothing got damaged. In fact, everyone that was there, thought it was funny. Well, except for my manager. I thought I was going to get fired. It was a stupid thing I did.”

“So, what did your manager do?”

“He never yelled at me. I remember, he just came into my office that afternoon. He said one word, ‘Lucky!’ Then, he put some safety books on my desk, said he would be very interested to attend my safety meetings for the next three months.”

“So, tell me, how did that bring value to your thinking and your work?”

Just Promoted, No Respect

From the Ask Tom mailbag –

Question:
I was just promoted to the supervisory position on a crew I worked with for the past 2 years. Unfortunately, I am having a hard time gaining the trust and respect of my co-workers as well as other supervisors and managers. It seems to be difficult for some to grasp the fact that I have been entrusted with the responsibility for this team. It might be the fact that I have not had a great deal of time in the position, as of yet, so hopefully it may get better with time and my ability to be patient. But if there is any bit of advice and/or support that you may be able to provide, I am all ears.

Response:
It is always tough to become a new supervisor, to an existing peer group or a new group. A new supervisor always means change. And most people don’t like change, at least they don’t like the unknown parts of change.

Respect comes, not from the authority of the position, or the experience of the supervisor. Respect comes from bringing value to the work and thinking of the individuals on the team.

Team members always seek out the person in the company that brings value to their decision making and problem solving. If it happens to be their supervisor, that’s great. All too often, it’s not.

Think about it. We all work for two bosses. We work for the boss who is assigned to us, and we work for the boss we seek out. The boss we seek out is the one who brings value to our work, our thinking and our lives.

So, if you are the new supervisor, that’s the boss you need to be.

How To Sort Resumes

“Think about it this way,” Jean explained. “In an ideal world, with 400 resumes, we would conduct 400 interviews, but that’s just not practical.”

I nodded in agreement.

“So, we have to have some way, by looking at the resumes, to determine which of those would most likely yield the kind of candidate that ultimately brings something to the open role.”

“And, now,” I jumped in. “You look for something about the resume that would disqualify the candidate instead of something about the candidate that is actually interesting, related to the role? You are sorting OUT, not IN?”

“Exactly,” Jean replied. “The purpose for disqualifying resumes is only to reduce the workload of slogging through candidates. It does reduce the workload, but doesn’t necessarily leave us with a high quality candidate pool.”

“So, you think there is a better way of sorting resumes that creates a better pool?”

“Yes,” Jean replied. “Let’s say we want to reduce the resume pool from 400 down to 50. I could work to find 350 reasons why we would reject a resume, or I could work to find 50 reasons why I want to take a resume to the next step.”

“So, what criteria would you use to find those 50 reasons,” I pressed.

“For that, I have to go back to the role description. Remember, it’s all about the work.”

I Don’t Know What That Means

“So, what is the goal?” I asked. “What is the expected output?”

Marianna smiled, looked down at the paper in front of her. “Strategically improve current workflow resulting in improved success on projects in support of long-term company goals.”

I nodded. “Sounds great. But, I don’t know what that means.”

Marianna looked puzzled. “Well, that is what I expect from the manager in this role,” she replied.

“I know that’s what you expect, but I am still confused.” I stopped. “It is noble to improve workflow, but I don’t know what you expect to see. How are you going to evaluate effectiveness? What do you expect this person to do?”

“Well, we have work-cells that pass work along the line. Sometimes there are delays where things stack up. Sometimes, there are quality problems that are discovered at the end of the line, where we have to scrap a whole day’s production because of a small adjustment up the line. Sometimes, we run out of raw materials, so production stops. Sometimes, our work flow gets interrupted by a priority order that gets inserted at the last minute.”

“Okay, now we are getting somewhere. You want the person in this role to chart out the workflow, identify problems related to workflow delays, interim quality inspections, raw material min-max levels and expedited orders. The accountability (work output) will be a one-page work flow chart showing work-cell to work-cell production hand-offs, identifying where delays occur, when interim quality inspections are performed, quantities of raw material inventory related to production, and contingency processes for expedited work orders.”

Marianna nodded her head in agreement.

“Then, why didn’t you say so in the first place?” I smiled.

Rejected for a Spelling Error

“We had 400 resumes in response to our job posting,” Jean complained, “but when I look at those that made the cut, I am disappointed.”

“What do you mean?” I asked.

“I looked at the reject stack. Here was one that was rejected for a spelling error, but the candidate had completed a special certificate program at a school in upstate Vermont. I know about that program. I want to talk to that candidate.”

“Rejected for a spelling error?”

“And here was one, rejected because of a three month gap in employment. But the candidate spent six months with a special ed program in a village in Africa. I want to talk to that candidate.”

“And?” I prompted.

“This candidate graduated from an unremarkable college, fresh out of school, with no work experience in our field, but managed to hold down a full-time job, a part-time job and take a full-course load in college. I want to talk to that candidate.”

“So, what passed the stage-gate?” I wanted to know.

“Here’s one. Perfect spelling, no gaps in job history, a reputable academic history, ten years experience in a retail perfume department. Only one small problem. We don’t sell perfume. How did that resume make it to the IN stack?”

“What do you think the problem is?” I asked.

“I think we are going about this all wrong. We look at resumes and find some flaw to disqualify the candidate. We look at resumes and sort OUT. I think we need to reverse the process. We need to determine the critical role requirements and then sort IN for those qualities.”

I Don’t Care What the Candidate Knows

“I don’t understand,” Rachel quizzed. “When I interviewed this candidate for the position, he knew all the technical angles of the job. Now that I hired him, it’s like he is clueless.”

“What do you think the problem is?” I asked.

“It’s the difference between talking a good game and actually playing the game,” she observed. “But when he talked about the job, he sounded like he had been doing this for years.”

“So, what do you think the problem is?” I repeated.

“Just knowing the job isn’t enough. You actually have to have done the job.”

“And your conclusion?” I nodded.

“Technical skill comes in two parts. One part is the technical knowledge. That is what I asked questions about. The other part of skill is practice. Execution takes practice. I didn’t ask interview questions about the practice part. How did the candidate practice the skill part? Frequency of practice? Depth of practice? Accuracy of practice? At the end of the day, I don’t care what the candidate knows, I care what the candidate can do.”

Everyone Liked the Candidate

“It happened again,” Ted explained. “I told myself that the next time we needed to hire someone, I would be prepared for the interview.”

“And?” I asked.

“Scott came down the hallway. He said the candidate in the conference room had talked to four other people and everyone liked him. Heck, I didn’t even know we had interviews scheduled.

“He asked if I had fifteen minutes to talk to the candidate, just to see if I liked him, too.

“Funny, I liked him, too.”

“So, what’s the problem?” I pursued.

“Everyone liked him, but here we are, two months down the road and I find out he doesn’t have any experience in one of the most critical parts of the job. He just told me point blank that he has never done this before. Worst part, he tells me he doesn’t even see that as part of his job. If we need that done, he suggests we hire an expert or a consultant to help out.

“Just what I need, to hire another consultant because someone on the inside can’t do their job.”

The Head vs The Work

From the Ask Tom mailbag –

Question:
I just finished reading Hiring Talent – thank you for writing such an outstanding book! As an executive recruiter having recently discovered Requisite Organization, your application of Jaques’ work has been by far the most helpful I have found. Nevertheless, I noted with interest no mention in your book of his Mental Processing (declarative, cumulative, serial and parallel) in determining level of work, so reaching out to find out your view on this in assessing leadership potential.

Response:
You have indeed paid attention. Elliott was keenly aware of tools (training, experience, insight) that he would use vs those tools he would train others to use. Near the end of his life, he was quite sensitive to the training of industrial psychologists and HR professionals in the use of language analysis to determine potential capability according to the four levels of mental processing. His reservations were related to the potential for abuse, misdiagnosis and personal damage that could be the result of such efforts. Understand, that this perspective (RO) is very powerful and, misused, can be devastating to an individual.

This does not minimize the value of our understanding of mental processing, but will have an impact on the tools we might use.

In my presentations and workshops, I make a distinction between two diagnostic approaches –

  1. The head
  2. The work

Elliott was a psychotherapist and perfectly comfortable in the head. But he was also aware of the pitfalls in that approach, specifically for managers and supervisors.

I stay out of the head. In my conversations with Elliott’s widow, Kathryn Cason, I came to the conclusion that we serve ourselves well if we would only focus on the work. Elliott himself, admitted that the field of psychology, with its IQ tests and personality profiles, has no clear definition for the behavior called work. That is why most psychometric assessments (Meyers-Briggs, Profiles XT, Predictive Index, DISC) are inconsistent as a selection tool. They are statistically valid and repeatable instruments, but success related to work can be elusive.

The second approach, focus on the work, turns out to be a natural application of RO for hiring managers and managers-once-removed. Calibrating mental processing in the work yields more practical results than attempting to divine an individual’s potential capability. I coach my students not to play amateur psychologist, but play to their strengths as managers. They are experts in the work.

Hiring Talent provides the prescription, using the behavioral interview, to parse through the work. The four levels of mental processing are there, but embedded in descriptions of work. My definition of work is solving problems and making decisions. Most managers can describe, in detail, the level of problem-solving and level of decision-making required in a role. And that is the focus of Hiring Talent. If we have accurately described the problem-solving and decision-making in a role, then the evaluation becomes simple. Does the candidate have experience and is the candidate competent solving those problems and making those decisions?

This approach is powerful because of its underlying science combined with the power of the behavioral interview. It is accessible to any hiring manager without exposure to RO. Even more powerful for managers familiar with RO.

I have always maintained that an executive recruiter who uses the methodology outlined in Hiring Talent will be head and shoulders above its competition in qualifying candidates for its client base.