The Job Description Nobody Reads Until There Is a Dispute

The job description may be the one document nobody looks at until something goes wrong.

At hiring it is prepared, the new employee reads it, signs it, and it goes into a file. In most organizations, that is the end of its working life.

Then the first disagreement happens, and suddenly it is back at the center of the room.

• An employee says: this is not part of my job.
• A manager says: this is part of your responsibilities.
• One department asks another to take on a task, and each side believes it belongs to the other.

At that moment the first question is always the same: where is the job description?

A reference, not a hiring formality

That question reveals what the job description is supposed to be. Not a step in onboarding, but a reference that sets the boundaries of responsibility, reduces overlap between roles, and makes expectations clear between an employee and their manager.

The reality in many organizations is different. The nature of work changes. New systems arrive. Responsibilities are added and others disappear. The employee's role expands. And the job description stays exactly as it was years ago, describing a job that no longer exists in that form.

So when disputes surface, the problem is often not the employee or the manager. The problem is that the reference itself no longer reflects how the work is done.

What a good job description does

In my experience, the most useful job description is not the longest or the most detailed. It is the one that answers two simple questions for every employee:

What is expected of me? And where does my responsibility end?

When those answers are clear:

• there is less room for personal interpretation and misunderstanding;
• cooperation between departments is easier, because handoffs are defined;
• performance reviews are fairer, because people are assessed against something real.

When the description is vague or outdated, each person starts drawing the borders of their own job. That is where many avoidable conflicts begin.

Keeping it alive

This does not require a large project. A few habits change a lot:

1. Write for outcomes, not activities. Five to eight core accountabilities say more than forty bullet points.
2. State decision rights. What can this role decide alone, recommend, or only be consulted on?
3. Review it when the work changes, not only when someone is hired. A restructure, a new system or a new mandate is a trigger.
4. Link it to the job architecture, so grades, pay and career paths rest on the same description.
5. Use it in conversations, at least in the annual review, so it stays a working document rather than an archive.

Two questions I usually ask leaders, and that I would ask you: Are your people still working within their job descriptions? And when were those descriptions last updated?