Skill

Assign role accountabilities and escalation paths

Defines which abstract role owns client relationship, quality, and day-to-day delivery, plus decision rights and escalation paths between roles — for the role set, not named individuals.

In / outRole catalogue + seniority model → accountability matrix (ownership per function, decision rights, escalation paths per role)

You might say…

We need a clear chain of accountability set up before names go in the boxes — otherwise the org model is just a vanity chart.

What it does

Defines which role owns the client relationship, which owns quality, and which owns day-to-day delivery, plus the decision rights and escalation paths between roles in the abstract (not for named people). Used alongside the seniority shape to produce the team's accountability model. Single judgement over the role set.

Trigger: Use alongside seniority shape design to produce the team's accountability model before staffing specific people.

Recognise the problem?

The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.

Start a conversation