In my experience, most leaders say they want capable teams, but their daily behaviour accidentally weakens capability instead of building it.
Not on purpose. Not through ego, but through speed.
It’s quicker to answer the question. Quicker to fix the slide. Quicker to rewrite the email. Quicker to take over the client call. In the moment, it feels efficient. Over time, it creates reliance.
Capability doesn’t grow when the leader is the shortcut.
This is why capability is the second pillar in the UNLED model.
Once direction is clear, the next job is to make sure your people can actually operate inside it without relying on you every step of the way.
And capability is wider than most leaders think.
It’s not just skill. It’s judgement. It’s confidence. It’s decision quality under pressure. It’s knowing what to do when the script runs out. You can have trained people who are still dependent and you can have experienced people who still check everything.
One of the biggest myths in leadership is that capability grows with time served. It doesn’t. It grows with the right exposure and the right conversations.
I’ve seen people with ten years in role still escalate basic decisions. I’ve seen people with six months step up fast because their leader coached instead of answered.
Over-Helping
Most capability stalls because leaders over-help.
When someone brings you a problem and you give them the solution, you solve today’s issue and weaken tomorrow’s thinker. When you make them think it through, you slow the moment and strengthen the person.
Answer Questions With Questions
A simple practical shift is to answer questions with questions more often than feels comfortable.
When someone says, “What should I do here?” your first move doesn’t have to be an answer. It can be, “What are you thinking?” or “What options do you see?” or “What would you recommend if this was yours to own?”
At first, they may resist. That’s normal. They’re used to getting answers. Stay with it. Capability often grows right after mild discomfort.
Leader Rescue
Another pattern that blocks capability is leader rescue.
You see someone struggling and you step in too early. You save the deadline. You protect the client. You keep standards high. All good intentions. But if rescue becomes predictable, learning becomes optional.
People don’t build strength when the weight is always taken off them.
This doesn’t mean letting people fail publicly or recklessly. It means letting them carry more of the thinking and more of the load while you stay close enough to coach. There’s a difference between abandonment and development. Good leaders know the line.
Specific Feedback
Capability also grows through specific feedback, not general praise.
“Good job” feels nice, but it teaches nothing.
Specific feedback builds repeatable strength. “The way you structured that client summary made the decision easy” tells them what to keep. “Next time, lead with the risk, not the background” tells them what to adjust.
Capability feeds on precision.
After-Action Reflection
One underused capability builder is after-action reflection. Quick, simple, and powerful. After a piece of work, ask three questions. What worked? What didn’t? What would you do differently next time? Not in a formal review. In normal conversation.
This turns experience into learning instead of just activity.
Progressive Stretch
Another practical move is progressive stretch.
Most leaders either under-stretch or over-stretch. They keep giving the same level of work to the same people, or they throw someone in too deep too fast. Capability grows best when stretch is stepped.
Give the next level version of the task, not a completely different universe. Let them lead the client call with you listening. Let them draft the proposal with your review. Let them run the meeting with your backup.
Stretch plus support beats pressure plus silence.
Mind Your Language
Watch your language too. Capability is shaped by how leaders respond to mistakes. If every error gets a takeover response, people play safe. If errors get a learning response, people grow.
Try phrases like, “Walk me through your thinking” or “What will you change next time?” instead of “I’ll fix it.” Same moment. Different long-term effect.
There’s also a structural side to capability. If the same questions appear every week, that’s not a people problem. That’s a missing resource. A checklist. A template. A playbook. Smart leaders turn repeated help into shared tools.
That’s how capability scales across the team, not just inside individuals.
One more truth worth saying out loud. Capability takes longer upfront and saves time later. Many leaders quit too early because the early phase feels slower. Of course it does. You’re growing people, not just closing tasks.
But once capability compounds, the leader’s load drops sharply. Decisions happen lower. Quality stabilises. Confidence rises.
If you feel constantly pulled back into the same types of problems, don’t just ask who keeps bringing them. Ask what capability is missing and how you are developing it.
Strong teams are not built by being available. They are built by being developmental.
Build more thinkers than followers. That’s when you stop being needed in the small stuff and start being useful in the big stuff.
