Jesse Jacoby
The best analyst on a team I advised was promoted to lead it, and within six months she was drowning. Not because she had gotten worse at the work. She had gotten better. She was still the fastest, most accurate, most reliable person in the room. That was the problem. She kept doing the work instead of leading it, rescuing every deliverable, correcting every draft, absorbing every hard call rather than developing the people who should have been making them. Her team stopped growing. Her best people started leaving. And nobody could explain why the obvious choice for the role was quietly failing in it.
Her story is not unusual. It is the single most common leadership failure I see, and it is almost never diagnosed correctly. We call it a performance problem, a fit problem, a readiness problem. It is none of those. It is the predictable result of promoting someone for competence and then asking them to lead with judgment, without ever telling them those are two different things.
What Competence Rewards, and What It Hides
Organizations are competence machines. From the first day of someone’s career, the system measures what they can do. Did they hit the number, ship the code, close the deal, deliver the deck? Competence is visible, verifiable, and easy to reward. So we reward it, over and over, at every level. The people who accumulate the most of it rise fastest.
The trouble is that competence and leadership are not the same capability, and the gap between them widens the higher someone climbs. Competence is about execution: what I can do myself. Leadership is about judgment: what I can see that others can’t, and what I can help other people do. Those two things feel related, but they draw on almost opposite instincts. Competence says solve it. Judgment says notice who should solve it, and what solving it now teaches them, and whether it should be solved at all.
We promote people because they are the best at doing the work. Then we are surprised when they keep doing the work instead of leading it. But why would we be surprised? Doing the work is the only thing the organization ever rewarded them for.
The Transition Nobody Names
There is a moment in every career where the ground shifts. The capabilities that earned someone the role stop being the capabilities that make them effective in it. The individual contributor who lived by responsiveness, thoroughness, and personal output now has to lead through other people, which means letting go of the very behaviors that built their reputation.
This is the transition from competence to judgment, and almost no organization makes it explicit. We hand people a title and a team and assume the shift will happen on its own. Sometimes it does. More often the new leader keeps reaching for the tool that always worked, doing more, working harder, staying later, and cannot understand why effort that used to scale results now produces diminishing returns. Effort scales you. Judgment scales the people around you. Nobody teaches the difference until someone is already struggling to feel it.
The cruelty of this transition is that it punishes the strong. The more competent someone was as an individual contributor, the harder the shift, because their competence worked so well for so long that they have no reason to question it. Their instincts, which were assets a level ago, quietly become liabilities. And the feedback loop that would tell them so is broken, because everyone around them still sees a high performer doing high-quality work.
Why It Stays Invisible Until It’s a Crisis
The competence-to-judgment gap hides in plain sight because its early symptoms look like virtues. A new manager who does the hard work themselves looks dedicated. One who reviews every deliverable looks rigorous. One who takes the tough client call personally looks accountable. Nobody flags any of it, because in isolation each behavior is admirable.
The cost shows up later and somewhere else. It shows up in the direct report who never learned to handle the client because their manager always stepped in. It shows up in the team that cannot function when the leader is on vacation. It shows up in the quiet departure of an ambitious high performer who realized they would never get room to grow. By the time these symptoms are visible, they are attributed to the team, the market, or bad luck, almost never to the leadership behavior that produced them. The diagnosis arrives late, if it arrives at all.
Judgment Is Learnable, but Not the Way Competence Was
Here is the good news that most organizations miss: judgment is not a fixed trait you either have or lack. It develops. But it develops through a fundamentally different process than competence does, and that is where the whole system breaks down.
Competence is built through repetition and feedback on a task. You do the thing, you see the result, you adjust, you get better. Judgment is built through exposure to consequential decisions where the right answer is not obvious and the feedback is slow, ambiguous, or delayed. You cannot drill judgment the way you drill a skill. You develop it by making real calls in real conditions, reflecting on why you chose what you chose, and watching how it plays out over time.
That means the organizations that develop judgment well do something uncomfortable: they give people decision-making reps before those people have the title, and they resist the urge to rescue them from productive mistakes. They treat a high performer’s first ambiguous call not as a risk to be managed but as a developmental moment to be protected. This is the opposite of how most talent systems operate, which optimize for getting the work done correctly right now, and in doing so quietly starve their future leaders of the one thing that would prepare them.
Designing the Transition on Purpose
If the shift from competence to judgment is predictable, it can be designed for rather than left to chance. A few moves matter more than the rest.
Name the transition out loud. Tell people, before the promotion, that the job is about to change in kind and not just degree. The behaviors that earned them the role are not the behaviors that will make them succeed in it. Simply making this explicit spares people months of confusion and self-blame.
Give judgment reps early. Long before someone is promoted, put them in situations that require judgment, not just execution. Let them own an ambiguous decision, sit in on a call above their level, make a recommendation where the answer is genuinely unclear. Judgment built before the title is judgment they can lean on after it.
Protect the productive struggle. When a new leader makes a defensible call that turns out wrong, resist the reflex to take the decision back. Debrief it instead. The learning lives in owning the consequence and reflecting on it, not in being rescued from it. An organization that rescues too fast trains dependence, not judgment.
Change what you reward. As long as the visible, rewarded behavior is personal output, leaders will keep producing personal output. Start measuring and recognizing the things judgment produces: people developed, decisions delegated, a team that runs well when the leader steps away. What gets rewarded gets repeated.
The Cost of Leaving It to Chance
Every organization runs this transition. The only choice is whether to run it deliberately or accidentally. Run it accidentally, and you promote your strongest individual contributors into roles that neutralize their strengths, watch a predictable share of them struggle, and lose some of your best people twice: once as the leader who burns out trying to do everything, and again as the talented reports who leave because there was never room to grow underneath them.
Run it deliberately, and the same promotions become the moment your best people multiply their impact instead of capping it. The competence that got them there stops being a trap and starts being a foundation.
The next time one of your strongest performers steps into leadership and starts to struggle, resist the easy story that they were not ready. Ask a harder question instead: did anyone ever tell them the job was about to change, and did anyone help them build the judgment the new role would demand? If the answer is no, the failure is not theirs. It is the system’s, and the system is something you can redesign.
