6
Components in the finished document
Playbook / SOP
How the team does the thing without me in the room, written at the grain a competent person can follow unsupervised.
Where This Sits
0
Measured directly, not asserted
6
Pieces that carry my judgment
This is a Enablement deliverable, which means it transfers the judgment. It is the unit of scope: it can be commissioned on its own, priced on its own, and accepted on its own, whether or not anything else is bought alongside it.
It is not a package and not a retainer. It is one document with 6 components, and the list below is the whole of it.
What Is Inside It
Every component is listed with the one sentence that says what it is. They are grouped by how each one is produced, because the difference between a number a tool gave me and a number I decided matters more than most reports admit.
Judged
My reading of the evidence. This is the part you are actually paying for, and the part you are entitled to argue with.
- Decision tree
- The branching logic for a recurring judgement, written so someone else reaches the same answer.
- Step checklist
- The ordered actions for a recurring task, at the grain a competent person can follow unsupervised.
- Worked example
- One real case carried through the process end to end, including the parts that were ambiguous.
- Template or boilerplate
- The reusable starting file for a recurring output, pre-structured so quality does not depend on memory.
- Escalation criteria
- The specific conditions under which someone must stop and ask rather than proceed.
- Glossary
- Plain definitions of every technical term used, so the document survives being forwarded to someone non-technical.