Operating model · Phase 03
Built to reduce your dependency on us.
Quarter 2 onward. Systems get documented and transferred. Our engagements are designed to make us less necessary over time — which is the reason, not the contradiction, behind a nine-year median relationship.
Why we document as we go
Handover starts on day one, not month nine
A handover document written from memory after the fact is a summary. A handover document written as decisions happen is a record.
Every decision made during instrumentation and constraint analysis is logged at the time it is made — what was tested, what the result was, and why a particular path was chosen over the alternatives. By the time an engagement reaches its second quarter, that log is already most of a handover document. What remains is turning it into something a client’s own team can operate: naming conventions, dashboard definitions, and a written playbook for the decisions that used to require calling us.
Some clients take the handover fully and the engagement ends there, on schedule, with nothing left owed on either side. Most keep us on for the parts of the system that benefit from a standing practitioner — new constraint analysis as the business changes, or measurement maintenance as platforms shift — while running the documented parts themselves. Either outcome counts as the engagement working as designed.
What gets handed over
Three things, always
Documentation
The decision log
Every test, result and rationale, recorded at the time it happened rather than reconstructed later.
Systems
Naming and dashboards
Taxonomy and reporting built so a new operator can pick them up without a translation layer.
A choice
Take it, or keep us on part-time
A full exit and a reduced, standing relationship are both considered a successful handover.
Related