Role Clarity: The Hidden Operating Problem Behind Growing Teams

Role clarity sounds like a soft topic. It is not. It is the input to almost every operating decision a company makes: who is asked, who decides, who is accountable when something is missed, and what a performance conversation can reasonably be about.

It is also invisible. No leadership team meets to discuss the fact that roles are unclear. They meet to discuss why a project slipped, why two teams built the same thing, or why a strong performer resigned unexpectedly. Role ambiguity is upstream of all three.

How unclear roles present

The symptoms are consistent enough to use as a diagnostic. If you recognise three or more of these, the problem is probably definitional rather than behavioural.

• Decisions circulate. A question moves between three people, each of whom thinks someone else should own it, and eventually reaches a founder who resolves it in four minutes.
• Work is duplicated at the edges. Two teams solve the same problem because the boundary between them was never drawn.
• Meetings grow. People are invited defensively, because nobody is sure whose decision it is and being absent is riskier than attending.
• Performance conversations lack evidence. A manager wants to raise an issue and cannot point to what was expected, because it was never stated.
• New joiners take a quarter to become useful. Not because the work is hard, but because the map exists only in conversation.

Job descriptions are not role definitions

Most companies have job descriptions. They were written for recruitment, they list activities, and they are read once. A role definition is a different document with a different purpose: it is read by the person doing the job, by their manager, and by everyone who has to work with them.

A one-page format that works

Length is the enemy here. A role definition that runs to three pages will not be maintained, and an unmaintained definition is worse than none because people cite it selectively. Five sections, one page.

1. Purpose. One sentence: why this role exists, in terms of what would go wrong without it.
2. Outcomes owned. Three to five outcomes this person is accountable for. Not activities — results, stated so that success is verifiable.
3. Decisions held. What this person decides without approval, what they decide after consulting a named role, and what they recommend but do not decide.
4. Key interfaces. The three or four roles this one must work with, and what each side owes the other.
5. Level. Which level this role sits at, and what that means for scope, autonomy and complexity.

The third section is where the value is and where most drafts go soft. "Involved in pricing decisions" is not a decision right. "Approves discounts up to 15%; above that, recommends to the Commercial Director" is.

Do the interfaces, not just the roles

A set of individually clear roles can still produce an unclear organisation. What sits between them — the handoffs, the shared outcomes, the sequences that cross two teams — is where most delay lives in companies past fifty people.

For the three or four interfaces that carry the most volume, write down what is handed over, what "ready" means, who accepts it, and what happens when it arrives incomplete. This takes an afternoon and it removes a recurring category of argument.

Keep it current or do not bother

Role definitions decay. The work changes, the structure shifts, someone takes on an outcome informally and it never gets written down. A definition that is eighteen months old is actively misleading.

Two habits keep them alive without creating an administrative burden. First, review the role definition in the same conversation as the goal-setting cycle, once or twice a year. Second, whenever a decision is escalated twice for the same reason, treat it as a signal that a decision right is missing and fix the definition rather than the instance.

The cost of unclear roles is paid in the leadership team's calendar. Every ambiguity that is not resolved on paper is resolved in a meeting.

Where to start

Do not attempt the whole organisation. Start with the ten roles closest to the delays you are currently experiencing — usually the layer directly beneath the leadership team, where scope grew fastest and definitions were never revisited.

Done properly, this is a two to three week exercise with a disproportionate effect. It is also the natural first step before any of the broader organisation work we do, because it frequently reveals that the structure is adequate and only the ownership inside it was never stated.