Many organisations say they want to build capability, but the way work is commissioned and delivered can produce the opposite. A specialist arrives, interprets the problem, creates the materials, facilitates the difficult conversations and remains the person who understands how everything fits together. The project may be delivered. The team may even be pleased with the result. Yet the capability still sits outside the people expected to live with it.
This is not always deliberate. Dependency can feel efficient in the short term. It is quicker for an experienced person to make the decision, complete the analysis or translate the process than to slow down and make the thinking visible. Under delivery pressure, transfer becomes something that will happen later. Later often means a handover document, a recording or a final workshop after the important choices have already been made.
The goal is not to make support disappear. It is to make capability remain.
Capability is more than knowledge
Knowing that a framework exists is not the same as being able to use it. Attending training is not the same as having the confidence to apply it when the situation is ambiguous. Capability includes understanding, judgement, practice and the ability to adapt when the original example no longer fits.
This is why BridgeWorks describes “Make People Bigger” as a standard rather than an encouraging phrase. Bigger should be visible. An individual can explain the problem in their own words. A team can use a shared method without waiting for the person who introduced it. An organisation can continue making good decisions after the project team has moved on.
What bigger looks like
- For an individual: “I understand what is happening, I know what to do next and I can judge whether it is working.”
- For a team: “We can use the method together, challenge each other constructively and bring new colleagues into the work.”
- For an organisation: “The capability is distributed, decisions do not depend on one person and improvement continues after external support ends.”
Why traditional handovers are not enough
A handover usually transfers outputs. Capability transfer must also reveal the decisions, assumptions and judgement behind those outputs. Without that layer, people inherit a finished artefact but not the ability to recreate, challenge or improve it.
Consider a governance model. A team can receive the process map, meeting cadence and reporting template. But can they explain which decision each part supports? Do they know what evidence would justify changing the cadence? Can they recognise when a forum has stopped adding value? If not, the governance has been installed rather than understood.
The same applies to AI. A prompt library can be useful, but it does not automatically help someone recognise an appropriate use case, protect sensitive information or evaluate an answer that sounds convincing. Capability appears when the person can make those judgements without copying the expert’s exact steps.
Design the work for transfer from the beginning
Name the capability, not only the deliverable
Instead of defining success as “produce the new process,” also define what people should be able to do afterwards. They might need to facilitate a decision, adapt a framework, assess an AI use case or explain a trade-off to senior stakeholders.
Build through real work
People gain confidence by completing meaningful tasks, not by collecting information about them. Use live examples where the learner already understands the context. That gives them a basis for evaluating the method rather than following it blindly.
Make the thinking visible
Explain why a choice was made, what alternatives were considered and which assumptions would change the recommendation. Invite others into the reasoning before the answer is polished. This may feel slower at first, but it creates people who can think with the method rather than wait for its creator.
Create opportunities to lead
Transfer becomes real when someone else facilitates the session, teaches the framework or adapts it to a new problem. The original expert should move from doing, to observing, to being available only when genuinely needed.
Plan the step-back point
Every engagement should be able to answer: what will people be able to continue without us, and how will we know? The step-back is not abandonment. It is evidence that the work has produced confidence and capability rather than permanent reliance.
A practical test
Before closing a project, ask the people closest to the work to explain the approach without using the project language. Ask them what they would change if the context shifted. Ask who else could now lead the work. Their answers will tell you more about capability than the completion status of the deliverables.
A good solution can still include specialist support. Some challenges require expertise, challenge or independent assurance. The distinction is whether that support enlarges the people involved or quietly makes itself the only route to progress.