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.
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
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.
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.
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.”
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.
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.
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.
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
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
The artifact
One page per role. Illustrative content.
| Field | What the role card says |
|---|---|
| Role | Process owner, intake and handoffs |
| Owns | The written standard and its definitions of done |
| Can decide | Required fields, gate criteria, SLA clocks, routing |
| Cannot decide | Pricing, contract terms, anything outside the process |
| Exceptions | Requested in writing; approved by the role holder; logged |
| Escalation | One named executive, with a 48-hour clock |
| Deputy | Named, trained on the playbook, same authority |
| Review | Every quarter against the metrics it owns |
More in Operating Model & Governance
See all tools