Tag Archives: role description

Role Assessment

Question:
You talk about creating a system for recruiting that would rival our equipment procurement system. Where do we start?

Response:
Think about that machine your company just purchased. If the price was north of $50,000, a bunch of people spent a lot of time looking at this machine in many different ways. Here is where it all started.

One, two or three people sat down and did a needs assessment. In that needs assessment, they asked some very fundamental questions.

  • What do we need this machine to do for us?
  • Is there another way, or another machine that would do a better job?
  • At the end of the week, how much production do we need from this machine?
  • What are the quality standards that we need from this machine?
  • How will this machine interface with our current work flow?
  • What kind of support will this machine require to sustain the productivity we need from it?
  • What other customers like us are currently using this machine?
  • How is this machine performing for them?
  • If we grow, what capacity will this machine need, in reserve, to accommodate our growth?

Think about these questions. Replace the word “machine” with the word “person.” Think about the role description you are writing. This is where you start.

Trying to Shortcut the Work

“So, let’s call her right now, offer her the position, straight away,” I suggested.

“But, you haven’t even read the profile,” Kristen protested. Even she could see the absurdity of making an offer before proper due diligence.

“I don’t need to read the profile,” I replied, pressing the absurdity.

“But if you don’t read the profile, how can you know if this person will be able to do the job?”

“Excellent question. How can we know if this person will be able to do the job if we don’t have a role description to help us read the profile?”

“Well, we have the job posting.”

“Kristen, I read the job posting. There is more on company benefits than there is on expectations. It appears to me that you are trying to shortcut the work required in this hiring process.”

“It’s not that I don’t want to do the work, I just don’t have the time. I have a lot of other important things I need to be doing,” Kristen insisted. “Writing a role description takes a lot of time, and I am sure HR has one that is pretty close.”

“It’s not that you don’t have the time. You have as much time as you need. It’s just not a high enough priority.”

Where to Start?

Jean was upset. After two weeks of interviewing, the committee finally made an offer to a candidate for an open position. “I called her up and she laughed, said she took another position last week. So, we went to our second candidate, same thing. Our third candidate was missing two essential qualifications, but the committee didn’t want to start the process over. I just made the offer, but I am skeptical. I just hope it works out.”

“Well, hope is a strategy,” I replied. “Why did it take so long to make a decision on your first two candidates? You interviewed them almost two weeks ago.”

“Whenever the committee got together, we would argue about what was important for the position. Our meetings were more confusing than helpful.”

“The job description, wasn’t that helpful?”

Jean nodded. “It’s funny, we didn’t actually write one until this past weekend. It was only when we did, that the committee was able to agree on the qualifications and make a decision. It was just too late.”

Jean stared at the table, shook his head and smiled. “That’s where we should have started.”

Nagging Questions Before the Offer Letter

You are ready to extend the offer letter, but there is this nagging hesitation in your mind.

  • Is this the right person?
  • Am I making a mistake?
  • What happens if I am wrong?

But, you have a 90 day probation period, so if it doesn’t work out, no harm, no foul.

And, you will have to start over again, 90 days down the road.

  • Why do you have to wait 90 days to find out if this is the right person?
  • How can you eliminate mistakes in your hiring process?
  • How can you up your batting average, reduce the times you are wrong?
  • What separates the average hiring manager from the few who most consistently make good hires?

There is no magic, no fairy dust, just a little managerial work. Most managers make hiring mistakes because they didn’t know what they were looking for in the first place.

How to Describe Work

We were kicking around the new role description for a Project Manager. Howard held a copy of the current description. Current should be taken with a grain of salt. It was created five years ago and was little more than a starting place.

“Okay,” I began. “It says here that one of the responsibilities is scheduling.
-The Project Manager is in charge of scheduling materials, equipment and personnel for the project.-

“Remember our two questions? How well should it be done and by when?” I paused. The looks around the table were puzzled. I would have to dig deeper.

“Is part of scheduling actually publishing a written schedule?” I asked, finally getting nods of agreement.

“How far in advance should the schedule go?”

Matthew raised his hand. “At least a week.” He looked around to see if he was right. No one challenged him.

“Okay, by when should this schedule be published?”

Henry jumped in first. “By Friday, the week before, so on Monday, we know what is going on.”

“What time on Friday?”

“By 5:00 o’clock.” Henry replied.

I smiled. “Why not give yourself some time on Friday to review the Project Manager’s schedule to make sure it will fly?” Henry thought a minute, then slowly his head nodded.

“By Friday at noon, the Project Manager will publish a written schedule detailing the materials, equipment and personnel requirements for each day of the following week.”

“Is that better than the Project Manager is in charge of scheduling?”

Where Management Trouble Begins

From the Ask Tom mailbag –

Question:
In your workshop last week, you stressed the importance of a role description. To be honest, we don’t really have time to write them. We either use an old version from HR, get something off the internet, or use our posting from Craig’s List.

Response:
And, that’s where the trouble begins. The reason we have so much difficulty with issues related to motivation and management is that we don’t accurately define the work. The role description is the cornerstone document –

  • Defines the work, the outputs, the expectations in the role.
  • Organizes the bank of interview questions.
  • Creates the basis for behavioral interview questions.
  • Structures the decision making process for selecting from the candidate pool.
  • Structures the monthly (or more frequent) 1-1 conversation between the team member and the manager.
  • Structures a performance improvement plan, when necessary.
  • Provides grounds for termination, when necessary.

It’s all about the work. Our problems begin when we don’t accurately define the work. What are the decisions to be made, problems to be solved in the role?

Culture as an Accountability

From the Ask Tom mailbag-

Question:
Is culture a Key Result Area (KRA) in a role description?

Response:
Over the past several years, I have come to the conclusion – Yes.

Here are the four absolutes identified by Elliott Jaques required for success (effectiveness) in any role.

  • Capability (time span)
  • Skill (technical knowledge, practiced performance)
  • Interest, passion (value for the work)
  • Required behaviors (contracted behaviors, habits, culture)

Culture is that unwritten set of rules (based on our beliefs and assumptions) that governs the required behaviors in the work that we do together.

While culture impacts everyone in the organization, I find it is a managerial accountability related to setting context. Context is culture, culture is context.

I look for several things from a manager.

  • Awareness of the company’s culture.
  • Ability to communicate the company’s culture in stories and examples.
  • Model behaviors that support the company’s culture.
  • Observe behaviors in others and where appropriate, provide coaching, when necessary, corrective action.
  • Participate in the on-going definition of the company’s culture.

Here is what it looks like in a role description –
Key Result Area (KRA) – Culture
As a member of the management team, the manager will understand and be conversant in the company’s mission, vision and values related to culture.

Accountability – the manager will be accountable for effectively communicating the company’s mission, vision and values. This will include the telling of stories and examples of connected behaviors that support the company’s culture. The manager will be an effective model of those behaviors that support the company’s culture. The manager will be attentive to the behavior of other managers and staff in accordance with the company’s mission, vision and values. The manager will be accountable for coaching, and, where appropriate, taking corrective action. The manager will actively participate in meetings regarding the definition and maintenance of the company’s mission, vision and values, providing constructive input to the definition of the company’s culture.

Send Interview Questions in Advance?

From the Ask Tom mailbag-

Question:
When interviewing for a specific role, is there any benefit to sending at least some of the core interview questions to the candidates prior to the interview so they can be better prepared to provide the specific work examples we are interviewing for?

Response:
What’s the purpose? Every element of the interview protocol must have a purpose. No purpose, don’t do it.

My primary purpose in an interview is to gather truthful data points surrounding the critical role requirements identified in the role description. I connect the dots with data points (step me through the process). I connect to the truth through details and repetitive patterns of response (give me another example).

I hesitate to send interview questions in advance because I am not interested in a story, I am interested in details. Sending the questions, in advance, allows time to create a story with fabricated details. I am not interested in the enhanced resume or exaggerated detail.

I would send the role description. What’s the purpose? The job posting and the role description (two different documents) exist to attract qualified candidates. I need candidates. The job posting creates my candidate pool. The role description self-disqualifies people in the candidate pool.

I want the candidate to look at the role description and say one of two things –

  • I did that.
  • I have no idea how to do that.

I will find out the details in the interview. I will see the patterns in the interview. -Tom

The Role Description is a Design Task

“There’s more?” Ben thought our conversation about role descriptions was finished. “What do you mean next step?”

“What do you think a role description is for?” I asked.

“So the person I hire knows what to do,” Ben curtly replied.

“That’s nice, but not even close,” I paused. “You haven’t hired the person, yet. So, what is the purpose of the role description? Here is a hint. It’s all about you.”

“Me? It’s not my role description.”

“No, but you are the manager. You decide what tasks need to be completed, the appropriate time it will take to complete the tasks, and the effectiveness of the person in the role. Without the role description, you have no idea how to make those decisions. Without the role description, it’s just a noodle mess in your head, a disorganized list of tasks and vague accountabilities. The first purpose for a role description is for you to organize your thinking about the role.”

“And the second purpose?”

“You are about to walk into an interview. Without the role description, you don’t know what questions to ask,” I challenged.

How Many Questions to Ask in an Interview

From the Ask Tom mailbag –

Question:

Yesterday, you talked about how we could evaluate the capability of a team member related to the work.  Your focus was all about the work, calibrating the level of work in the role.  But your evaluation appears to depend on observation of actual work output.  I get it.  But how do we evaluate capability in non-employees, candidates we are interviewing for roles.  Unfortunately, we don’t have the luxury of observation.  We get to ask them questions.  That’s it.  How do we evaluate capability?

Response:

Interviewing candidates and gathering clues on their capability is certainly more difficult than observing team members in actual work output (applied capability).  But the platform is the same, we just have to capture our clues in a different way.

It’s all about the work.  It’s still all about the work.  With internal team members, calibrating capability requires an accurate definition of the work, an accurate definition of the stratum level of work.  In a candidate interview, the cornerstone document is still the role description.

The role description should be organized into Key Result Areas, those tasks and activities that go together, grouped together.  And those tasks and activities that don’t go together, separated from each other.  Most roles have between 5-8 Key Result Areas (KRAs).  This is where the work, the level of work gets clearly defined.

In each KRA, my discipline is to create ten written questions about the work, decisions to be made and problems to be solved in the role.  If you have five KRAs, you will have 50 written questions.  If the role contains eight KRAs, you will have 80 written questions.

And the questions are all about the work.

For every written question that you ask, I expect you to ask two drill down questions.  So, if you have 50 written questions, at the end of the interview, you will have asked 150 questions, all about the work.

In the course of your previous interviews, it is unlikely you have ever asked 150 specific questions about the work contained in the defined role.  If you had, you would have a very clear idea about the candidates capability related to the work, the candidate’s capability related to the level of work.

It’s all about the work.