Chapter 1
Set direction
Translate purpose and customer needs into priorities and boundaries.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Agree three measurable operating priorities. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 2
Clarify ownership
Assign decision rights, roles, escalation and cover.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Name one accountable owner for every critical process. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 3
Control delivery
Define inputs, steps, acceptance, records and exceptions.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Observe one real delivery and correct the documented process. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 4
Manage risk
Use risks to change controls and decisions, not decorate registers.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Test the top three risks against current controls. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 5
Measure performance
Choose a small set of indicators connected to quality, timeliness, cash and outcomes.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Remove metrics that do not trigger a decision. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 6
Improve deliberately
Connect feedback, incidents, root causes and management review.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Close one recurring problem through corrective action. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.