Role clarity and accountability without title inflation

1. The outcome. One sentence naming what the role is answerable for producing. Two outcomes usually means two roles that have been combined on paper rather than in work.
2. The decisions. What the holder may settle alone, what needs agreement, and the limits on each.
3. The dependencies. What the role needs from others to succeed, and what others need from it. These are the interfaces that produce most friction.
4. The measures. What the role is judged on, ideally the same figures that appear on the scorecard the business reviews.
5. The exclusions. What the role is not responsible for. This is the part most often missing and the part that resolves arguments.

Ambiguity is easier to locate from symptoms than from structure. Three signals are reliable: work that stalls while people wait to find out who owns it, decisions that get made twice by different people, and conversations that turn into a discussion of who should have been involved.

• List the recurring decisions in a normal month. Anything with no clear owner is a boundary problem.
• Ask each manager what they can decide without asking anyone. Compare the answers with what they actually do.
• Look for roles that have absorbed a function quietly, usually after a departure or a new system, and are now measured on the old outcome.

This takes a few hours and produces a specific list. Starting from a structure chart usually produces a reorganisation instead.

A useful role document for a business of any size fits on a page: the outcome, the decisions, the interfaces, and the exclusions. Where two roles meet, the document should say who decides when they disagree. That single sentence prevents a category of recurring friction that no amount of seniority resolves cleanly.

Decision rights and role clarity are different documents with the same purpose. The notes on decision rights and delegation cover how to set the limits that make the role's authority real.

• Titles describe seniority; accountability describes who answers for an outcome.
• Creating a title to solve an ambiguity usually adds a role without removing the overlap.
• Where someone is accountable for an outcome they cannot influence, the problem is the role's authority, not its name.
• Where two people share an outcome, one of them must hold the decision. Accountability is not divisible in practice, even when it is in a document.

The example below is hypothetical and describes a pattern rather than a client engagement.

• Definitions can outpace the work. A role document written once and never revisited describes a business that no longer exists. The review trigger matters more than the format.
• Over-specification slows small teams. Where five people do everything, a page per role is a burden. One page for the team's boundary decisions is usually enough.
• Clarity exposes capability gaps. Once a decision has an owner, it becomes visible when it is not being made. That is useful and uncomfortable in equal measure.
• It does not fix a mismatched structure. Where a role genuinely owns three unrelated outcomes because the business is under-resourced, clarifying the boundaries will show the strain rather than relieve it.

Role definition and accountability sit inside the Leadership & People capability, alongside decision rights and the management rhythm that reinforces both. Where the ambiguity sits between sales and delivery, the notes on the sales-to-delivery handoff cover the boundary in more detail.