Field note · November 16, 2026
Leadership Growth: When Your Experience Only Works Through You
By Todd McKeever

Every experienced leader knows the meeting that cannot start until he arrives. The team is competent. The information is on the table. Nobody is shirking. But the decision waits, because the one person who can weigh the trade-offs is still driving in, or on a plane, or supposed to be on vacation with his phone face down on the counter, lighting up.
It is flattering, being the person the room waits for. It feels like proof that the years added up to something. After twenty or thirty years of building judgment, why would it not feel good to be the one who can make the call nobody else can make?
Here is the harder reading of that same scene. If the decision cannot be made without you, then something you know has never been converted into anything anyone else can use. Your experience is real. It is also stranded.
The cost runs in both directions. The team's hardest problems queue up at one desk. And the leader cannot step toward anything new, because everything he currently holds would wobble the moment he loosened his grip. He has not built people who extend his judgment. He has built a schedule that imprisons it. An organization whose hardest calls live inside one person's head does not have that person's strength. It has his ceiling.
The growth question changes in mid-career
Early in a career, growth means acquiring. You gather skill, scope, and scar tissue. You learn to read a room, run a meeting, spot a weak plan before it costs money. The growth is in what accumulates in you, and it should be. Nobody can transfer what he has never carried.
Somewhere in the middle years, the question turns around. The leader who keeps asking only "what do I need to learn next?" is answering a question his season has already retired. The live question is different: what do I know that still only works when I am the one doing it?
That question is uncomfortable because it audits the years instead of admiring them. Most experienced leaders can list what they are good at. Far fewer can point to the specific judgments, the calls they make almost without thinking, that would simply stop happening if they were gone for a month. Growth at this stage is not measured by what has accumulated in the leader. It is measured by what still works when he is not in the room.
Why judgment resists being handed over
Tasks delegate cleanly because tasks are visible. You can watch someone run the process, check the output, and correct the error. Judgment does not work that way. Judgment is compressed. The experienced leader looks at a situation and the pattern announces itself, and half the steps he took to get there happened too fast for him to report. Ask him how he knew, and he will say "experience," which is completely true and completely useless to the person standing next to him who needs to make the same call next week.
Underneath the instinct there are usually a thousand observations folded together: what he looks at first, what he compares against what, which causes he rules out before he entertains the obvious one, and the one or two things he has learned never to do. None of that transfers by osmosis. It transfers only when somebody unfolds it on purpose, step by step, in a form another person can pick up and use when the expert is not there to consult.
There is a quieter trap here, too. Explaining your reasoning well feels like handing it over. It is not. A clear explanation proves the explainer understands. It says nothing about whether the listener can now perform. One thing I never do is confuse a confident explanation with evidence that someone can do the work. Transfer has not happened until the other person makes the call, on a live situation, and the call holds.
A worked example: the performance problem
Consider one piece of judgment nearly every experienced leader carries: knowing when an employee's performance problem calls for coaching, when it calls for changing the working conditions, and when it calls for accountability. An experienced leader often recognizes the difference within a few conversations. A newer manager may respond to all three situations the same way, usually with whichever response his temperament prefers.
Unfolded, the judgment looks like this. I begin by looking at what changed. Has this person performed successfully before? Is the expectation actually clear? Does the employee have the authority, equipment, training, and time to deliver? I compare what the employee says with what I can observe, and I listen for whether the problem comes from lack of skill, competing priorities, unclear expectations, or a repeated choice. I rule out circumstances the employee cannot control before I decide the problem is unwillingness.
Written as questions a newer manager can carry into the room, the judgment becomes usable: Can the employee explain what successful performance looks like? Has he demonstrated the required skill before? Are the necessary resources, time, and authority available? What specific evidence shows where performance is breaking down? What response would actually address the cause?
And the decision rule underneath: if expectations are unclear, clarify them. If capability is missing, teach and practice. If the working conditions prevent success, remove the obstacle. If expectations are clear, capability exists, conditions are reasonable, and the employee repeatedly chooses not to meet the standard, then move to accountability, and document the evidence supporting the decision. That is the same judgment the experienced leader was making all along. It is simply no longer trapped inside him.
The thinking transfers first. Authority has to transfer separately.
There is a second half to the handover that most leaders skip, and transfers die there quietly. Understanding a decision is not the same as holding the authority to make it. That distinction matters most exactly where the decision concerns employee discipline, financial commitments, safety, or legal exposure.
So before the worksheet changes hands, the authority lines get named in three lanes. Decide independently: what the person may decide and act on alone. Consult first: what he may work through, but must talk over before acting. Escalate always: what must come to you or above you, every time, no matter how clear the answer looks.
Skip this step and a predictable thing happens. The newer manager reasons well, reaches the right call, and then hesitates, because nobody ever told him whether he is permitted to make it. He brings it back to you "just to be safe." You decide it, just this once. And the transfer is undone, not by incompetence on either side, but by a boundary nobody drew. A worksheet that teaches the right thinking while leaving the next person unsure whether he is allowed to act has transferred knowledge, not responsibility. The authority lines are what make the transfer real.
Let it break where you can see it
The written form is not finished when you are satisfied with it. It is finished when somebody else has used it on a real case and you have watched where it breaks.
Give the newer manager an actual performance situation. Ask him to work the questions and recommend a response without your involvement. Watch for three things. Can he distinguish evidence from assumptions? Can he identify a problem in the system rather than automatically blaming the individual? Can he explain why his recommended action fits the actual cause? If he cannot, that failure is not an embarrassment. It is a precise reading of where your instructions stopped being useful.
Then fix the break in the form, not by taking the work back. Suppose he recommends disciplinary action because an employee repeatedly misses deadlines. Further examination reveals the employee is receiving conflicting priorities from two supervisors. The manager followed the checklist and read repeated failure as repeated unwillingness. The worksheet was missing a rule, and now it has one: before treating repeated failure as unwillingness, verify that the employee controls the conditions necessary to succeed. Add the rule, hand him another situation, and watch whether the improved form produces better judgment without your explanation holding it up.
That loop, write it, test it, repair the form, is the whole discipline. Every pass makes the judgment less dependent on the person who first earned it.
One move to make this week
You do not need a program for this. You need one piece of know-how and thirty honest minutes.
Name one piece of know-how that currently stops at you. Then write how you actually do it: what you look at first, what you compare, what you rule out, and the thing you never do. Five or six plain sentences are enough to start. You are not writing a manual. You are finding out whether your judgment can survive being written down, which is the first test of whether it can survive being handed over.
If you want the full worked example with the complete worksheet, the five questions, the decision rule, the authority lines, and the final test for whether it works without you, it is in the paid membership library as The Works Without You Worksheet, alongside the rest of the member tools.
Because here is the sentence this whole week stands on. Your experience is not the legacy. What someone else can use is.
The teaching stays free, here and every week. If you want to work a decision like this one through together, that happens in paid membership.