How unclear ownership shows up
A decision is repeatedly escalated because no one is confident they can make it. Two teams produce similar reports. A customer issue moves between functions while each waits for the other to act. These can look like individual performance problems when the real issue is how responsibilities and decisions have been designed.
The cost is not only time. Ambiguity creates frustration and makes it harder to hold anyone fairly accountable for a result.
Look beyond the position description
A role review should start by tracing the important work: what outcome is needed, which decisions are required and where information passes between teams. Compare that reality with the formal structure, job descriptions and actual capacity. Ask people doing the work where ownership becomes uncertain.
- Which outcomes have one clearly identified owner?
- Where do roles overlap without a defined decision maker?
- Which decisions are routinely referred upwards?
- What work has changed since the roles were last designed?
What clearer roles can look like
The answer may involve explicit decision rights, a simpler hand-off, a revised span of control or a role redesigned around current demand. It should also specify the input other teams provide and how exceptions are handled. A chart and position descriptions should reflect the operating decisions, rather than stand in for them.
CLEAR reviews roles alongside structures, resources and processes. The aim is practical accountability: people know what they own, leaders can make timely decisions and the business can see whether the change helps. Where a redesign affects employees, thoughtful consultation and appropriate specialist advice remain part of implementation.
First question to ask: Pick a decision that stalled last month. Who believed they owned it, who actually decided, and what had to happen in between?
Use the role-clarity exercise to map one decision and test the handoff.
What a role clarity review produces
We begin with one or two decisions or workflows that are causing friction, then compare the written roles with the work people actually do. The review identifies where ownership overlaps, where authority is missing and which tasks have drifted into a role over time.
The output is a practical responsibility map: the outcome each role owns, the decisions it can make, the input it needs from others and the point at which an exception should be escalated. If a role needs redesign, we describe the work before rewriting the position description and plan how to introduce the change with the people affected.
For a smaller business, that might free the owner from approving routine decisions. In a larger organisation, it might clarify a handoff between functions or management layers. The measure of success is whether work moves and decisions are made more reliably, not whether the new chart looks simpler.