Most leaders say they want less dependency, right up until the moment they have to step back and allow it.
Removal means designing yourself out of the day-to-day path of progress. Getting out of the way isn’t the same as walking away. You’re still accountable, you’re just no longer the person holding the daily work together. Optional in the operations, present in the leadership.
Teams rarely stay dependent because they lack talent. They stay dependent because the leader never exits the decision path. Every approval, every judgement call, every tricky moment still routes upward, and after a while that stops being a habit and becomes the operating model.
Where Removal Sits
Removal is what the UNLED® model builds towards. Direction, Capability, Decision Ownership and Systems & Rituals are the four pillars, and Removal is what they hold up. Get those four right and this becomes possible. Skip them and stepping back is just abandonment with better branding.
That’s the difference between good and bad removal. Saying “you’ve got this now” and walking away isn’t removal, it’s a shrug. Designed removal answers three questions before you go: what decisions are yours now, what guardrails still apply, and when should you pull me back in. Without those, people hesitate or guess.
Knowing What to Let Go Of and When
Most leaders get the timing wrong in one of three ways. They step back before the team is ready and end up firefighting. They hold on long after they’re needed and become the bottleneck. Or they hand over the easy things and stay tethered to everything that matters.
Two questions will tell you where you actually stand. What still goes wrong when you’re away? And where does everything still depend on you? Make the list and be honest with it. Wherever your name keeps appearing, the system still runs on you being there.
Then there’s a simple test for what’s removable. If you’ve done something more than five times, someone else should be able to do it next. Repeatable means removable.
Timing matters though. Remove yourself when three things are true: the direction is clear, your team has proved they can handle it, and the results hold up without you stepping in. Going early leaves people in the lurch. Holding on past that point is usually ego wearing the costume of high standards.
Where Your Involvement Should Go
You don’t need to remove yourself from everything. You need to be deliberate about where you stay, where you step out, and where you build something that takes your place. Sort what you’re still involved in by how much it matters and how much it still needs you personally.
High impact, high reliance
The things that carry real weight and still revolve around you. Big negotiations, final sign-off before launch, complex escalations, key hiring calls. These are the hardest to hand over and the most important to, because as long as you hold them, your availability is the ceiling on what the team can achieve.
Transfer these properly. Explain how you think about the decision rather than just showing the task. Then move in stages: they shadow you, they lead with you watching, they lead with you available, they lead and you debrief afterwards.
High impact, low reliance
Your sweet spot. Important work you’ve already set up well. Stay close enough to guide, far enough back that the team still owns the outcome.
Ask questions that raise the thinking rather than correcting the detail. What patterns are we seeing? What’s slipping through that we haven’t spotted? If we stay on this track, where does it put us in six months?
Low impact, high reliance
Where your time goes to die. Small approvals, routine sign-offs, standard reports, the same process question every fortnight. Each one is quick. Together they eat the week.
Don’t delegate these one at a time. Build something that removes you permanently. Set rules instead of requests, so instead of “check with me first” people get “if it meets A, B and C, send it.” The rule does the checking for you, and your team learns your judgement by applying it rather than waiting for you to apply it.
Low impact, low reliance
The easiest quadrant to leave and the hardest in practice, because habit is holding you there rather than necessity.
I used to sit in on every weekly team catch-up. Not to run it, just to stay across things. I barely spoke. When I did, the whole dynamic changed, because people stopped thinking out loud and started performing for me. So I stopped going. The meetings got shorter, sharper and more honest. My silence hadn’t been creating space for them. My absence did.
If you’re still hovering somewhere, ask whether you’d insert yourself into it today if you weren’t already involved.
Staying Visible Without Interfering
Distance without blindness is the thing to aim for. Dashboards, shared trackers, regular summaries. Enough to see progress without sitting inside every conversation.
Too close and you’re the bottleneck. Too far and you lose the plot entirely. Designed removal keeps you above the work and still across the system.
Expect the first few months to be untidy. Some calls will land differently from how you’d have made them. If the outcome is sound, that’s transfer working rather than failing, and correcting every difference pulls the ownership straight back to you.
The Part Nobody Admits
There’s a psychological barrier here that most leaders won’t say out loud. Being needed feels good. It signals value and importance, and removal can feel like erasing your own role.
It upgrades it. Step out of low-level decisions and you create room for the work only you can do. Strategy, structure, talent, direction. Leaders who never remove themselves never get there, because they stay stuck in operational gravity.
If your diary is full of decisions other people could make, you’re under-removed.
Don’t measure your value by how many decisions you make. Measure it by how many decision-makers you create.
