← BackSee all toolsThe Operating Backbone and Role-Based AuthorityWorking demo · sample data · shows a method I used, not a real event
Operating model · authority

The Operating Backbone and Role-Based Authority

Six tests for whether a company has an operating model, and a way to attach process authority to the role, not the person.

I used this approach to move a project-driven company toward a repeatable operating model. The scenarios and card are illustrative.

The six parts

What an operating backbone is made of.

A company that grew by projects usually has no governing operating model. Information sits in pockets, and each team does well what its own manager asks. These six tests show how much backbone exists.

01

Predictable execution

Does the same input produce the same path?

Test: hand two people the same case and compare what they do.
Sign of failure: every case becomes a custom project.

02

Clear ownership

Can anyone name the one owner of this step?

Test: ask three people who owns it. Count the answers.
Sign of failure: “I stepped in to help.”

03

Clear handoffs

Is the receiving team told, and do they get what they need?

Test: check the last ten handoffs for missing fields.
Sign of failure: finance finds out after the customer does.

04

System-of-record truth

Is there one home for each fact?

Test: change a fact once and see where it has to be re-typed.
Sign of failure: every team keeps its own version.

05

Automation-ready design

Are steps defined well enough that software can run them?

Test: could a checklist run this without judgement?
Sign of failure: automating a step nobody can describe.

06

KPI governance

Does each metric have a definition, an owner and a decision it drives?

Test: for each metric, name the decision it changes.
Sign of failure: dashboards nobody acts on.

Authority

Attach authority to the role, not the person.

Borrowed from a military idea: a billet is a position with duties and authority, whoever fills it. Choose where authority sits and pick a scenario to see what happens to a process.

Authority sits with…

Scenario

Holds

The process keeps its standard.

The artifact

A billet card for a process owner.

One page per role. Illustrative content.

FieldWhat the role card says
RoleProcess owner, intake and handoffs
OwnsThe written standard and its definitions of done
Can decideRequired fields, gate criteria, SLA clocks, routing
Cannot decidePricing, contract terms, anything outside the process
ExceptionsRequested in writing; approved by the role holder; logged
EscalationOne named executive, with a 48-hour clock
DeputyNamed, trained on the playbook, same authority
ReviewEvery quarter against the metrics it owns

More in Operating Model & Governance

See all tools