The handover illusion
Most transformations end with a ceremony: the documentation is delivered, the sign-off is signed, the consultancy leaves. Everyone agrees knowledge has been transferred because a folder changed hands. Then the first non-trivial change request arrives, and the client discovers the folder was a map of decisions, not the ability to make new ones.
Documentation records what was done. It does not confer the judgement to do the next thing. Those are different assets, and confusing them is how dependency is quietly manufactured.
“Documentation records what was done. It does not confer the judgement to do the next thing.”
Self-sufficiency is structural, not documentary
Real knowledge transfer is built into how the work is done, not bolted on at the end. It means client teams holding the pen on real decisions during the engagement - not observing, doing - with the experienced partner beside them rather than in front of them.
By the time the engagement ends, the capability already lives inside the organisation because that is where it was built. There is nothing to hand over because nothing was ever held apart.
The boundary that matters
This is the line that separates genuine project success from a permanent dependency loop. On one side, the client can run and evolve the system on its own. On the other, every meaningful change requires the vendor to come back - and the relationship that looked like partnership reveals itself as reliance.
The honest measure of a transformation is not what works at go-live. It is what the client can still change, unaided, a year later.