In my experience, most leaders say they want less dependency, right up until the moment they have to step back and allow it.
Removal is the third pillar of UNLED and the one that creates the biggest shift. Direction sets the target. Capability builds the muscle. Removal changes the structure. It’s where leadership stops being central and starts being architectural.
Put simply, removal means designing yourself out of the day-to-day path of progress.
Not disappearing. Not neglecting. Not “hands off and hope.”
But instead, deliberate, structured and visible step-back.
Most teams don’t 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. Over time, that becomes the operating model.
What System Have You Created?
People adapt to the system you create.
If you are always available to decide, people will always wait. If you are always present in the middle, people will always route through you. Not because they’re lazy. Because they’re rational.
Removal changes the route.
One of the biggest myths is that stepping back lowers standards. In reality, unmanaged involvement lowers standards. When leaders stay too embedded, teams stop owning quality. They produce for review, not for outcome.
Ownership and over-involvement cannot coexist for long.
Removal forces a healthy transfer. Decisions move down. Judgement moves outward. Responsibility spreads. That’s when teams start acting like adults instead of extensions.
But removal has to be done well. Bad removal creates confusion. Good removal creates growth.
I’ve seen leaders try to step back by simply saying, “You’ve got this now,” and walking away. That’s not removal. That’s abdication. The difference is design.
Answer These Questions
Good removal answers three questions before the leader steps back.
- What decisions are now yours?
- What guardrails still apply?
- When should you pull me back in?
Without those, people hesitate or guess. With them, people act.
Decision Mapping
A practical starting point is decision mapping. Take one recurring decision type and make it explicit who owns it now. Not in your head. Out loud. Visible. Repeated.
For example, instead of saying, “Run it past me,” say, “You own decisions up to X level of risk or cost. Beyond that, loop me in.” That one sentence shifts behaviour fast.
Staged Removal
Another useful move is staged removal.
Instead of jumping from full involvement to none, reduce your touchpoints in steps. First you review and question. Then you review only. Then you sample. Then you step out entirely. This keeps standards intact while ownership grows.
Think of it like removing stabilisers from a bike. You don’t kick the bike and walk away. You loosen, observe, adjust, then release.
Being Needed Feels Good
There’s also a psychological barrier leaders rarely admit. Being needed feels good. It signals value. Importance. Relevance. Removal can feel like erasing your role.
It isn’t.
It upgrades your role.
When you remove yourself from low-level decisions, you create space for higher-level leadership. Strategy. Structure. Talent. Direction. Leaders who never remove themselves never reach that level because they stay trapped in operational gravity.
If your diary is full of decisions others could make, you are under-removed.
How Many Decision-Makers Do You Create?
One phrase I’ve used with leaders for years is this. Don’t measure your value by how many decisions you make. Measure it by how many decision-makers you create.
That’s removal done right.
You’ll know removal is working when a few signals appear. Questions come with recommendations, not requests. Updates replace approvals. People inform you after acting, not before. At first that can feel strange. Even risky. It’s actually progress.
Another practical idea is the “tell me after” rule. For defined areas, ask your team to act and then inform you, instead of asking first. It builds pace and judgement at the same time.
You can also build removal into your language. Instead of “Ask me if unsure,” try “Decide within the guardrails and brief me after.” Language sets permission.
Expect wobble. Removal is rarely smooth at first. Some decisions will be made differently than you would have made them. That’s not failure. That’s transfer. If the outcome is sound, style differences are acceptable tuition fees.
If you correct every difference, you pull ownership straight back.
Visibility Without Interference
One more lever is visibility without interference. Use dashboards, shared trackers, and regular summaries so you can see progress without sitting inside every conversation. That allows distance without blindness.
Too close and you become the bottleneck. Too far and you lose connection. Designed removal keeps you above the work but still over the system.
If you feel overloaded, over-consulted, and over-required, removal is not a risk. It’s the remedy.
