I used to think this was just a cranky saying from impatient people who couldn’t delegate. Now, after three decades in the industry, I realize it’s uncomfortably true. But not for the reasons I originally thought.
Here’s the pattern. A team is struggling. They reach out for help. I come in, assess the situation, and put together a solid plan. Documentation. Frameworks. Step-by-step guidance. A beautiful PowerPoint if they’re lucky. I hand it over, dust off my hands, and wait for the magic to happen.
Nothing happens.
Weeks later, same team, same problems. The docs are sitting in a SharePoint folder unopened. The plan was “reviewed” in a meeting and never mentioned again. They’re still stuck.
My first instinct was always frustration. I gave you everything you needed! It’s all right there! Why won’t you just follow the plan?
But then I realized something that should have been obvious. If they could take my plan and execute it, they probably wouldn’t have needed me in the first place.
This isn’t a dig at these teams. It’s just reality. When someone is struggling, there’s usually a reason. Maybe they lack the experience to know what good looks like. Maybe they’re underwater and don’t have bandwidth to absorb new information. Maybe the organizational dysfunction that caused the problem will also prevent the solution. Whatever it is, the gap between “here’s a plan” and “plan successfully executed” is enormous. And that gap is exactly why they called for help.
So now when a struggling team comes to me, I know I have three options.
Option one, lean all the way in. Roll up your sleeves and do the work yourself, or pair so closely with the team that you’re essentially doing it with them watching. This works, but it doesn’t scale. You become a bottleneck, and they don’t build any muscle. It’s like doing your kid’s homework for them. The assignment gets turned in on time, but they didn’t learn anything.
Option two, accept limited impact. Send the docs, give the advice, and make peace with the fact that maybe 20% of it will stick. That’s not failure. That’s reality. Some help is better than no help, even if it’s not the transformation everyone hoped for.
Option three, change the system, not just the team. Sometimes the team isn’t the problem. They’re downstream of broken processes, bad incentives, or impossible expectations. All the plans in the world won’t fix that. The intervention needs to happen at a different altitude. Think of it like a doctor treating symptoms when the real issue is the patient’s environment. You can prescribe medicine all day, but if they’re going home to the thing that’s making them sick, the medicine isn’t going to help.
What doesn’t work is the fantasy I used to believe in, that I could simply transfer my knowledge via document and competence would follow. That’s not how it works. Knowledge doesn’t automatically become capability. Plans don’t execute themselves.
These days, when someone asks for my help, I try to figure out early which situation I’m walking into. How much can I realistically invest? What level of lift is this team capable of right now? What’s actually blocking them? Is it skill, capacity, or something structural?
And sometimes, if it really matters and there’s no other way, I just do it myself.
Not because I’m impatient. Because I finally understand the assignment.