When employees are unclear about their responsibilities, the obvious answer is often: “We need better job descriptions.”
Sometimes that is true.
But a job description can only describe a role after the organisation has made the more important decisions around it. If reporting lines, accountabilities and decision rights are unclear, rewriting the document may simply describe the confusion more neatly.
Real role clarity is broader than a list of duties.
A job description answers only part of the question
A useful job description can explain:
- the purpose of the role;
- key responsibilities;
- reporting relationship;
- important requirements or capabilities;
- expected outputs or areas of accountability.
That is valuable. But employees also need to understand how their role relates to other roles.
Who has the final decision? Who is consulted? Who owns the outcome when two functions are involved? What happens when priorities conflict? Which decisions can the role make without returning to a more senior person?
Those questions usually sit outside a conventional job description.
The difference between a task and an accountability
Job descriptions often become long lists of activities:
- prepare reports;
- attend meetings;
- follow up with customers;
- maintain records;
- support the team.
Activities describe what a person may do. Accountability describes what the organisation expects the role to own.
For example, “prepare the monthly sales report” is an activity. “Ensure leadership has accurate monthly sales-performance information by the third working day” is closer to an accountability because it describes an outcome and ownership.
A strong role needs both enough practical detail to be understandable and enough outcome clarity to support real management.
Reporting lines matter
A job description may state that an employee reports to the Operations Manager. That still does not tell us whether Finance, Sales or another function can assign work directly to the role, who resolves conflicting priorities or where certain approvals sit.
In small organisations, informal working relationships often grow around the formal reporting structure. That is not necessarily a problem.
The problem is when the informal system becomes the only system and different people carry different assumptions about authority.
Role clarity therefore requires the organisation to look at reporting relationships as well as the individual role document.
Decision rights matter even more as the company grows
In a founder-led business, employees often know that the founder is the final answer.
As the organisation grows, that becomes a bottleneck. Managers may receive new titles without receiving clear decision authority. The founder then remains involved in routine approvals because everybody is trying to avoid making the wrong call.
A job description that says “manage the team” does not resolve that.
The organisation needs to decide what the manager can approve, what must be escalated and what decisions belong elsewhere.
That is a design question.
Overlap between roles needs to be resolved, not hidden
Two roles can each have reasonable job descriptions and still overlap significantly.
For example, Operations may believe it owns vendor management while Finance believes vendor approval sits entirely with Finance. HR may believe managers own performance conversations while managers expect HR to run the whole process.
If both roles are written independently, the overlap can remain invisible until a disagreement occurs.
Organisation design looks across roles and asks how the work connects.
Role clarity also supports better performance management
Managers cannot fairly assess performance if the organisation has not clearly defined what the employee is expected to own.
This is one reason businesses sometimes struggle with KPIs. They start by trying to find measurable targets before deciding what the role is genuinely accountable for.
The sequence should normally be:
- clarify the purpose of the role;
- define key accountabilities;
- resolve reporting and decision rights;
- identify meaningful performance outcomes; and
- then select measures that help assess those outcomes.
A KPI should not be used to compensate for an unclear role.
What good role clarity looks like
An employee should be able to answer:
- Why does my role exist?
- What outcomes am I accountable for?
- Who do I report to?
- Which decisions can I make?
- Where do I depend on another role?
- What needs to be escalated?
- How will my performance be judged?
A manager should be able to answer the same questions about the roles in the team.
If the job description exists but those answers remain unclear, the organisation does not yet have full role clarity.
The practical takeaway
Better job descriptions are useful. They are often necessary.
But they should be the written expression of a clear organisation design, not a substitute for one.
If the business is experiencing duplicated work, slow approvals, repeated role conflict or performance confusion, the right starting question may be bigger than “Do we need to rewrite our job descriptions?”
It may be: Have we actually decided how this work should be organised?
Organisation Design & Role Clarity
Related article: When a Growing Business Needs Organisation Design