ongoing
The Handover
Designed to support your department moving from rung 3 (Systemised) to rung 4 (Native).
if this is you
The standard exists and the workflow works.
What has not happened is the total adoption within your team. It still runs because you are the one running it, and it would stop within a month of your attention going somewhere else.
what it is
Two workflows, handed over properly.
Weekly sessions with the team who will own them, and an ownership model with actual names against it. The point is not to add capability. It is to make the capability survive without me in it, and without you holding it up.
what you get
- Two workflows handed over
- Weekly working sessions with the team
- An ownership model with names against it, not roles
how it is bought, and why there is no number here
It runs monthly with a minimum term, and the number goes in a proposal rather than on this page.
That is deliberate. The total is more than one signature covers, and putting it in front of you cold would be asking you to go and win an argument on my behalf, with people who were never in the room. I have watched that kill two good pieces of work. So it comes after a Diagnostic and a fix, when there is something to point at.
the rung
Rung 4 is where workflows run end to end and people steer by intent.
This is designed to support that move. It does not promise you will land there.
where it starts
Not here. It starts with a Diagnostic.
The Adoption Ladder is adapted with credit from Boris Cherny’s "Steps of AI Adoption" (2026).