How to lead a team for the first time

Leading a team for the first time means doing a different job than the one that got you promoted.

As an individual contributor, you succeeded by being good at a skill: writing code, closing deals, running campaigns, analyzing data. Your performance was largely within your control.

As a manager, you succeed by improving other people's performance. The skill is understanding what's blocking someone else and helping remove it. Your performance is almost entirely mediated through other people.

That shift is the one most new managers underestimate. Here's what it actually looks like in practice.

The three things that matter most in your first 90 days

1. Learn before you change

You were probably given this role because you have strong opinions and good judgment. Resist using them immediately.

Your first job is to understand the current state: what's working, what isn't, why things are the way they are. The most common failure mode for new managers is arriving with a change agenda before they've understood the context.

Ask questions. Do 1:1s with everyone on your team in the first two weeks. Don't have an agenda. Listen. Ask: "What's working well that we should protect? What's frustrating? What would you change if you could?" You'll learn more from those conversations than from any amount of analysis.

Give yourself a 30-day moratorium on making structural changes. You can have opinions. You earn the right to act on them by demonstrating you've understood the situation first.

2. Establish a 1:1 practice

If you do one thing right as a new manager, make it this: hold weekly 1:1s and actually use them.

Not for status updates. For coaching, unblocking, development, and trust-building. Status can happen in writing or in team meetings. 1:1 time is for the things that don't happen in group settings.

A 1:1 that works looks like this: - First 10 minutes: what's on their mind (you listen) - Next 10 minutes: whatever you need to address (keep it focused, one or two things, not a laundry list) - Last 5 minutes: their development, longer-term thinking, or something forward-looking

Your job in a 1:1 is to ask questions, not answer them. "What's blocking you?" "What would you do if you had to decide right now?" "What do you think is the right next move?" The goal is to develop their judgment, not substitute yours.

3. Be explicit about expectations

New managers often assume people know what good looks like. They don't, not until you tell them.

In your first 30 days, have explicit conversations about: - What does excellent performance look like in this role? - How do I like to communicate and be communicated with? - When do I want to be looped in, and when should you just decide? - What's the decision-making framework: what's yours to decide, what's mine?

Ambiguity is the enemy of performance. The clearer you are about expectations, the less time people spend guessing and the more time they spend executing.

The hardest parts of being a first-time manager

Giving feedback when it's uncomfortable

This is where most first-time managers struggle most. Positive feedback is easy. Critical feedback, especially to someone who's been on the team longer than you, or who you like personally, is hard.

The instinct is to soften it so much it loses meaning. "You're doing great overall, but maybe just a small thing to consider..." The person walks away thinking everything is fine when it isn't.

Feedback that works is specific, behavioral, and timely. Not "you need to communicate better." Specific: "In the team meeting on Tuesday, you interrupted three people before they finished their thoughts. I noticed it affected how much others contributed in the second half."

And it has to actually be delivered. Not hinted at. Not sent in a long email hoping they'll read between the lines. Spoken, clearly, in a 1:1 where they can respond.

The kindest thing a manager can do is give someone direct feedback while there's still time to act on it. Waiting until a performance review is the opposite of kind.

Letting go of the work

You were probably promoted because you're excellent at something. Now other people are doing that thing, and they're doing it worse than you would.

This is real. And it's not a reason to take the work back.

Your job is to help them get better, not to be better than them yourself. Doing their work for them stunts their development, creates dependency, and scales to zero. You can't do everyone's job.

The shift is: your job is to ask better questions, give better feedback, and create conditions for their success. Not to be the best individual contributor on the team.

Managing people who are more senior or more expert

This happens frequently: you manage someone who has more domain expertise than you, or who was a peer before you got promoted.

The mistake is pretending to be the expert. You're not. And they know you're not.

The right frame: your job is to help them do their best work, not to know more than they do. Ask them to teach you. "Walk me through your thinking on this." "What would you do differently if you were me?" Expertise-deference, done well, builds respect rather than undermining your authority.

Your authority as a manager doesn't come from knowing more. It comes from making good decisions, being consistent, and following through.

The questions every first-time manager should ask themselves weekly

1. Who on my team is blocked right now, and what am I doing about it?
2. Who is growing, and who has plateaued. Do I know why?
3. What feedback did I give this week that I was tempted to soften?
4. Who haven't I had a real conversation with recently?
5. Am I spending my time on the most impactful things, or am I defaulting to the things I'm comfortable with?

The last one is particularly important. New managers often spend too much time doing individual contributor work because it feels productive. It is productive for them. Not necessarily for the team.

What nobody tells you

Management is not for everyone. This is worth saying plainly.

Some people try it, find that the satisfaction they got from doing the work doesn't translate to helping others do it, and go back to individual contributor work. That's a legitimate and often excellent choice. Senior IC tracks exist for a reason.

If you find yourself eight months in and still resenting the shift, still wishing you could just do the work yourself, still not finding satisfaction in the coaching and team-building parts, that's important information. Management is a calling as much as a skill, and not every excellent individual contributor will find it fulfilling.

But if you're three months in and still finding it hard: that's normal. The first year is genuinely the hardest. The skills are learnable. Most people who persist through the discomfort find their footing.

Practice your hardest management conversations: 1:1 feedback, performance issues, difficult team dynamics. AI coaching, free, no signup required.