Make yourself unnecessary: what good advisory leaves behind
Good advisory leaves a team stronger, not dependent. Capability and judgement should stay with the team, through co-delivery, explicit reasoning, and grown champions.
The test of good advisory is what stays behind when the advice does. A strong engagement leaves a team more capable and more confident, not more dependent. The goal is to make yourself unnecessary as a crutch while staying valuable as a partner: capability and judgement should belong to the team, not travel out the door with the consultant. That is the difference between renting expertise and building it.
What does dependency look like, and why avoid it?
Dependency is the easy failure mode of advisory work. The consultant becomes the only person who understands the system, the only one who can make the hard call, the single point of failure everyone routes around. It looks like success because things keep working, right up until the engagement ends and the capability leaves with it.
Avoiding that is not about doing less. It is about doing the work in a way that deposits understanding into the team as you go. Every decision you make alone is a decision the team did not learn to make. Every reasoning step you keep in your head is judgement that does not transfer.
How does capability actually transfer?
It transfers through proximity and repetition, not handover documents. The pattern that works for me has four parts:
- Embedded co-delivery. Work on the real project alongside the team, not on a parallel proof of concept. Capability built on real constraints is capability that holds.
- Explicit reasoning. Say the why out loud, every time. The trade-off you weighed, the option you rejected, the risk you accepted. Reasoning that stays implicit cannot be copied.
- Pairing on hard calls. Make the difficult decisions together, with the team in the room, so judgement is practised rather than observed.
- Growing internal champions. Find the people who will carry the practice after you, and invest in them deliberately so the capability has somewhere to live.
To be clear, this is not about leaving. I stay as Technical Lead for AI for Delivery at PALO IT throughout. Transferring capability and staying engaged are not in tension. The point is that the team gets stronger because of the engagement, not merely served by it.
What does “leaving the team stronger” look like in practice?
It looks like the team making the next hard call without you in the room, and making it well. It looks like the internal champion explaining a trade-off to a new hire in your words, then in their own. It looks like the practice outliving the engagement.
That is the explicit aim of how I structure knowledge transfer and enablement: not a dependency, but durable capability the team keeps. The best outcome is a team that no longer needs me to do the work, and still wants me around as a sounding board.