There’s a version of every role that exists on paper.
And then there’s the version that exists in reality.
For most small and growing businesses, those two things have quietly drifted apart in more recent times.
The job description still lists responsibilities, reporting lines and required skills. It looks structured. Clear. Considered.
But day to day, the work tells a different story. Priorities shift. New tools are introduced. People step in where needed. Tasks evolve without ever being formally redefined.
Over time, the gap between what a role is and what it says it is starts to widen. And while that might seem harmless, it’s often where performance issues, frustration and stalled career development begin.
When roles stop reflecting reality
In many SMEs, job descriptions are created at the point of hiring and then left untouched.
That might have worked when roles were more stable, but it doesn’t hold up in environments where:
- teams are lean and constantly adapting
- employees take on responsibilities beyond their original scope
- new systems or AI tools change how work gets done
- business priorities shift faster than documentation can keep up
What starts as flexibility can quickly become ambiguity.
People are contributing more, but not always in ways that are visible or recognised. Managers are relying on output as measurement, but without a shared understanding of what the role actually encompasses anymore.
And over time, this creates a quiet but significant disconnect.
Why this matters more than it seems
When a role isn’t clearly defined in its current state, it affects more than just clarity.
It starts to shape how people experience their work.
- Performance becomes harder to measure
Expectations are implied rather than agreed, which leads to inconsistency and second-guessing. - Career development stalls
If the role hasn’t been updated, neither has the pathway forward. People can’t see how they’re progressing, even if they’re doing more. - High performers feel it first
They’re often the ones picking up additional responsibilities, solving problems, and stretching beyond their remit. Without recognition or structure, this can quickly turn into frustration. - Managers default to reactive conversations
Instead of proactively guiding growth, discussions happen when something goes wrong or when someone starts to disengage.
What’s often labelled as a “performance issue” or “lack of engagement” is, in many cases, a role design issue.
The shift: from job descriptions to role design
The organisations navigating this well aren’t abandoning structure altogether.
They’re just approaching it differently.
Instead of treating job descriptions as static documents, they’re focusing on role design as an ongoing process.
That shift looks like:
- Defining outcomes, not just tasks
Moving beyond lists of duties to clarify what success in the role actually looks like. - Clarifying areas of ownership
Who is responsible for what, even as tasks evolve. - Acknowledging that roles will change
Building in the expectation that responsibilities will shift, and making that visible. - Linking work to growth
Helping employees understand not just what they’re doing, but how it’s building their capability.
This isn’t about adding more process. It’s about making what’s already happening more intentional.
What this can look like in practice
For SMEs, this doesn’t need to be complex or time-consuming. Small shifts can make a meaningful difference.
A few practical ways to start:
- Quarterly role check-ins
A short conversation focused on how the role has evolved. What’s been added? What’s changed? What no longer applies? - Updating responsibilities in real time
Keeping a simple, shared record of current responsibilities rather than relying on the original job description. - Making growth visible
Connecting new responsibilities to skill development or progression, even if titles aren’t changing. - Creating space for clarity
Giving employees the opportunity to ask: Is this still my role? and What does success look like now?
These aren’t formal HR exercises. They’re practical conversations that bring alignment back into the day-to-day.
A more useful way to think about roles
The idea that a role can be fully captured in a static document is becoming harder to sustain.
Work is more fluid. Tools are evolving. Expectations are shifting faster than most documentation can keep up with.
That doesn’t mean structure is less important. If anything, it matters more.
But the structure needs to reflect reality.
When roles are actively designed rather than passively documented, something shifts.
People understand what they own. They can see how they’re growing. Conversations become clearer. Progress becomes visible.
And perhaps most importantly, employees can see a future in the role they’re already in.
Because career development is about setting an employee up for a promotion, but instead, setting them up with the understanding of how their work is evolving, and where it could take them next.