Years into a leadership role, someone said something about me that really hurt. The person said, “The thing you need to know about Keather is that she doesn’t do anything without involving other people.” It was meant as a knock, and I took it like a knock that I was someone who couldn’t get things done on my own.
I sat with that longer than I’d like to admit. And then I was gifted with a leadership coach, who has now become a lifelong friend. She reframed it for me. She told me that getting work done through other people wasn’t a weakness. She told me it was my leadership superpower, and that I needed to lean into that. She said it’s a leadership muscle most people never strengthen.
That reframe changed how I lead. We run on EOS at Omnia, and a best practice and phrase from that system has stuck with me more than almost any other: delegate to elevate. Not delegate to get something off your plate. Delegate to elevate the person you’re handing it to, and elevate yourself in the process by finally getting out of the way.
It’s also exactly what we help other companies do with employee behavioral assessment data every day: give leaders a real, evidence-based way to see who on their team is ready for more, instead of guessing based on a gut feeling.
Here’s the uncomfortable truth. Most of us are reluctant delegators, and it’s rarely because we’re not trusting or controlling. It’s something deeper than that.
Why are leaders so reluctant to delegate?
Because we get in our own heads about it. I hear the same three reasons over and over, from myself included.
The first is the belief that nobody else can do it as well as we can. The second is telling ourselves there’s no one to hand it to, even when that’s not really true (we just haven’t looked hard enough). The third is the fear that if we don’t do the task ourselves, we’ll look weak, lazy, or incompetent. None of those three are really about the work. They’re about our own identity as a leader and how much of it is tied up in being the one who handles everything.
That’s the part nobody talks about enough. Reluctant delegation isn’t usually a skills problem. It’s an ego problem wearing a to-do list as a disguise.
I got lucky. The feedback I mentioned at the start pushed me in the opposite direction, toward involving people too much rather than too little. But I’ve coached enough leaders on my own team to know that most people land on the other side of that line. They hold on, tell themselves it’s temporary, and then wonder eighteen months later why they still can’t take a real vacation without their phone blowing up.
What's the difference between delegating and developing?
Reluctance isn’t the only failure mode. Plenty of leaders delegate constantly and still never develop anyone, because handing off a task isn’t the same thing as handing off judgment.
Delegating hands someone a task and expects a result. Developing hands someone your judgment and trusts them to build their own.
Here’s a rule that changed how I lead, and it came from some of the best advice I ever got as a new leader: be okay with people doing it differently than you, as long as they get a successful result and it doesn’t hurt your brand or your client along the way. That single sentence is the entire difference between delegating and developing. Delegating cares about the method matching yours. Developing cares about the outcome and lets the method be theirs.
I’ve watched what happens when that rule gets skipped. I know of two leaders who ended up handing off real responsibility to each other without ever developing that shared understanding first. They had completely different approaches to getting to the same result, and because nobody had ever aligned on outcome over method, they spent months in conflict. Not about whether the work got done. It did. They fought about how it got done, over and over, because neither one had been developed to trust the other’s approach. That’s what delegation without development looks like from the inside. Everyone is busy. Nobody is aligned. The team dynamics slowly rot.
How do you delegate to elevate someone in reality?
Start with a person, not a task. Look at your team and think about who’s ready to be stretched, and be honest about what natural strengths they already bring to the table. This is where knowing how someone is wired matters. An employee development assessment will tell you more about someone’s leadership style and decision-making process in less than 15 minutes and way more effectively than six months of guessing based on how they act in meetings.
From there, here’s what really makes delegation elevate someone instead of just offloading work onto them:
- Pick one person you’re ready to develop. Not your whole team at once. One person, on purpose.
- Name the specific skill to develop and be honest about why. “I want to build their confidence representing our firm at industry events” is specific. “I want them to step up more” is not.
- Choose a repeatable responsibility, not a one-off task. A single project teaches nothing that repeats. A recurring piece of ownership builds a habit.
- Hand them the outcome and the guardrails, then let go of the how. Tell them what success looks like and where the brand and client lines are. Everything inside those lines is theirs to figure out.
- Check in on the decision, not just the deliverable. Ask what they’d do and why before you ask what they did.
- Expect them to do it differently than you would. That’s not a warning sign. That’s the entire point.
None of this requires a formal program. It requires picking one person this week and doing this on purpose instead of by accident.
What's the payoff for developing your leaders?
My favorite part of leadership is watching someone grow into a stretch responsibility and realize they’re more capable than they thought. That’s not a corporate talking point. That’s truly the best part of my job.
There’s a business case too, and it’s not small. Our own 2026 Talent Trends research found that only 26.7% of organizations have a formal development process, while 55.7% rely on informal, whatever-the-manager-feels-like-doing approaches. Development happens by accident far more often than it happens on purpose, and that gap shows up later as turnover, stalled succession plans, and managers who are technically in charge but have never actually led anyone. Employee retention tools and structured development conversations exist because of exactly this gap. They catch it before it costs you the employee.
And there’s the pipeline problem every SMB leader eventually runs into. Someone leaves, or the company grows faster than expected, and suddenly you need a leader you didn’t build. Delegating to elevate is how you build that bench before you need it instead of scrambling for it after. It’s slower than just doing the work yourself. It’s also the only version of leadership development that scales past you.
So here’s what I’d ask you to do this week. Pick one person on your team you could be developing instead of just delegating to. Name the specific skill you want to build in them and be honest with yourself about why it matters. Then find a repeatable responsibility you can hand them with the sole intent of delegating to elevate, not just clearing your own plate.
If you want help figuring out how the leaders on your team are wired and where your real development gaps sit, our team can walk you through it. And if you want the full data behind what’s happening with leadership and development across small and mid-sized businesses right now, our 2026 Talent Trends report is worth the read.
Schedule a consult with our team or Download the 2026 Talent Trends report. Or do both!
