Crosshire
← The engagement, end to end
Engagement23 The engagement, end to end · 3 of 3

What good looks like when you leave

The engagement is not finished when the pipelines run. It is finished when the team keeps them running without you, and that is checkable rather than felt.

Stand 29.07.2026

#The handover test

What
Nine checks, run in the final fortnight. Every one is observable — no item on this list is a judgement call, which is deliberate, because "the team feels confident" is not a handover criterion.
  1. Every production object is owned by a group, not a person. Verify it with a query, not a promise.
  2. The consultant is not on the alert rota, and has not been for two weeks.
  3. A game day has been run and survived — a real pipeline broken deliberately, diagnosed and fixed by the team.
  4. Every pipeline has a runbook, written by whoever gets woken, and each one answers the re-run question: safe to re-run blind, or needs intervention first.
  5. The last three incidents produced runbook updates in the same week they happened.
  6. CI fails for the right reasons — someone can point at a build that correctly blocked a merge in the last month.
  7. A team member has added a new source end to end — bronze through gold, tested, granted, monitored — without pairing.
  8. The eight irreversible decisions are in the client's repository, and someone who was not in the room can explain them.
  9. The currency register has been re-verified by the team at least once, so the habit transferred and not just the document.
Why
The failure this prevents is the standard consulting failure, and it is rarely technical: the platform works, the team can operate it while things go well, and the first genuinely novel incident after the consultant leaves takes four days instead of four hours.
Checks 3, 5 and 7 are the load-bearing ones. They are the only three that cannot be satisfied by documentation — each requires the team to have already done the thing unaided. Everything else on the list can be faked by a diligent writer.
Doing it
  • Run the nine checks in week 10, not week 13Failures need time to become passes.
  • Take yourself off the rota deliberately, and earlyEarly enough that a real incident lands while you are still reachable but not responsible.
  • Schedule the game dayIt never happens if it is left to a quiet week.
  • Write nothing in the final fortnight that the team could write instead
Embedding it
  • Give them the nine checks in week one, not week tenA test you can see from the start is a target; a test sprung at the end is an exam.
  • When a check fails, hand back the fix rather than doing itA failed check you repair yourself has taught nobody anything.
  • Name the owner of each runbook out loud, in front of the team, and get a verbal yesWritten ownership with no spoken agreement is not ownership.
  • Ask in the retro which check was hardestThat answer is the honest state of the handover, and it is usually check 7.
Defaults
  • Nine observable checks, shared in week one, verified in week ten
  • Group ownership everywhere in production, proven by query
  • Consultant off the rota with two weeks of runway remaining
  • The final fortnight is the team writing and you reviewing — never the reverse
Gotchas
  • A handover that is a document rather than a demonstrationThe document is read once and never again; the pipeline someone built unaided is remembered. If you only have time for one, build the second.
  • Staying on the alert rota 'just in case' through the final weekIt is kind, and it guarantees the team never experiences an incident as theirs — so the first one they own happens with no one to ask.
  • Named owners who were never askedSomeone discovers they own a pipeline when it pages them at 03:00, and the runbook they never wrote is the one they now need.
  • Skipping the game day because the quarter is busyThe quarter is always busy. Its absence is only discovered during the first real incident, which is the worst possible time to learn that the runbook was never tested.