A familiar shape: a strategy engagement produces a good document. Six weeks later a different team starts building from it. Nine months on, the thing that shipped bears only a family resemblance to the plan, and nobody can point to the moment it diverged.
What actually gets lost
Not the deliverable. The deliverable survives. What is lost is everything that did not make it into the deliverable: the three options considered and rejected, why the obvious approach was wrong, which constraint was hard and which was merely preferred.
A build team without that context will re-derive it, badly, under time pressure. Every unstated assumption becomes a coin flip.
The reversal nobody notices
The worst version is quieter than an argument. A developer hits a constraint, makes a sensible local call, and the strategic decision is reversed without anyone realising it was a strategic decision. It is not visible in a status report. It shows up a quarter later as a number that did not move.
What helps
- Keep at least one person across the whole arc, not as an overseer but doing the work
- Write down decisions with their reasoning, not just their outcome
- Make the plan the thing that gets updated, rather than a document that is filed and superseded by reality
- Put something reviewable in front of the client every week, so divergence surfaces in days rather than quarters
Why agencies find this hard
Because the economics push the other way. Strategy sells at one rate, delivery at another, and utilisation is easier to manage when specialists move between projects. Keeping the same senior person on one engagement from scoping through launch is more expensive to staff. It is also the only reliable way we have found to stop the gap opening.
If you are commissioning work, the question worth asking is simple: who will still be on this project in six months, and will they have been in the room when the plan was made?