In most organizations I have worked with, the job description is written once — when there is a vacancy to advertise. After that it sits in a folder and nobody returns to it: not the manager, not the person, not the review meeting.
That is not an accident. A document written to attract candidates is not built to work with afterwards. An advert has to appeal broadly; a role definition has to be precise and draw lines. Those two purposes do not fit in one text.
A task list is not a role
A task list says what someone does. A role definition says what they are answerable for — which is to say, whose question it is when something goes wrong. The first gets longer as work is added. The second gets sharper as responsibility becomes clear.
The difference shows up where two people each assume something belongs to the other. A task list cannot settle it, because the task may be missing from both lists and neither person has misrepresented anything.
Four things a usable role definition contains
Outcomes, not activities
“Follow up with clients” is an activity, and any amount of it can be defended. “Active clients answered within twenty-four hours” is an outcome, and it can be discussed. That single change removes most of the ambiguity from a review conversation.
The decision boundary
Make explicit what this role decides, what it proposes, and what it simply executes. The absence of that distinction is behind most complaints expressed as “I have no authority” or “everything has to come through me”.
Dependencies
Every role depends on outputs from other roles. When that is unwritten, a delay elsewhere is recorded as underperformance here. Writing it down reduces the friction and also shows where to fix it.
What success looks like in ninety days
Not annual objectives — something observable inside the first quarter. It gives the person direction and lets the manager learn early whether the appointment was right.
Why this keeps getting postponed
Because the benefit is delayed. Not writing it costs nothing today, and six months later it surfaces as an awkward review, a poor internal move or an unexpected resignation — by which point nobody connects it back to the job description.
In small companies the usual argument is that everyone does everything. That is true up to a point, and it becomes expensive at exactly the moment the team passes five people: the flexibility that was an advantage at four reads as ambiguity at twelve.
Define the role while there is still no dispute. After a dispute, any definition is read as taking sides.
Where to start
You do not have to redefine the whole organization at once. Take the one role producing the most friction right now and write those four sections for it — preferably with the person, not about them. If you hit a disagreement while writing, that disagreement is what has been costing you.