Make yourself unnecessary: what good advisory leaves behind
Preem advisory leaves a crew stronger, not hooked on you like a bad ripperdoc. Capability and judgement should stay chipped into the crew, through co-delivery, explicit reasoning, and grown champions.
The test of good advisory is what stays behind when the fixer deltas. A strong engagement leaves a crew more capable and more chromed, not more hooked. The goal is to make yourself unnecessary as a crutch while staying preem as a partner: capability and judgement should belong to the crew, not walk out the door with the consultant when they delta. That is the difference between renting chrome and building it into your own wetware.
What does dependency look like, and why avoid it?
Dependency is the easy way advisory work flatlines. The consultant becomes the only choom 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 deltas with it, leaving the crew flatlined.
Avoiding that is not about doing less. It is about doing the work in a way that deposits understanding into the crew’s wetware as you go. Every decision you make alone is a decision the crew did not learn to make. Every reasoning step you keep locked in your own skull is judgement that never transfers.
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. Jack into the real project alongside the crew, not some parallel proof of concept. Capability built on real constraints is capability that holds.
- Explicit reasoning. Say the why out loud, every time, like a netrunner narrating the run. 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 crew in the room, so judgement gets chipped in by practice rather than just watched.
- Growing internal champions. Find the chooms who will carry the practice after you delta, and invest in them deliberately so the capability has somewhere to live.
To be clear, this is not about deltaing for good. I stay chromed in 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 crew gets stronger because of the engagement, not merely served by it. A gonk move is to hoard the knowledge so they keep paying your eddies.
What does “leaving the crew stronger” look like in practice?
It looks like the crew making the next hard call without you in the room, and making it nova. 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 long after you delta.
That is the explicit aim of how I structure knowledge transfer and enablement: not a dependency, but durable capability the crew keeps chipped in. The best outcome is a crew of self-sufficient samurai that no longer needs me to do the work, and still wants me around as a sounding board.