Pages But Not Progress
A deliverable ends when the pages are done. An outcome ends when something improves.
Somewhere in a lot of organizations there’s a binder on a shelf.
It came from a consulting firm. Cost real money. Arrived with a presentation, a framework, and maybe a roadmap. The recommendations were probably reasonable. Some of them were genuinely good.
None of it was ever implemented.
Part of my onboarding at one point in my career was being handed exactly that binder. It was how I was supposed to learn what a system could do. Not what it did. No plan behind it. No resources dedicated to it. Just pages of what was possible from someone who had already moved on to the next engagement.
I’ve thought about that binder a lot since.
Not because it was unusual, but because it wasn’t.
There’s a version of help that feels like help but is actually designed to keep you dependent on the helper.
The manager who answers every question directly, immediately, and completely feels like a resource. What they’re actually doing is making sure the team never has to think without them. Every answer creates the next question. The manager stays indispensable. The team stops growing.
The consulting firm that delivers recommendations without implementation has the same dynamic, whether they intend it or not. The binder creates the follow-on engagement. The client has pages but not progress. The next conversation starts with “we could help you implement this.”
It feels like service. It’s actually a grip.
The alternative is harder to sell because it looks like less in the short term.
The leader who delegates outcomes instead of tasks gives the team a problem to solve, not an answer to execute. It’s messier. It takes longer. The team makes mistakes they wouldn’t have made with tighter control. But they also develop the confidence to move without being told. Eventually they stop needing the same level of guidance.
That’s the goal. Not to make yourself unnecessary forever. To make yourself unnecessary for this problem.
A good thinking partner works the same way. They help you define what you’re actually solving for. They work through it with you, not for you. And when you’ve found the answer, they stop. Not because the relationship is over. Because the work is done.
I think about this in two distinct ways in my own practice.
Advisory is available when you need a perspective above the weeds. You define the problem. We work toward clarity together. You move forward on your own. That’s not a standing meeting or an ongoing retainer. It’s a conversation when you need one.
A project is different. I’m filling a role you don’t currently have for a specific, defined engagement with a clear outcome. When the outcome is achieved, the engagement ends.
In both cases the goal is the same. You leave better than you arrived. Clearer. More confident. Still independent.
That doesn't mean the relationship ends. It means if we work together again, it's because I helped. Not because I made myself hard to leave.
The dusty binder is a symptom of help that was never designed to end.
The question worth asking before you engage a consultant or advisor is how do they talk about success? If the answer is a deliverable, be careful. If the answer is your progress, you are in the right room.