Three months after the promotion, the pattern is usually the same. Your new manager is working longer hours than they ever did as an individual contributor. Their own output has dropped, which you expected. What you did not expect is that the team's output has dropped too. They look tired. When you ask how it's going, they say fine, and you both know that isn't the whole answer.
Almost everyone reads this as a sign they weren't ready. Sometimes that's true. Much more often, nobody told them what to stop doing.
A promotion is treated as addition. New title, more responsibility, and usually a much longer to-do list. But the move from doing the work to leading the work is mostly subtraction, and the things that have to go are the exact things that got them promoted. Nobody hands over that list, so the new manager keeps doing what made them excellent and wonders why it isn't working.
Here is the list. It's written for you, the person who promoted them, because they can't do this part alone.
They have to stop being the fastest answer
As an individual contributor, their value was obvious: they were often the best, fastest or most knowledgeable in their field. Someone asked, they answered, problems were solved. It was efficient and it felt good.
As a manager, answering instantly is a slow poison. Every quick answer teaches the team that the shortest path to a decision runs through them, which is precisely the dependency you were trying to break by promoting them in the first place. Six months of quick answers and they have rebuilt your bottleneck one level down.
What replaces it is slower and feels worse: asking what the person would do, waiting through the silence, and letting them proceed on an answer that is merely good rather than optimal. The first few times, this costs real time. It's the only thing that stops costing time later.
They have to stop doing the work because it's faster
Every new manager hits the same arithmetic. Explaining this task, double checking someone’s attempt and making fixes to it will take an hour. Doing it themselves will take twenty minutes. So they do it.
The arithmetic is correct once and wrong forever after. It also has an emotional pull that has nothing to do with efficiency: doing the work is where they know they're good, and management in month two is a stream of things they're bad at. Reaching for the familiar task is a way of feeling competent again for an hour.
Watch for the manager who is visibly busy but whose team seems underused. That's this, almost always.
They have to stop being liked in the same way
This is the one nobody warns them about, and the one that hurts.
Yesterday they were a peer. They complained about the same things, took the same breaks, sat on the same side of decisions. Today they have to allocate work, evaluate performance, and sometimes deliver news the team hates. Many first-time managers try to keep the friendship intact by softening every message, which produces the worst outcome available: the team is unclear, and the friendship becomes strained anyway.
The goal isn't for them to become cold. It's to accept that some decisions will cost affection, and that clarity delivered kindly is more respected than vagueness delivered warmly. The relationship changes shape. It doesn't have to end.
They have to stop measuring the day by their own output
The hardest habit to break is internal. For years they knew whether it had been a good day by looking at what they had finished from their list of tasks and projects. Now a good day might be one where they wrote nothing, shipped nothing, closed nothing, and instead unblocked four people, ran a decent one-on-one, and stopped a problem that would have surfaced two weeks later.
That day feels empty by comparison. It was probably their most valuable day of the week. Until someone tells them what the new scoreboard is, they will keep grading themselves on the old one and quietly concluding they're failing.
What this means for you
You can't outsource this to a course. Two days in a room can give them language and the relief of hearing that other managers struggle in the same places, but the subtraction happens in your building, with your work, and mostly in conversations with you.
Three things make the difference:
- Name what stops, not just what starts. Most promotion conversations are entirely additive: here's the title, here's the team, here's what we need from you. Add the other half. Tell them plainly which parts of their old job they are handing over, who is taking each piece, and by when. If you can't say what they're putting down, you haven't actually promoted them. You've given them two jobs.
- Tell them the new scoreboard. Say out loud what a good week looks like now, in terms that don't involve their personal output. Their team hit the deadline without you being involved. Someone on their team handled something they would have escalated last month. Nobody was surprised by anything in the Monday meeting. Whatever it is for your business, say it, because they will not guess it.
- Protect the first month. Thirty minutes a week, in the calendar, not "grab me whenever you have a question." Most new managers won't ask for help because asking feels like proof they shouldn't have been promoted. One question is enough to run the meeting: what did you do this week that someone else should have done? The answer is a map of what they haven't unlearned yet, and it gets more useful the longer you keep asking it.
When it isn't working
Sometimes the subtraction doesn't take. If, after a few months of real support, they are still doing the team's work at night, still answering every question themselves, still unable to sit through the discomfort of watching someone do it worse, then you may have a person who is genuinely happier and more valuable as a senior individual contributor.
That's a legitimate outcome and worth saying so, clearly, without dressing it up as failure. What makes it a disaster is leaving them in the role for two years because moving them back feels like an admission. Small companies can rarely absorb that.
The point of naming the gap before the promotion, and of giving people leadership reps before you give them the title, is that you find this out cheaply. Reps before the title covers how.
This is one spoke of the leadership bench, our model for building a leadership pipeline in a small company. See also why your promotions keep failing in the first 90 days.