The leader who stopped helping
by Scott D. Clary
Most people think great leadership means having the answers. The best leaders I've met are the ones who learned to keep their answers to themselves.
I caught myself doing something last month that I'm still thinking about.
One of the people on my team came to me with a problem. Something about the way we were structuring a sponsorship deal that didn't feel right. She'd been working on it for a couple of days and was stuck. I could see the answer. It was sitting right there. And before she even finished explaining, I started walking her through how to fix it.
She nodded, took notes, said thank you, and left.
And I felt great about it. Helpful leader. Generous with his time. Available.
It took me about a week to realize what I'd actually done. She came back with a nearly identical problem the following Tuesday. Same category. Same type of stuck. Because I'd solved it for her the first time, she never built the muscle to solve it herself. She learned to bring problems to me. I taught her that.
The pattern nobody talks about
Once I saw this in myself, I started asking about it in interviews. Not directly, because nobody wants to admit they might be a bottleneck. But I'd ask founders and leaders what they wish they'd done differently in the first few years of building their team.
The answer that keeps coming back, in different words but always the same shape, is some version of: I wish I'd let people struggle longer before stepping in.
A founder who scaled a SaaS company to about fifty employees told me the hardest transition of his career had nothing to do with fundraising or product. It was learning to watch someone do something slower, messier, and less efficiently than he could do it himself, and not intervene. He said he'd sit in meetings physically biting the inside of his cheek to keep from jumping in with the answer. "Every time I solved it for them," he told me, "I was basically saying: I don't trust you to figure this out."
He didn't mean it that way. He meant to be helpful. That's what made it so hard to see.
solved it for them," he told me, "I was basically saying: I don't trust you to figure this out."
He didn't mean it that way. He meant to be helpful. That's what made it so hard to see.
A woman who runs a creative agency told me she lost three senior people in one year before she figured out what was happening. She was so involved in the work, so present with feedback and direction, that her best people felt like they had no room to develop their own judgment. "They didn't leave because I was a bad boss," she said. "They left because I was too good of one. I was everywhere. And when you're everywhere, your team never gets to discover what they can do without you."
What helpfulness actually costs
There's a version of leadership that looks, from the outside, like exactly what you'd want. Available, full of answers, deeply invested in every problem. People describe this person as "hands on" or "dedicated" or "involved."
And sometimes that's exactly what a team needs, especially early on when everyone is learning the game and the stakes of a wrong move are high.
But there's a point where that involvement crosses a line, and almost nobody notices when it happens. You keep helping, the team keeps bringing problems, everything keeps getting solved. Everyone feels productive. But underneath the surface, something corrosive is taking hold: the team is learning to depend on one person's judgment instead of developing their own.
50