When Stepping In to Help Your Team Is Actually Holding Them Back
The project is running late. A manager is struggling with a decision. You can see the answer almost immediately, because you have solved this kind of problem hundreds of times. So you step in. The issue gets settled, the customer gets an answer, everybody moves on. The result looks good. There is another result you just haven't measured yet. What did the person learn about their own abilities? This is an expensive habit in a successful business. You want a stronger leadership team. You want people who can make decisions and carry responsibility. But the very experience that made you successful keeps pulling you back into the work you need others to own. Our napkin today carries one simple thought. Thrashing and swimming can look a lot alike.
From Edge of the Napkin, Episode 410 of Paper Napkin Wisdom.
When Helping Becomes the Problem
Some recent leadership coaching conversations have brought this into focus for me. The example below combines details from different situations to protect the people involved.
Consider a woman who spent years building a company people respect. She knows her business extraordinarily well. Her standards are high, and her people trust her judgment. She is proud of being available whenever someone needs her.
As the company grows, she wants her management team to take on more. So she gives people bigger assignments. She asks them to make more decisions. Ownership gets encouraged. And she stays nearby.
When a project starts slipping, she lets them fail a little, then gets involved. A difficult customer conversation goes sideways, and she lets them drown a little before supplying the answer. Someone approaches a problem differently than she would, so she lets them talk it through and then redirects them gently and kindly.
Most of the time the immediate results are good. A customer gets an answer. A project keeps moving. From her perspective, that looks like leadership.
Underneath that success there is something worth noticing. She is still making the important decisions. Her people are getting better at bringing problems to her. They are getting better at waiting for her direction. And they stop preparing quite as hard.
Here is the part that makes it difficult. She genuinely wants them to grow. Other leaders have heard her encourage exactly this, to step back and let a team learn through mistakes. She understands the principle and believes she is applying it. Her approach is to give people room to struggle, but only to a point. When things look like they are tipping, she steps in.
It's not a shortage of care, it's a shortage of room to learn.
From a Distance, Effort Can Look Like Failure
Picture a swimming pool with seats high above it. Someone is moving their arms rapidly. Their legs are kicking. Water is flying everywhere. There is a tremendous amount of effort in motion.
From that distance it might look like they are struggling. Maybe they are. Now picture Michael Phelps or Summer McIntosh pushing through the water. Plenty of turbulence, plenty of splashing, an enormous amount of work. They are swimming exceptionally well.
The difference isn't how much water moves, it's what's actually happening underneath it. From further away, it gets harder to tell.
Leadership has the same problem. A difficult conversation can sound messy before it becomes useful. Someone learning to manage people may take longer to find the right words. A first attempt at solving a problem can look inefficient beside the polished answer you have been trained to give after 20 years. That isn't evidence they can't do it. It may be evidence they are doing it for the first, second, or third time.
Where the boundary sits
There is a boundary, and it matters. If someone's safety is at risk, you intervene. A workplace health and safety issue is the same. Where a mistake could cause serious, irreversible harm, you protect people. You don't let a preventable disaster happen to prove a point about development.
Real swimming pools need lifeguards, and so does a business in its own way. But a lifeguard doesn't jump in every time someone splashes. Knowing the difference is the job.
And I wonder how many leaders confuse their own discomfort with someone else's emergency. You can feel anxious watching a junior leader take an unfamiliar path. The discomfort is real. Their inability is still an assumption. The minute you treat that assumption as a fact, you step across a boundary that should have belonged to them.
Why the Fastest Leader Becomes the Slowest Company
You may have become successful by being the answer. Customers trusted your judgment. People came to you because you fixed things. Over time, your speed became part of your value.
Then something interesting happens. Your ability to solve problems becomes the reason everybody expects you to solve them. You tell people to take ownership, and you keep taking it back. Decisions are supposed to sit with them, yet every difficult one somehow returns to your desk. Initiative is what you asked for, and the moment someone tries a new approach you correct it before they find out whether it works.
The team learns something from that behavior. The answer lives with you. Even if you never say those words, your actions mean them.
Sometimes this hides inside the best of intentions. The leader tells themselves they are protecting the customer, maintaining standards, keeping the team moving. Those are real possibilities. But when every exception gets returned to the same person, how can anybody tell whether the team lacks judgment or simply lacks permission to use it?
An employee who gets interrupted five times learns to bring half-finished problems to the boss. They stop finishing the thought themselves. Notice whose habit started the cycle. Every rescue teaches somebody what to expect next time.
There is a second cost that goes unseen. They don't just stop making decisions, they stop preparing as thoroughly. Why carry the full weight of a choice when someone else will carry it for you?
Your team may move a little slower today. The leader who is always the fastest person to the answer can become the slowest part of the whole company, because eventually everything has to pass through them.
The Other Side of the Same Story
Now think about a man being asked to carry a responsibility he has never carried before. He is capable. Knowing the business is not his problem, and people respect him. This particular assignment stretches him.
He has to lead an important conversation with other managers. There are competing opinions, and some difficult decisions need to be made. Contributing to these discussions is familiar to him. This time the outcome is his.
So he thinks through the people involved. He thinks about what he needs to accomplish. Then come the parts that make him uncomfortable, and he works through those too. He asks for guidance beforehand, and his coach isn't going to take over when things get hard.
The conversation happens. There are uncomfortable moments. Some questions are harder than expected. He has to listen carefully, make decisions, and keep the discussion moving. He gets through it. It was awkward and clunky.
Afterward, something changed. He has evidence that he can do this, and he understands how he could prepare differently next time. That experience belongs to him. He earned it through preparation, action, and the willingness to work through the difficulty. The same way you learned it.
Imagine the same assignment with a senior leader stepping in every time the conversation got uncomfortable. The discussion might have gone more smoothly. The person leading it would have learned something entirely different. Perhaps that he wasn't ready, or that the answer still needed to come from someone above him.
Two leaders, the same principle from opposite sides. One keeps removing difficult work from people's hands. The other builds confidence because the responsibility stays where it belongs. It's not abandonment, it's support that leaves the ownership in place.
Preparation changes when ownership is real. And ownership becomes real when the leader lets the person finish the work.
Five Things Worth Noticing
1. A fast answer can create a slow team. You can solve today's problem in minutes. If every problem needs that answer, the business starts waiting for one person. Decisions back up. Managers hesitate. Notice who is making the decisions, not just how quickly they get made. The long-term measure is whether the next decision can happen at a greater distance from you.
2. Your discomfort is poor evidence of their incompetence. Watching someone struggle is uncomfortable, and that feeling belongs to the observer. It doesn't establish what the other person can do. Before stepping in, look at what is actually happening. Is the person making progress? Are they asking better questions? Do they understand the risk? A longer route may still be a useful route.
3. Responsibility needs boundaries, not constant rescue. Decide what the manager can own and what must be escalated. Set a point for checking in. Be specific about the risks the business cannot absorb. Then let judgment develop inside those limits.
4. Every rescue teaches a habit. When difficult work keeps coming back to you, some people stop preparing as thoroughly. Others bring half-formed problems forward, expecting the final answer from above. The leader then treats that dependence as proof the team isn't ready. Notice how much of that dependence has been taught. The pattern changes when you change what happens after someone asks for help.
5. Confidence grows through decisions people own. Someone can hear that you believe in them a hundred times, and that encouragement matters. Making a decision, seeing what it produces, and adjusting afterward gives them something different. Momentum comes from experience the person actually carried.
Judgment comes from carrying a decision far enough to experience what it produces. It comes from noticing something you missed, from discovering your first idea doesn't work, from recovering, asking for help, adjusting, and getting to the other side. That experience can't be transferred in a meeting.
One Different Move This Week
Choose one situation where you usually step in. Make it something with room to learn. A sales discussion, a staffing decision, a customer issue with a manageable downside. Important enough to matter, and obviously not dangerous.
Before the work starts, agree on the boundaries. Name the point at which you must intervene: a safety issue, a legal obligation, a financial exposure the business can't accept. Then let the person carry the decision inside those boundaries.
When you feel yourself reaching for the answer, ask one question instead. What are you seeing that I'm not? Listen to how they understand the problem. Ask what they plan to try, and how they plan to prepare. Walk through the preparation with them. Practice it two or three times if that helps. Then let them make a choice you might not have made, as long as it stays inside what you agreed.
Afterward, ask what worked and what they noticed. Let them describe what they would do differently. You might be surprised by how they were thinking.
The point isn't to have a perfect week. The point is to give someone an experience they can actually own.
Maybe the team doesn't need another answer from you. Maybe they need you to notice what's happening before they decide they need help. There is a person on your team right now who may be capable of more than you have allowed either of you to see. Give them a chance to show you this week. Because thrashing and swimming can look a lot alike.
Related Insights
If most of the hard decisions still come back to your desk, it is worth finding out how much of the business is still running through you. The Subtraction Test
Wisdom Weekly. Get Wisdom Weekly, a short Sunday letter on leading what you have built. Subscribe to Wisdom Weekly
Comments