There’s a moment many leaders don’t admit out loud. You’re working harder on someone else’s career than they are, and the more you try to fix it, the less ownership they seem to take. It feels noble in the moment. It looks like support, but it quietly turns into a trap that drains leaders, stalls employees, and keeps organizations addicted to the idea that speed is the same as progress.
Brad Federman remembers the instant he recognized that trap in his own leadership. In his book, Never Delegate Again: Uncover the Secret to Growing Your Company, Your People and Yourself, he opens with a story about Olivia, a standout employee with deep institutional knowledge and strong relationships across the business. She was burned out in her current role but didn’t want to leave the company. Brad did what many conscientious leaders do when someone talented is at risk of walking out the door: he took responsibility for solving the problem. He hunted for roles, explored possibilities, and tried to engineer a landing spot that would keep her engaged and retained.
Then, a colleague delivered a blunt message: “She’s going to leave, and it’s all your fault. She says you’re not helping her.” Brad’s first reaction was frustration because he believed he was doing exactly that. He was working tirelessly behind the scenes, but the sentence that followed in his own mind cracked the situation open: “I’m killing myself to help her.” In that phrasing was the real diagnosis. If he was killing himself, then he had become the owner of Olivia’s career. He had taken the steering wheel, and in doing so, he had removed the struggle, reflection, and self-direction that growth requires.
The turnaround didn’t come from a better internal job board search or a more persuasive retention pitch but from flipping ownership. Brad sat down with Olivia and they built a plan that was her plan. She took the lead, and he supported. She worked it, she found a new role, and ultimately, she stayed. This breakthrough was a shift from rescuing to coaching, from “I’ll fix this” to “I’ll back you while you build it.”
Why “Helping” Often Hinders
Federman’s argument begins with a deceptively simple idea: leaders confuse helping with growth. He uses a parenting analogy that lands because it’s hard to argue with. If a child is learning to spell and you spell every word for them, you feel helpful, but you’ve actually prevented learning. The struggle of sounding it out, checking, correcting, and practicing is the work that wires the skill. Likewise, leaders often try to remove the struggle for employees, especially when the stakes feel high or time feels tight, and then wonder why capability doesn’t build.
“In most cases, when you’re helping, you’re hindering,” Federman says. The pattern is familiar: someone brings a problem, and the leader provides the answer. The moment feels productive because the immediate pain goes away. But the employee doesn’t develop the internal muscle to solve the next version of the problem, and the leader becomes the bottleneck. Over time, the leader’s job shifts from setting direction to being an on-call solver, and the employee’s confidence shrinks because they rarely experience the full arc of figuring it out.
What makes this worse is that many leaders hold an unrealistic expectation about how learning works at work. They know, from their own lives, that meaningful growth takes time and includes setbacks. Yet they treat employee development as if it should happen instantly. That mismatch becomes a source of chronic disappointment and control: when growth doesn’t happen on demand, the leader steps in and does it themselves, which ensures growth won’t happen.
The Real Superpower Is Staying Relevant
Federman insists the context around delegation has changed so dramatically that older models struggle to hold up. He points to how work has evolved from a generalist environment to an increasingly specialized one. A classic framework like the Eisenhower Matrix suggests that if something is urgent and important, you should do it yourself. That advice made more sense in eras where leaders could realistically understand most of the work well enough to execute it. In a modern organization, and even in many modern industries, “urgent and important” tasks often require specialized expertise that a leader doesn’t personally have.
The deeper shift, though, is that organizations have over-optimized for efficiency at the expense of capability building. Federman argues that efficiency can’t be the primary objective when skill sets expire quickly and work changes constantly. In the conversation, he notes that skill sets can have a shelf life of just a few years, while company life cycles have compressed dramatically compared to previous generations. The implication is uncomfortable but clear: if you aren’t building growth into the rhythm of work, you’re building a business that may not keep up.
That’s why he calls relevance the new name of the game. Staying relevant means staying ahead of the curve, and that requires people to grow continuously. Delegation becomes a daily growth conversation, not an occasional managerial task. When leaders treat delegation as “dumping” to reduce their own load, they miss the strategic opportunity to build the very capability that keeps the company adaptable.
A Growth Matrix Instead of a Dumping Ground
Most leaders have been taught to delegate as a form of productivity. Federman offers a different lens, one he describes as a Growth Matrix. The point is not to move work away from the leader as quickly as possible, but rather to look at every task and decide what it should become in the system. Some tasks should be removed because they hinder growth or add no value. Some should be automated. Some require immediate expertise where development time isn’t available. Some are foundational and belong in onboarding or early role development. And some are growth assignments that intentionally stretch someone in a way that builds relevance.
This sounds straightforward until you place it inside real organizational dynamics. Leaders often choose the path of least resistance. They throw unclear projects “over the transom” to a reliable go-to person, the one who always figures it out. That person becomes burned out and resentful, not because they hate the challenge, but because the system has turned them into a dumping ground. Meanwhile, others on the team feel overlooked or assume they aren’t trusted, and they disengage or deliver exactly the level of effort they believe the leader expects of them.
Federman argues that the fix starts before you assign anything. Define the assignment. What is it, specifically? When does it start and end? What skills does it require? What motivations or working styles does it fit? What does success look like? Leaders often skip this work, then blame employees for confusion or failure. But confusion is rarely the employee’s fault when expectations were never clear. Therefore, clarity is a prerequisite for fair delegation and real development.
The Mini-Me Trap and the 25-Year Benchmark
Another delegation killer is what Federman calls “mini-me syndrome,” or the belief that others should do it like you do it. That belief often disguises itself as high standards. In reality, it’s usually a mix of stress, identity, and fear. Leaders who were promoted for being excellent individual contributors can struggle to let others learn in public, especially when deadlines are tight and reputations feel on the line.
Federman tells a story of a VP of Sales who was irritated that his team didn’t sell as fast or as well as he did. Federman asked him to think back to his first day selling. The leader admitted he was terrible. The coach’s question landed: why measure a six-month employee against a 25-year benchmark? Someone gave you a chance, and now it’s your turn to give someone else the chance.
The pressure leaders feel is real, and Federman doesn’t dismiss it. He argues that when leaders let stress drive them, the stress leaks into control. They jump in, take over, and unintentionally communicate, “I don’t trust you.” That message not only hurts feelings but also reduces initiative, increases dependency, and makes the leader’s workload heavier over time. In his view, leaders need a “relief valve” to manage their stress, because otherwise their people absorb it and performance suffers.
Meeting People Where They Are During Change
Delegation doesn’t happen in a vacuum. It often intersects with change, and change reveals readiness differences. Federman introduces the Fast Forward Model, describing five stages people move through with any change: no way, maybe, prepare, act, and routine. The leadership mistake is treating those stages as irrelevant and applying a one-size-fits-all strategy.
He uses a practical example: organizations roll out a new system and immediately send everyone to training, but a chunk of the group is sitting there thinking, “This is BS, I’m not doing this.” They’re in the “no way” stage, so training doesn’t land. Weeks later, when they’re ready, they ask to go back and are told, “You’ve already been.” That pushes them back into resistance, not because they’re stubborn, but because the system punished their readiness.
In the “no way” stage, leaders need to ask questions that uncover concerns and perspectives. What worries you about this? What would make this feel safer? What information would help you see the value? Leaders who default to “get on the bus” language increase sabotage, turnover, and quiet quitting whereas leaders who meet people where they are create movement.
Time, Reflection, and Value: The Ingredients Leaders Skip
Federman identifies three ingredients that drive growth: time, reflection, and value. The irony is that everyone understands this when they think about their own growth. Meaningful change takes months. It involves struggle, experimentation, and pauses to make sense of what’s happening. Yet leaders assign tasks as if competence should appear immediately, and when it doesn’t, they take the work back.
Reflection is often the first casualty. When an employee struggles, leaders rush to provide the answer. That solves the immediate problem, but it robs the employee of processing, which is where learning consolidates. Even when someone gives you the “right answer,” it doesn’t always stick until you come to terms with it yourself. Leaders who ask guiding questions help employees build the internal framework for future decisions.
Value is the third ingredient, and it matters more now because expectations at work have shifted. People want purpose, flexibility, learning, and a healthy culture. They also recognize that loyalty is not guaranteed on either side. Federman argues that leaders mislabel employees as entitled when they ask, “Why me?” or “What’s in it for me?” He sees those questions as intelligence. People are evaluating whether an assignment is a growth opportunity or just a burden.
That means leaders need to get good at articulating value. Why is this important to the company? Why did I pick you? Why do I think you’ll succeed? Why will this be good for you? Those answers create motivation and confidence while making expectations clearer.
Feedback That Invests in the Future
Feedback is supposed to be part of growth, but Federman believes most feedback fails because it either avoids hard truths or delivers them in ways that trigger fear and shutdown. His alternative is what he calls investment feedback, similar to the concept of feedforward. The idea is to help someone get from point A to point B instead of trapping them in point A with a list of what went wrong.
He makes an important point: most employees already know when they blew it. They don’t need a manager to replay their embarrassment. What they need is a leader on their side, someone who acknowledges the disappointment but quickly turns the focus toward what to do next time. That shift communicates faith in the person’s ability to grow, and it gives them options they can test and learn from.
Praise fits into this, too, but only when it’s authentic. Federman warns against robotic systems that require leaders to praise on a schedule. People can feel when it’s performative. Real praise lands when it’s timely, specific, and human.
Staying in the Coach Role
Federman’s closing idea is simple but demanding: leaders are the coach, not the player. The easiest way to fall back onto the field is to never define the boundaries in the first place. If a leader and employee agree on milestones, check-ins, and what support looks like, it becomes easier for the leader to stay off the field. It also gives the employee language to push back respectfully: “Remember, we said we’d review this at the next milestone.”
He also recommends that leaders track their impulses to take over, not as a guilt exercise, but as a learning practice. When you feel the need to jump in, write it down. Come back later and ask what triggered it. Was it a legitimate risk or discomfort with a different approach? Reflection is a leadership skill, not an employee-only one.
Ultimately, Federman’s message is a warning and an invitation. The world is changing faster, and organizations that treat growth as optional will struggle to stay relevant. Delegation is a strategic lever for building capability, resilience, and adaptability.
Lessons to Carry Forward
Delegation becomes transformational when leaders stop treating it as a way to clear their inbox and start treating it as a way to build relevance. That shift requires leaders to give people time to learn, space to reflect, and a clear understanding of why an assignment matters. It also requires leaders to replace mini-me expectations with coaching behaviors, meeting people where they are in change and offering feedback that invests in future performance instead of punishing past mistakes.
When leaders hand back ownership, like Brad did with Olivia, they become more effective. They stop being the hero of someone else’s growth story and start being the coach who helps others learn to drive.
Brandon Laws is a workplace culture and leadership enthusiast, host of the Transform Your Workplace podcast, and VP of Marketing and Product at Xenium HR.