The Job Role

One of the most damaging assumptions in organisations is that a job
title defines the work.

It does not.

A job title is a label. A job description is often a list. Neither is
enough to create clarity, accountability or meaningful contribution. The
real job role is the practical agreement between the organisation and
the person about why the role exists, what it must produce, what
decisions it can make, what relationships it must manage, and how
success will be recognised.

When this agreement is weak, people drift. They do what is visible,
urgent or politically safe. They protect themselves. They wait for
instruction. They duplicate work, avoid decisions, or become trapped in
activity that looks busy but does not create value.

When the job role is clear, work becomes more coherent. The person
knows where they stand. The manager knows what to support. The team
knows what to expect. The organisation can connect capability to
purpose.

This is why the job role and the job profile matter.

They are not human resources paperwork. They are management
instruments.

The role is not the person

A role and a person are not the same thing.

The role describes the work that must be done for the organisation to
function. The person brings capability, judgement, personality, history,
strengths, weaknesses, energy and ambition into that role.

Good management holds both realities at the same time.

If the organisation ignores the role, work becomes personalised.
Everything depends on who happens to be in the seat. When that person
leaves, the organisation discovers that knowledge, authority and
accountability were never properly designed.

If the organisation ignores the person, work becomes mechanical.
People are treated as interchangeable parts. Their strengths are wasted,
their judgement is suppressed, and the role becomes a cage rather than a
platform.

The best organisations design roles clearly and then allow capable
people to bring those roles to life.

Why the job role exists

Every role should begin with purpose.

Why does this role exist? What would be missing if it did not exist?
What value does it create for the organisation, the customer, the team
or the system?

This question is more important than most job descriptions admit.
Many job profiles begin with tasks. Tasks are useful, but they are not
the reason the role exists. A person can complete tasks and still fail
to create the outcome the role was designed for.

A finance role may exist to protect financial integrity, not merely
to process invoices. A customer service role may exist to resolve
customer friction, not merely to answer calls. A manager role may exist
to create conditions for team performance, not merely to attend meetings
and approve leave.

Purpose gives direction to judgement.

Without purpose, people default to compliance. With purpose, they can
make better decisions when the written process does not cover the
situation in front of them.

Outputs matter more than
activities

A well-designed job role should define outputs.

Activities describe what a person does. Outputs describe what the
work must produce. This distinction is critical.

“Attend meetings” is an activity. “Ensure project decisions are made
with the right information and recorded for action” is an output.

“Call customers” is an activity. “Resolve customer issues in a way
that protects trust and reduces repeat contact” is an output.

“Prepare reports” is an activity. “Give management accurate
information for decision making” is an output.

When roles are defined only by activities, people become busy without
necessarily being effective. When roles are defined by outputs, people
can ask whether the work is producing the intended result.

This does not mean activities are irrelevant. Some activities are
essential. But activities should be connected to the output they
support.

The job profile should therefore make the core outputs visible.

Authority must match
accountability

One of the most common role design failures is to give someone
accountability without authority.

The person is expected to deliver an outcome, but they cannot make
the necessary decisions. They cannot access information. They cannot
influence the people whose work affects the result. They must ask
permission for every meaningful action and are then blamed when progress
is slow.

This creates frustration and organisational dishonesty.

A job role must define authority. What decisions can this person
make? What resources can they allocate? What commitments can they make
to customers, suppliers, team members or other departments? What must be
escalated? What is the boundary between judgement and approval?

Authority does not need to be unlimited. In fact, good role design is
precise about limits. But the authority that is required to produce the
expected output must be explicit.

Accountability without authority is not management. It is
institutionalised helplessness.

Boundaries prevent confusion

Roles need boundaries.

This is not because people should refuse to help outside their job
description. Good organisations need flexibility. People must sometimes
step across boundaries to solve problems, support colleagues and respond
to reality.

But without boundaries, work becomes confused. Two people may think
they own the same decision. No one may own a critical handoff. A manager
may assume a specialist is responsible for an outcome while the
specialist assumes the manager owns it. Teams begin to negotiate
responsibility case by case, and the organisation loses time.

A good job profile defines the edges of the role.

What work belongs here?

What work belongs elsewhere?

Where are the key handoffs?

Which decisions require consultation?

Which relationships must be actively managed?

Where is the role expected to contribute but not own?

Boundaries create freedom because they reduce ambiguity. People can
collaborate better when they know where responsibility sits.

The job profile
should define relationships

No role operates alone.

Every role exists inside a web of relationships: manager, team
members, customers, suppliers, regulators, other departments,
executives, communities, systems and sometimes the public. A job profile
that ignores relationships is incomplete.

The profile should identify the relationships that matter most and
the nature of those relationships.

Does the role advise, approve, coordinate, serve, challenge, support,
sell, govern, design, implement or monitor? Does it require influence
without authority? Does it depend on cross-functional cooperation? Does
it carry customer-facing responsibility? Does it represent the
organisation externally?

Many performance problems are actually relationship-design problems.
A person may have the technical ability to do the work, but the role
requires negotiation, influence, service orientation or stakeholder
management that was never made clear.

The role should describe not only what must be done, but with whom it
must be done.

Competence is more than
qualification

The job profile must define the capabilities required for the role,
but this should be done carefully.

Qualifications matter in some roles. Licences, professional
standards, technical knowledge and formal education may be essential.
But competence is broader than qualification.

Competence includes knowledge, skill, judgement, behaviour, values,
experience and the ability to perform under the conditions of the role.
A person may have the formal qualification but lack the practical
judgement. Another person may have deep experience but need formal
development to close a technical gap.

A good job profile distinguishes between:

Essential qualifications.

Technical skills.

Behavioural competencies.

Experience requirements.

Decision-making capability.

Learning requirements.

This distinction matters because hiring, promotion and development
decisions become stronger when the organisation knows what capability is
truly required.

If the role requires judgement under pressure, say so. If it requires
analytical thinking, say so. If it requires empathy with customers, say
so. If it requires the ability to work with ambiguity, say so.

Do not hide real requirements behind generic phrases.

Measures must
reflect the purpose of the role

Job profiles often fail because the measures do not match the role’s
purpose.

If the role exists to improve service quality, but the person is
measured only on speed, quality will suffer. If the role exists to build
relationships, but the person is measured only on transaction volume,
trust will suffer. If the role exists to manage risk, but the person is
measured only on growth, the organisation may create dangerous
behaviour.

Measures teach people what the organisation really values.

A job profile should therefore identify the outcomes by which the
role will be judged. These measures should be specific enough to guide
performance, but not so narrow that they encourage mechanical
behaviour.

Good measures combine quantity, quality, timeliness, customer impact,
risk, learning and contribution to the broader system.

The role profile should help the manager and employee have a clear
conversation about success.

What must be delivered?

How will we know it is good?

What trade-offs must be managed?

What behaviours matter in achieving the result?

What evidence will we use?

Performance management becomes far more constructive when the role
has been properly defined.

The role must connect to
strategy

A role is not only a local task. It is a contribution to
strategy.

Every job should connect, in some way, to what the organisation is
trying to achieve. The connection may be direct or indirect, but it
should exist. If people cannot see how their role matters, they are more
likely to experience work as a set of demands rather than a meaningful
contribution.

This is especially important in larger organisations where work can
become fragmented. People may process, check, capture, approve, respond,
reconcile, schedule, monitor or report without seeing the line between
their work and the customer, citizen, student, patient or strategic
outcome.

Managers must make that line visible.

The job profile can help. It should show how the role contributes to
the team, the function and the organisation’s larger purpose. This is
not motivational decoration. It is operational clarity.

People make better decisions when they understand the purpose behind
the work.

The role changes
as the organisation changes

Roles are living agreements.

Organisations change. Customers change. Technology changes.
Regulations change. Teams change. Strategy changes. A role that made
sense three years ago may now be misaligned with the work that actually
needs to happen.

This is why job profiles should not be written once and
forgotten.

They should be reviewed when the strategy changes, when performance
problems repeat, when people complain about unclear responsibilities,
when technology changes the work, when a role becomes overloaded, when
handoffs fail, or when recruitment repeatedly produces the wrong
candidates.

A static job profile in a changing organisation becomes fiction.

But constant informal change is also dangerous. If the role changes
without being named, the person may carry more responsibility without
support, authority or recognition. The organisation may create hidden
work that never appears in planning or resourcing.

Role change should be deliberate.

How job profiles should be
used

A job profile should be useful across the employee lifecycle.

In recruitment, it should help the organisation attract people who
understand the real work, not only the attractive title. It should make
the expectations honest.

In selection, it should guide interviews, assessments and reference
checks. The organisation should test for the capabilities the role
actually requires.

In onboarding, it should help the new employee understand purpose,
outputs, relationships, authority, measures and early priorities.

In performance management, it should anchor conversations about what
is working, what is unclear, what support is needed and what outcomes
are expected.

In development, it should show the gap between current capability and
future contribution.

In succession planning, it should help the organisation understand
which roles are critical and what kind of readiness is required.

In organisational design, it should reveal duplication, gaps,
overload and unclear accountability.

If a job profile is used only for filing, it is failing.

The manager’s responsibility

The manager cannot outsource role clarity to human resources.

Human resources can facilitate the process, ensure consistency,
provide frameworks and help with governance. But the manager must
understand the work well enough to define the role properly.

The manager should be able to explain:

Why the role exists.

What outcomes matter most.

Where the role has authority.

Which relationships are critical.

What capability is required.

How success will be measured.

Where the role is likely to experience tension.

What support the person will need.

If the manager cannot explain these things, the employee will have to
discover them through frustration.

That is poor management.

The employee’s responsibility

Role clarity is not only the manager’s responsibility.

Employees must also engage with their roles intelligently. They
should ask questions, test assumptions, clarify priorities and
understand how their work affects others. They should not hide behind
the job description when the situation clearly requires judgement, but
they should also not silently absorb work that destroys their core
contribution.

A mature employee can say:

This is what I understand the role to require.

These are the outputs I believe matter most.

These are the decisions I think I can make.

These are the areas where I need clarity.

This is where the role has changed.

This is the support I need to deliver properly.

Such conversations create adulthood in the organisation. They move
the role from a document to a working agreement.

The cost of role ambiguity

Role ambiguity is expensive.

It creates duplication because several people do the same work. It
creates gaps because everyone assumes someone else owns the issue. It
slows decisions because authority is unclear. It creates conflict
because boundaries are negotiated emotionally. It weakens performance
management because expectations were never properly defined.

It also harms people.

When people do not know what is truly expected, they become anxious.
They default to what is easiest to measure. They overwork to prove
commitment. They avoid initiative because they fear overstepping. They
protect their time instead of contributing their best thinking.

Over time, role ambiguity becomes disengagement.

People may stay, but they stop bringing themselves fully to the
work.

A job role is a platform

A well-designed job role is not a cage.

It is a platform.

It tells a person where they stand, what matters, what they own, how
they contribute and where they can exercise judgement. It gives enough
structure to create accountability and enough space for initiative,
learning and growth.

The best job profiles do not reduce people to tasks. They create the
conditions in which people can contribute with clarity.

This is the difference between a bureaucratic document and a
management instrument.

A bureaucratic job description protects the organisation from
uncertainty.

A useful job profile helps the organisation and the person create
value together.

When organisations understand this difference, they stop treating
roles as static boxes on an organogram. They begin to see roles as
living points of contribution inside a larger system of work.

That is where real performance begins.