If you lead with a servant’s heart, you know this trap. Something lands on the list. It needs to get done. And instead of asking who can take it, you just absorb it. Because you don’t want to burden anyone. Because it’s faster if you do it. Because, honestly, it feels good to be the one who carries the weight.
I know, because that was me. Leadership delegation was the skill I thought I had but was actually avoiding. We as leaders, and specifically those who are servant leaders, can fall into this trap of keeping too much on our plates because we want to help, we want to serve. And instead of delegating, we just take it on because we don’t want to burden anyone. Maybe I am just speaking for myself here. But I’ve worked with enough leaders over the years to know I’m not.
In Part 1 of this series, I introduced the Three Gates, an operating system for presence. Gate 3, “Who can help?”, is the one most leaders skip. This post is about why we skip it, what it actually costs, and how to reframe delegation as the highest form of service available to a senior leader.
When “Serving” Becomes “Controlling”
The pattern looks like humility. It functions as control.
Something needs doing. The leader takes it. The team never gets the chance. The leader burns out. The cycle repeats. And over time, a subtle but devastating thing happens: the team stops offering. They learn, through repetition, that their leader will absorb the work regardless. Research on organizational behavior calls this learned helplessness, and it spreads through teams like a contagion, creating cultures where initiative feels futile.
The cost is measurable. Gallup’s research shows that leaders account for 70% of the variance in team engagement. McKinsey found that leadership quality explains approximately 45% of variance in organizational performance. When a leader hoards work, they deprive team members of the developmental experiences that drive both engagement and retention. Gallup’s 2025 State of the Global Workplace report found that global employee engagement dropped to 21% in 2024, costing an estimated $438 billion in lost productivity.
And here’s the organizational cascade most over-functioning leaders miss: McKinsey found that half of all efforts to transform organizational performance fail because senior managers don’t act as role models for the change they’re asking others to make. When you model “I’ll just do it,” you’re not serving. You’re teaching self-reliance over team reliance.
The Question That Changed Everything
Years ago, a coach and mentor watched me struggle with this and asked one simple question.
“Hey Dusty, how do you feel when someone asks you for help?”
I paused and thought about it for a moment. I said, “I feel great. I feel needed. I feel compassion and empathy and desire to serve.”
He sagely nodded and said, “Have you ever thought about the opportunities for service that you’re stealing from others when you won’t ask for help?”
I have to admit, that one kind of rocked me because I’d never thought about it that way. I had framed delegation as a burden I was placing on someone else. He reframed it as a gift I was withholding. I was labeling something a burden of my own that wouldn’t necessarily be perceived that way.
The research validates this reframe. Xuan Zhao’s 2022 research at Stanford, published in Psychological Science, demonstrated across six experiments that people consistently underestimate others’ willingness to help and overestimate the inconvenience their requests cause. In one experiment, 47 of 50 people approached agreed to help on the first ask. The helpers also reported significantly more positive emotions than the requesters predicted.
Adam Grant’s research, also published in Psychological Science, found that people who reflected on being a benefactor (giving help) were significantly more prosocial than those who reflected on receiving help. The mechanism: giving strengthens identity as a capable, caring contributor. When you ask someone to contribute, you’re activating that identity.
Self-Determination Theory, one of the most robustly supported frameworks in organizational psychology, explains why this works at a deeper level. Humans have three basic psychological needs: autonomy, competence, and relatedness. Cross-cultural research found that these needs together explained 61% of the total variance in people’s experience of meaningful work. When a leader delegates meaningful work with appropriate autonomy, they simultaneously satisfy all three needs. When they retain the work, they frustrate all three.
Every time I absorbed something I should have handed off, I wasn’t being humble. I was being controlling. And I was denying someone else the chance to contribute, grow, and feel the same sense of purpose I feel when someone asks me for help.
The Leadership Delegation Shift: From Inward to Outward
The practical shift is simple to describe and hard to practice. When something needs to get done, the default question should not be “How do I handle this?” It should be “Who or what system can handle this?” Not inward. Outward.
This isn’t abdication. It’s architecture. And the data strongly favors it. Gallup’s study of 143 CEOs on the Inc. 500 list found that companies led by executives with high delegator talent posted an average three-year growth rate of 1,751%, which was 112 percentage points greater than CEOs with limited delegator talent. McKinsey’s research found that organizations whose leaders successfully empower through coaching are nearly four times more likely to make good decisions.
But delegation without clarity is just dumping. Practically, this means getting clear on four things before you hand something off: the Context (why it matters), the Objectives (what success looks like), the Resources (what they have to work with), and how you’ll Evaluate progress. We call this the C.O.R.E. Framework, and it’s how leaders delegate without micromanaging.
MIT Sloan’s Elsbeth Johnson offers a clarifying test: “Am I the best, cheapest person to do this work?” Her research showed that when leaders make all the decisions, they build dependency. And she connected delegation directly to succession planning: if you look at your bench and there aren’t strong candidates, chances are you haven’t been developing them through meaningful ownership.
The Enabling-Empowering Distinction
There’s an important nuance here for servant leaders specifically. The research identifies a paradox: the leader who most wants to serve their people may be the most at risk of disabling them.
A systematic review in The Leadership Quarterly found three ways the servant leadership imbalance manifests: leaders over-empathize with followers (resulting in their own burnout), leaders overemphasize relational aspects (resulting in lower task completion), and followers become overly dependent on leaders, unable to make decisions independently.
The distinction is between serving that enables (creating dependency through rescue) and serving that empowers (creating capability through challenge). The healthiest form of servant leadership delegates because it serves: it serves the team’s development, the organization’s capability, and the leader’s own capacity to sustain impact over time. The foundational 70-20-10 research from the Center for Creative Leadership found that 70% of key learning comes from on-the-job experiences, 20% from developmental relationships, and just 10% from formal training. Every meaningful task a leader retains is a developmental experience denied to the team.
The 30-Day Delegation Shift
Week 1: Audit. List everything on your plate. Mark items someone else could own with context and support. Be honest about what you’re holding because it matters versus what you’re holding because it’s comfortable.
Week 2: Delegate one item using C.O.R.E. Provide Context, define Objectives, clarify Resources, agree on Evaluation. Have the handoff conversation. Let go.
Week 3: Delegate a second. Notice what comes up emotionally. That resistance is data. The discomfort of letting go is where the growth is.
Week 4: Evaluate. What worked? What needs adjustment? What can you delegate next?
And daily: when a new request hits, before defaulting to “I’ll handle it,” pause and ask: Who or what system can handle this? Track for one week how many times your default was inward. That number is your growth edge.
Delegation isn’t the opposite of service. It’s the highest expression of it. When you carry everything, you’re not serving. You’re controlling. And you’re stealing from others the chance to contribute, grow, and feel the same purpose you feel when someone trusts you enough to ask for help.
This is Part 2 of a three-part series.
Read Part 1: The Three Gates— The complete operating system for presence.
Read Part 3: The 80% Permission— The circuit breaker for perfectionism.
Read The Complete Framework: Operating System for Presence— All four questions in one place.
Subscribe to the newsletter for weekly frameworks like these, or connect on LinkedIn where I share what I’m learning in real time.
FAQ
Use the C.O.R.E. Framework. Provide Context (why it matters and how it connects to the bigger picture), define Objectives (what success looks like, not what activities to perform), clarify Resources (what they have to work with, including time, budget, and access), and agree on Evaluation (how you’ll measure progress together). This creates ownership, not task assignment. When delegation fails, it’s almost always because one of these four was missing.
This is the question I hear most, and it’s usually backwards. Often the team isn’t “unready.” They’re underdeveloped because you’ve been absorbing the work that would develop them. Seventy percent of key learning comes from on-the-job experiences, not training. Delegation is development. Start with lower-stakes items, use C.O.R.E. to set them up for success, and build from there. You’ll be surprised how quickly people grow into meaningful ownership.
Check your C.O.R.E. Was the context clear? Were the objectives specific enough? Did they actually have the resources? If you skipped any of those steps, the issue isn’t delegation. It’s delegation without clarity. The other thing to examine honestly: is your standard for “good enough” realistic, or are you comparing their 80% to your 100%? Their 80% delivered on time often beats your 100% delivered late.
Think about how you feel when someone trusts you enough to ask for your help. You feel needed, purposeful, valued. Research from Stanford found that people consistently underestimate how willing others are to help and overestimate the inconvenience. When you delegate meaningful work, you’re giving someone purpose, inclusion, and the chance to grow. Refusing to delegate isn’t protecting anyone. It’s denying them the same sense of meaning you feel when someone trusts you.
Delegation includes clarity, support, and accountability. That’s the C.O.R.E. Framework. Abdication is handing something off without context and hoping it works. One builds capacity. The other creates chaos. If you’re worried about the line between them, the fact that you’re asking means you care enough to do it right. Use C.O.R.E. and you’ll stay on the right side.
Gate 3 asks “Who can help?” not “Which employee can take this?” The outward default applies to systems, processes, automation, contractors, and AI tools. It means any outward solution that removes the task from your personal capacity. The question isn’t whether you have a team. It’s whether you’re looking inward or outward when something lands on your plate.
Run the reframe from the mentor story: “How would this person feel if I asked them?” Most people feel trusted, valued, and purposeful when asked to contribute. The guilt you’re feeling is a projection. You’re assuming the request is a burden because that’s how you’ve labeled it internally. But as my mentor pointed out, you’re not burdening them. You’re including them. And when you don’t ask, you’re stealing the opportunity for service.
Then you both learn something. If you set them up with C.O.R.E., the failure is bounded and recoverable. And here’s the part that’s hard to hear: if you never let anyone fail, you never let anyone grow. The CEO Genome Project found that nearly 90% of strong CEO candidates scored high on dealing with setbacks productively. That capacity doesn’t develop in people who were never given the chance to stumble. Delegation with support isn’t risky. Over-functioning is.
