Professional Business Analysts / Afterwards

The handover that actually works

Documents transfer facts. They do not transfer understanding.

At the end of a project the analyst holds a large amount of undocumented context: why a rule exists, which stakeholder cares about which detail, what was tried and rejected, which parts are fragile. Almost none of that survives in the deliverables, and the standard response is to write a longer document, which does not solve it because nobody reads a long document at handover time.

What transfers understanding is working alongside somebody for a period while real questions arrive. The questions are the mechanism, because each one calls up context that would never have been written down unprompted. A fortnight of overlap conveys more than a hundred pages.

Where overlap is impossible, the highest value written artefact is not the specification. It is a short list of decisions with their reasons: we did it this way rather than that way because of this. That document is short, it is the thing people actually ask about later, and it is almost never produced.

The second highest value artefact is a list of the things that are known to be unresolved, honestly stated. Every project has them and they tend to be omitted from closing documents for presentational reasons, which guarantees they are rediscovered expensively.

The other artefact worth producing at handover is a map of who cares about what. Every system has a small number of details that matter enormously to particular people for reasons that are not documented anywhere, and the successor will discover these by changing one and hearing about it. A page listing those, with names, saves months of learning by collision and is the sort of knowledge that exists only in the head of somebody who has been present for the whole project.