Managers don't like to write job descriptions; which means they won't do them, will procrastinate endlessly or will delegate the responsibility to almost anyone else. If pushed into a corner many will simply throw together a half-hearted effort that is quickly flagged by its poor quality.
And that's for new descriptions. Showing similar distaste managers won't be interested in recommendations to periodically update whatever they already have on file.
When faced with a compulsion from HR, a typical response of passive resistance would be to take a minimalist approach, providing only the least acceptable product, so they could check this onerous duty off their to-do list and get back to more important work.
Why is that? Why is the lowly job description document considered as popular as a mafia lawyer or a used car salesman? Why do so many managers consider preparing a job description a thankless task, one they often delegate to the less informed and those even less interested?
The Manager's Favorite Kicking-Boy
How many reasons can you identify with?
- HR formatting: A common criticism is that the "forms control staff" has designed an either complex or lengthy (often both) document that demands answers to questions that go well beyond "what does the job do?"
- It takes too long: Managers can more easily verbalize a job's tasks or accountabilities than they can put pen to paper. Description preparation is considered a laborious process.
- Better writers get a better deal: A belief that those more comfortable with writing (can turn a better phrase) will receive better/higher salary grades and pay. The fear is that prose will trump content.
- No time: Managers will tell you that they always have better things to do; namely activities that more directly relate to advancing the needs of the business.
So why do we need the darn things in the first place? Why do we periodically turn our managers into administrators? Because, contrary to populist sarcasm outside of HR, those descriptions do perform several important functions.
- Job description: (duh!) A description of the role and responsibilities of the job holder, to explain what activities should be taking place.
- Job evaluation: To assist in determining which job is more important. Evaluators use the descriptions to help measure the internal value of each job, one to another.
- Market pricing: Ensures that when the Analyst is reviewing competitive pay practices, like jobs are matched.
- Performance appraisal: Helps both the employee and the manager know with specificity what activities (and results) are expected from those performing a job.
- Organization structure: The description aids a manager in establishing why a job is needed and how it differentiates from other jobs. It provides the justification to create a position or hire a new employee.
Thus, we see that the simple fact of describing the job generates several ongoing benefits to the company. Let the debate continue about formats, word count and other compensable factors, but most would agree - you really need to describe what performance you're prepared to pay for.
The Cost of Getting it Wrong
What happens when the balance of importance vs. distaste is skewed, when descriptions are carelessly slapped together, left in a closet to go out of date or simply ignored as new/revised jobs are established? How bad can it get?
It can get to be an expensive dilemma.
- Incorrect job evaluation: You get the grade wrong. Typically erring on the high side when descriptions are vague, outdated or filled with puffery results in artificially higher grades. That action pushes up fixed costs (pay), without a corresponding increase in value received (performance).
- Mismatch in market pricing: Like the above, incorrect matching could hand the job a higher price tag than warranted by actual responsibilities. Again, costs go up.
- Title inflation: When definitions are vague or too like other jobs the environment becomes ripe for "throwaway titles", meaningless designations meant to placate employees. The trouble is, this insidious practice worsens employee discomfort over time, while also raising compensation costs.
Personally, I don't like job descriptions either and hate to write them. But I recognize that they're good for me and for the business. So, here are a few tips 'n tricks to help you swallow a sometimes bitter pill.
- Keep it simple and keep it short. Focus on major tasks or accountabilities. More than two pages can be overkill.
- Write the "Basic Purpose" last. Don't start with it. Trust me, the task is easier that way.
- Get yourself a resource library that carries a host of pre-written benchmark descriptions. Either in book form or better - go online. Now the task is editing, not creation.
- Don't have the employee write the description. Too much chance for bias creep and unintended influences. It's a manager's responsibility.
- Consider an annual review to keep content current. Such is a small project if maintained, but eventually a large one if ignored.
The bottom line? It's ok to hate job descriptions (a salve to my conscience) if they are given the proper attention and respect. The benefits do outweigh the hassle.
Chuck Csizmar CCP is founder and Principal of CMC Compensation Group, providing global compensation consulting services to a wide variety of industries and non-profit organizations. He is also associated with several HR Consulting firms as a contributing consultant. Chuck is a broad-based subject matter expert with a specialty in international and expatriate compensation. He lives in Central Florida (near The Mouse) and enjoys growing fruit and managing (?) a clowder of cats.
Creative Commons image "Abandoned Cats," by Stefan Tell
Recent Comments