How do you go from individual contributor to manager?

Why is going from individual contributor to manager so hard?

Because it changes who you are at work, not just what you do. The skills transfer slowly, but the sense of your own value has to move all at once.

The Center for Creative Leadership puts it plainly: stepping into management for the first time is “a fundamental shift of identity.” It adds that “success isn’t about your individual contribution anymore,” and that the habits that made you a strong individual contributor can make you a less effective new leader if you keep running the same script.

Part of the difficulty is how people get picked. When Gallup asked US managers why they were hired, they commonly cited their success in a previous non-managerial role or their tenure. In other words, you were chosen for being an excellent doer. The role then asks you to stop being judged on that.

Linda Hill makes a similar point in Harvard Business Review. She writes that “Most new managers initially fail this test” of becoming a boss, because of common misconceptions about what being in charge means. A common one in practice is believing the job is mostly the old job, plus some people stuff.

What is the expert trap?

The expert trap is when the expertise that got you promoted keeps pulling you back into doing the work, so your team waits for you instead of growing past you.

It rarely looks like a problem from the inside. It looks like being helpful. A deadline slips, so you take over. A report comes in rough, so you rewrite it. Something breaks at 11pm, so you fix it, because explaining it would take longer. Each choice is reasonable. Together they form a pattern: the hard problems belong to you.

The trade-off is simple. Doing is fast now and slower later. Every time you step in, today goes better and next month gets a little worse, because nobody else learned to handle it.

This isn’t only a new-manager problem. A McKinsey survey of managers, reported by Fortune, found they spend “about 31% on individual-contributor work,” and only about 28% of their time managing people. Even experienced managers drift back to doing. New ones start much closer to it.

What does the expert trap look like in a normal week?

It looks like a full, busy, productive week in which your team got slightly more dependent on you. Here’s a made-up but typical example.

Say you’re a senior analyst who has just been promoted to lead a team of 5. Your new week goes like this:

• Monday: a dashboard is due to the leadership team on Wednesday. One of your analysts is building it, but it’s going slowly. You quietly start your own version “just in case.”
• Tuesday: two people ask how to handle a messy data source. You know the answer, so you fix the query for them. It takes 20 minutes each.
• Wednesday: you send your version of the dashboard, not theirs. It’s better. The analyst sees it go out.
• Thursday: a stakeholder emails you directly with a question, skipping the analyst who owns the work. You answer, because you can.
• Friday: you skip your 1:1s to catch up on your own analysis, which is the work you actually enjoy.

Now count it up. If the McKinsey figure of about 31% holds for you, that’s roughly 12 hours of a 40-hour week spent doing rather than leading. In this example it’s probably more.

The cost doesn’t show on Friday. It shows in three months, when the analyst who built the first dashboard has stopped trying very hard, stakeholders route everything through you, and you’re working evenings to keep up. Nothing went wrong in any single moment. The pattern did the damage.

What habits pull experts back into doing?

A handful of small, repeated habits, most of them triggered by pressure. You don’t need to fix them all, only the two or three that pull on you hardest.

The common ones:

• Taking over when a deadline is at risk. The most natural rescue, and the one that teaches people the deadline was never really theirs.
• Rewriting work before it goes out. Small edits feel harmless. Repeated, they tell people their version isn’t the real one.
• Being the first call when something breaks. If you’re always the one who fixes it, you’re also the only one who can.
• Owning the next step. Someone brings you a problem and leaves without it. Now it’s on your list, not theirs.
• Keeping the work you love. The interesting problems, the technical deep dives, the bits you’re proud of. These are the hardest to give away and the most valuable to the people who need to grow.
• Checking every detail. Reviewing results is your job. Reviewing every line usually isn’t.

One habit gets its own post. If your instinct is to answer every question the moment it’s asked, read why new managers give answers too fast. It covers the coaching side of this, so here we’ll stay with the bigger shift underneath it.

How do you let go of being the one who knows?

By changing what you count as your contribution. As long as your sense of a good day depends on what you personally made, you’ll keep reaching for the work.

CCL says your definition of success “must now include the success of others.” In practice, that means a few deliberate changes.

1. Rewrite your scorecard. At the end of each week, list what your team finished, not what you finished. Note one thing someone did that they couldn’t have done a month ago. That’s your output now.

2. Hand over the work you enjoy most. It sounds backwards. The work you love is usually the work you’re best at, which makes it the best learning for someone else. Keep one small piece if you need to, and give the rest away with context, not just a task.

3. Agree what “good enough” means before the work starts. Most rewriting happens because the standard lived only in your head. Write it down, share it, and judge the work against that rather than against what you’d have done.

4. Let a rough version go out with their name on it. Not when the stakes are high, but often. A draft that’s a bit rough and theirs builds more than a polished one that’s secretly yours.

5. Move yourself off the critical path. If any of your own tasks would block the team if you got busy, hand it over or take it off the plan. A manager who is also the bottleneck can’t step back to see the whole team.

6. Say it out loud. Tell your team: “I’m trying to do less of the work myself. If you see me grabbing something that’s yours, tell me.” It turns a private struggle into a shared agreement, and it gives people permission to push back.

None of this means pretending you’ve stopped being an expert. Your knowledge is still useful. It just works differently now: through the questions you ask, the standards you set and the people you teach, rather than through your own hands.

Should a manager still do hands-on work?

Often, yes, especially if you lead a small team. Many leads are player-coaches by design. The question is whether you choose the work or the work chooses you.

A useful test is to ask three questions about any hands-on task you’re tempted to take:

• Does it genuinely need me? Not “would I do it better,” but “can nobody else do it at all yet?”
• Is it on the critical path? If you get pulled into meetings, does the team stall?
• Am I doing it because I chose to, or because I’m under pressure? Reaching for the keyboard when things get tense is the reflex to watch.

If the honest answers are “yes, no, chose to,” keep it. That’s a player-coach doing real work. If they’re “no, yes, pressure,” it’s the expert trap dressed up as helpfulness.

It also helps to make your hands-on time visible. Block it in your calendar, tell the team what you’re working on, and protect your 1:1s from it. Hidden doing is the kind that grows.

How do you know if you’re making the shift?

Watch what happens when you’re not there. The clearest sign of progress is work that moves forward, and problems that get solved, without you.

A few signals to look for over a month:

• People bring you problems with a suggested fix, not empty-handed.
• Stakeholders start going to the person who owns the work, not to you.
• You can take a day off without your phone filling up.
• Someone on your team does something well that you used to do, and it doesn’t sting as much as you expected.

Here’s a small experiment to start on Monday:

1. Pick one piece of work you’d normally keep. Ideally one you enjoy.
2. Hand it over with the why, the standard and the deadline. Then agree when you’ll check in, and don’t check in before that.
3. Keep a tally for the week. Each time you take over, rewrite or rescue, make a mark. Don’t try to change it yet. Just notice when it happens.
4. On Friday, ask the person how it went. “What would have helped more from me? What got in the way?”

You’ll probably find your marks cluster around a few moments, usually the same ones each week. Those are your habits to work on. If handing work over is the specific sticking point, the Delegation Detox looks at that in more depth.

Where do you sit between Doer and Enabler?

Most new managers sit somewhere in the middle, and the useful question is which habits keep pulling you back towards doing.

The Expert Trap is a free self-test for exactly this moment. It takes about 5 minutes, needs no sign-up, and your answers stay in your browser. It asks 14 questions about what you actually do when work gets stuck, rushed or nearly right, and places you on a dial between Doer and Enabler. It then shows the two habits pulling you hardest towards Doer, with one move to try on Monday. It’s a snapshot of where you lean, not a verdict: doing is fast now and slower later, and the result shows you where that trade is costing you.

If you’re still deciding whether management is for you at all, Career Compass can help you weigh the manager track against the expert one. For a wider read on how you lead, including how strongly you lean towards solving things yourself, try The 42 Test, which gives you your Leader Code. You’ll find more for this career moment in Stepping up, and if you now manage people who used to be your peers, see going from peer to boss.

You were promoted because you were good at the work. The job now is to make sure you’re not the only one who is.