Article
Making the Shift From Team Member to Leader
Getting promoted into management is exciting for about two weeks. Then you realize the job is nothing like what you were doing before, and nobody has really explained what it actually requires.
Getting promoted into management is exciting for about two weeks. Then you realize the job is nothing like what you were doing before, and nobody has really explained what it actually requires.
Here's what changes, and what to do about it.
Your old strengths don't transfer cleanly
As an individual contributor, you were measured on your output - what you built, closed, shipped, or delivered. That feedback loop was direct. You did good work; people noticed.
Management doesn't work that way. Your output is now your team's output, which means your name isn't on most of it, and the connection between what you do and what gets produced is less obvious. A lot of new managers respond by staying too involved in the actual work - reviewing everything, redoing things, jumping in when a project feels shaky. It feels responsible. It's usually counterproductive.
When you're doing work your team should be doing, you're not doing the work only you can do: setting direction, removing blockers, making judgment calls, developing people. Those things don't get done if you're heads-down in execution.
The adjustment isn't just about trusting people more. It's about redefining what 'doing a good job' means in this role.
Your relationships with the team are different now
If you were promoted from within the team, this is where things get awkward. You were peers with these people. You complained about the same things, sat in the same meetings, maybe went to lunch together.
Now you're the one writing their performance reviews and having the conversation when something isn't working. That's a real change, and acknowledging it - at least to yourself - is more useful than pretending nothing has shifted.
The managers who handle this well tend to be direct about it early. They don't become cold or distant, but they're also not trying to be everyone's friend. They're clear about expectations, consistent in how they treat people, and willing to have uncomfortable conversations when they need to. That combination earns more actual respect than trying to keep the old dynamic alive.
Being clear is most of the job
Most management failures trace back to unclear expectations. Someone didn't deliver what was needed - but if you're honest about it, they were never told precisely what was needed, by when, or why it mattered.
When you assign work, say what you want, when you need it, and what a good outcome looks like. That's not micromanaging. It's giving someone what they need to succeed.
Feedback works the same way. If something is off, say so soon and say it plainly. A quick direct conversation right after something goes wrong is easier for everyone than saving it for a formal review. It also gives the person a chance to actually fix it.
One habit worth building early: when someone comes to you with a problem, ask what they think the right move is before you tell them. They often have a good answer. And when they don't, working through it themselves builds the kind of judgment that makes them less reliant on you over time.
Managing up is part of the job too
This is easy to neglect when you're focused on your team, but it matters. The people above you need to understand what your team is doing, what's going well, and what's at risk. If they don't, your team is invisible - which means they're last in line when resources get allocated or opportunities come up.
This isn't about managing optics. It's about making sure your team has the support and runway they need. Get comfortable summarizing what your team is working on, flagging problems before they escalate, and asking clearly for what you need.
Decisions won't wait for perfect information
You'll frequently be asked to make calls before you have everything you'd want - about people, priorities, resources, direction. Waiting for more data is sometimes the right move. More often it's a way of avoiding a decision that needs to get made.
Indecision has real costs. It leaves your team without direction, signals that you're not confident in the role, and often lets a manageable problem grow into a bigger one. Making a considered call, being transparent about your reasoning, and staying open to adjusting when new information comes in is generally better than holding out for certainty that won't come.
What it actually takes
Consistency, follow-through, and clarity. Those three things cover more of effective management than most leadership frameworks will tell you. Be reliable. Say what you mean. Do what you committed to. Make decisions and own them.
The rest - the more nuanced parts of managing people and navigating organizational dynamics - you'll figure out as you go. But if you get the basics right, you'll have enough trust built with your team to work through the harder stuff when it comes up.