006-handoff-is-part-of-the-work.md
The handoff starts before the last week
Leaving a team able to change the system takes practice during the engagement.
A handoff scheduled for the last afternoon leaves very little room to discover what the team cannot yet do. Walking through a repository is easy when the person who wrote it is in the room answering every question. That can conceal how much of the explanation still lives in their head.
I want the engagement to make room for someone else to use the work before I leave. They should be able to follow the setup instructions, make a small change, and get it into an environment where they can inspect the result. Watching where that process becomes difficult gives the remaining work a useful priority.
Let the instructions be tested
If I have to interrupt with an unwritten step, that step belongs in the instructions. If another engineer needs access they do not have, the handoff has an ownership problem to resolve. Neither is fixed by adding more pages to a document.
The exercise should include something going wrong. A failed deployment or a job with invalid input gives the team a reason to use the recovery instructions. They can ask whether the logs explain the failure and whether the suggested recovery is safe. I would rather have that conversation while there is time to improve the system.
Documentation also needs the reasoning behind choices that look strange. An engineer can read what the code does. They may have no way to recover why we accepted a limitation, or which external dependency prevents us from removing it. A short decision record can spare them another investigation.
Leave the remaining work in view
Every engagement has edges. There may be deferred cleanup or a dependency that still needs replacing. I want those items named, with enough context for the team to decide when to address them. A vague warning about technical debt is hard to act on.
There is some tension here for a consultant. Being the person with all the answers can make the work feel valuable. But if every routine change still requires a call to me, I have left the client with a dependency they should have been able to avoid. A useful final review includes the changes the team has already made without my help and the questions they still need answered.