The Handoff Problem

The handoff is where most agency relationships fail.

Not because the work was bad. Not because the relationship was bad. Because the knowledge didn't transfer.

What the handoff is supposed to be

The handoff is the moment when the agency gives the client what they built. The code, the documentation, the credentials, the context. The client takes ownership and the agency steps back.

In theory, this is clean. In practice, it's where most of the value is lost.

What actually happens

What actually happens is that the agency delivers the artifact — the code, the site, the system — but not the understanding. The client has the thing, but not the knowledge of how it works, why it was built the way it was, or how to change it.

The client is now dependent on the agency for every change, every fix, every addition. The agency has created a customer, not a capability.

This is sometimes deliberate. An agency that creates dependency creates recurring revenue. But it's often just the result of not thinking carefully about what a good handoff looks like.

The knowledge transfer problem

The knowledge transfer problem is that knowledge is hard to transfer. It lives in the heads of the people who built the thing. It's not fully captured in documentation, and documentation is often incomplete or out of date.

The only reliable way to transfer knowledge is to transfer people — to have the people who built the thing work alongside the people who will maintain it, until the maintainers understand it well enough to own it.

This takes time. It's more expensive in the short term. It's much cheaper in the long term.

What a good handoff looks like

A good handoff has three components.

Documentation that's actually useful. Not a data dump of everything that was done, but a clear explanation of the decisions that were made and why. The things that aren't obvious from reading the code. The things that will matter when something breaks.

A transition period. Time when the agency and the client team work together on the system. The agency explains; the client team asks questions and makes changes. The knowledge transfers through doing, not through reading.

Ongoing availability. Not a support contract — genuine availability to answer questions as they come up. The questions that can't be anticipated in advance, that only arise when the client team is actually running the system.

The partnership model

The alternative to the handoff model is the partnership model. The agency and the client work together continuously, with the agency's role changing over time as the client team builds capability.

This is how we work at NextGen. We don't aim to be needed forever. We aim to build capability in the client team, so that the relationship ends when it should — when the client can own the system fully.

That's a different incentive structure from the traditional agency model. It's also a better one.