My beef with job descriptions stems from that simple, yet toxic, saying. I agree that it helps one in saying no to unrelated tasks and stopping project scope creep, but too frequently it is used as a shield you hide behind when faced with change or new business.
What happens when a new project or initiative comes up at work that we both agree needs to be done? It’s not in your job description and it’s not in my job description, so does the work just not get done then?
Similarly, are you cautioning your team not to take initiative or work on larger projects because you fear that the work “isn’t in their job description?” Who needs career development opportunities or people who are passionate about their work anyway right?
A job description is definitely helpful for recruiting and hiring your staff. But don’t fall into the trap of trying to use it to motivate and manage them once they have signed the dotted line. You’re better than that!
Pick of the post: Slow Club – When I Go
No related posts.
2 comments
ms eyre says:
July 11, 2009 at 10:05 am (UTC 1)
Every JD has the line "other duties as needed". Point that out. Then tell them to talk to me. Mine is all "other duties as needed". That is what makes it fun.
–Dianna
ntippe says:
July 11, 2009 at 2:33 pm (UTC 1)
So true. The job descriptions also limit one's ability to follow their passion, which on the job, can be extremely demotivating. And it works both ways- managers/directors may not ask for certain duties to be completed by an employee if said task doesn't fall into their JD.