Role Clarity Beyond the Job Title

By Dr Riaan Steenberg

A job title is not a job role.

A title tells people where to place someone on an organisational
chart. A role tells the person what contribution is required, what
decisions they may make, what standards they must uphold, and how their
work connects to the wider system.

Many organisations confuse the two. They hire a title, write a job
description, and assume clarity has been created. Then performance
problems appear and everyone is surprised.

The surprise is usually unnecessary. The role was never properly
designed.

The Role Is a Contract
of Contribution

A useful job role answers a practical question: what contribution
must this person make for the organisation to work better?

That contribution has to be more precise than a list of tasks. Tasks
describe activity. Contribution describes value.

A finance manager does not merely produce reports. The role exists to
create financial visibility, protect discipline, and improve the quality
of decisions. A team leader does not merely allocate work. The role
exists to create focus, remove friction, build capability, and ensure
delivery.

When the contribution is unclear, people retreat into activity. They
become busy without becoming effective.

Three Layers of the Role

Every role has three layers.

The first layer is formal responsibility. These are the duties,
outputs, compliance requirements, and reporting lines that must be clear
enough to prevent confusion.

The second layer is decision authority. What may this person decide
without escalation? What must they recommend? What must they never
decide alone?

The third layer is contextual judgement. This is the part most job
descriptions miss. It asks how the role must respond to the
organisation’s current stage, pressure, culture, and strategy.

A role in a growing business is not the same as the same title in a
mature business. A role in crisis is not the same as a role in
stability. The title may remain identical while the contribution changes
completely.

The Cost of Vague Roles

Vague roles create expensive behaviour.

People duplicate work because boundaries are unclear. Decisions rise
unnecessarily because authority is not trusted. Accountability becomes
emotional because nobody can point to the original agreement. Talented
people become frustrated because they cannot see how to win.

The organisation then tries to solve a design problem with
motivation. It asks people to communicate better, collaborate more, or
show ownership.

Those requests may be valid, but they are incomplete. People cannot
show ownership over a role that has not been properly defined.

Design the Role
Before Judging the Person

Before concluding that someone is underperforming, examine the
role.

Is the expected contribution explicit? Are the decision rights clear?
Are the success measures meaningful? Does the person have the authority,
information, and relationships needed to do the work? Has the role
changed without being renegotiated?

This is not an excuse for poor performance. It is a fairness
test.

A well-designed role makes performance easier to discuss because the
conversation moves from personality to contribution.

The Living Role

Roles should not be static documents stored in a folder.

They should be reviewed when strategy changes, when the team grows,
when a new manager arrives, when recurring conflict appears, or when the
same decision keeps getting escalated.

A living role has enough stability to create accountability and
enough flexibility to remain relevant.

The best organisations treat role clarity as part of management
architecture. They understand that performance is not produced only by
talented people. It is produced by talented people working inside clear
structures.

A Simple Test

Ask each person three questions.

What are you here to contribute?

Which decisions are yours?

How will we know that your role is working?

If the answers are vague, the role is vague.

And if the role is vague, management work remains unfinished.