Why Your Best People Aren't Stepping Up - And It Might Be Your Fault
It's maddening.
You know they can handle it. The capability is there. The drive is there. You've seen exactly what they're capable of.
So why are you still the bottleneck? Why won't they take ownership?
Here's the part nobody wants to hear.
They're not failing to step up. They're responding to what you've built.
Every time you jump in. Every time you take the problem back. Every time you improve their solution and send it back as yours. Every time you say "I'll handle this" because it's faster or safer or just easier - you're sending the same signal.
You're not really the owner here.
And they're listening. Perhaps not consciously. But consistently.
The system isn't broken. It's working exactly as designed.
It's just not a design that scales
It can be helpful to break this down into types of owner.
In most teams there are three:
Natural owners - they grab things and drive them regardless of the system. You probably have one or two. They're not the problem.
Latent owners - the capability is there, the mindset is there, but the system is suppressing it. They've learned to escalate because that's what gets rewarded. This is the group you're frustrated with.
Non-owners - some people genuinely aren't wired this way. No system fixes that. That's a hiring conversation.
The frustration you're feeling? It's almost certainly aimed at group two.
And here's what that frustration is actually telling you - you already know they can do it. You wouldn't be frustrated if you didn't. You'd just be disappointed.
“You don’t build ownership into people. You build the conditions that reveal it.”
We saw this play out recently. A young leader, new to his role, was passing every problem straight up to senior staff and through to his client the moment it landed. The intention was good - "so everyone knows where we stand." But a shared problem doesn't solve it.
The whole team felt additional stress
Worried people who couldn't fix it chimed in
Noise everywhere
The client saw escalation without resolution - which added more stress back into the team
Trust started to wobble
He became overwhelmed - not just with the problem, but with managing everyone else's emotional response to it
The shift wasn't a pep talk about confidence or ownership. It was about building the environment that made ownership possible.
Three things changed:
Permission to sit with uncertainty - to hold a problem long enough to form a plan before sharing it. Not forever. Long enough.
Autonomy to solve it his way - his leader stopped prescribing the how and trusted him to find it. He's always more likely to win playing his own game.
A safety net - a senior leader who said: come to me first, before anyone else. I trust you. I won't let you crash and burn.
A big problem emerged shortly after. One that - shared immediately - would have created that same cascade. Instead he sat with it. That's not easy. Carrying a problem alone, knowing things aren't right, can feel like dishonesty.
But sitting with uncertainty isn't dishonesty. It's the job. Holding a problem long enough to form a plan, then bringing the right people in at the right time - that's leadership.
By the time the issue was shared it came with a plan. The client never carried the emotional weight of the raw problem. Trust held. The leader grew. The team stayed focused.
This is what we mean by win-win at Thread. The business wins. The person wins. Not one at the cost of the other. That's how you build sustainable high performing teams and businesses.
Three things worth doing now.
1. Audit your escalation patterns. Where do problems consistently land on your desk? For each one ask: did this come with a solution or just a problem? If it's just a problem - the system is teaching escalation. That's your signal.
2. Give permission explicitly. Don't assume people know they have the space. Tell them. Name the skill. Explain that sitting with uncertainty and owning the outcome is a fundamental part of leadership - not optional. Then give them something concrete:
A timeframe - "take 48 hours with this before we discuss it"
A safe first port of call - "come to me before anyone else"
Protected time if they need it - "I'll clear space for us to work through this together"
A safety net - "I trust you. I won't let you crash and burn."
And accountability - "I'll check in. I expect to hear how it's going."
Independent. But not alone.
3. Shift from critic to resource. Your instinct will be to improve it. Resist that. Ask questions first. What have you considered? What would you do next? You can make suggestions. Build on their thinking rather than replacing it. The moment you substitute your answer for theirs, ownership quietly returns to you. And they've learned the lesson one more time.
"I've tried giving autonomy but they still escalate."
Check the four tells. Any one of these teaches the same lesson:
The overrider - they bring a solution. You improve it and send it back as yours. Or tell them it's wrong and hand them the answer. They come back next time. And the time after. Then they stop bringing solutions altogether. They just bring you the problem. That's the pattern you're frustrated about - and you built it.
The rescuer - says "I'll handle this" the moment it feels too big. You think you're protecting them. You're teaching them the ceiling.
The absentee - delegates and disappears. No check-ins, no safety net. When it wobbles - and it will - there's no one there. They learn that ownership means carrying everything alone. They won't do it again.
The critic - feedback that only ever points out what's wrong. Their instincts start to feel untrustworthy. Escalation feels safer than trying.
“Autonomy without accountability isn’t ownership. It’s just hoping for the best.”
"But we're too small for this - it's just me and my co-founder."
This isn't a scale problem. Two people can still pass stress to each other unnecessarily. Own your half. Bring the other in as a resource when needed - not as a dumping ground for anxiety. The principle applies from day one.
"But what if they fail?"
There's a difference between getting it wrong and bursting into flames. Your job is to know the difference and step in before it becomes catastrophic. Give them room to learn. Don't give them room to destroy something irreplaceable.
You probably already have owners in your business.
People who - given the right conditions - would grab things, drive them, and deliver without you needing to be involved. You've seen their capability. And their hesitation makes a lot more sense now.
The question isn't whether they have what it takes.
You already know they do. That's why it's frustrating.
The question is whether you've built something that lets them show it.
“You don’t build ownership into people. You build the conditions that reveal it.”
Recognise this in your team? → Let's have a chat
