Congratulations. You got promoted.
Now you're sitting in a meeting where someone is crying about a coworker, and you're supposed to know what to do. Yesterday your biggest problem was a tricky spreadsheet. Today you're responsible for another human being's career development.
No one tells you this part. They tell you "you'd make a great manager" and hand you a team and a Confluence page titled "Management Resources" that hasn't been updated since 2019. And then they expect you to figure it out.
I've been there. I managed my first team with roughly the same preparation you'd get for assembling IKEA furniture: a vague diagram, no words, and the creeping suspicion that there were extra pieces. It took me a while, some excellent mentors, and a lot of mistakes to figure out what actually matters.
At EasyPost, I built a team of sixteen support engineers and eventually replaced myself with three team leads. That experience sits behind a lot of what follows: the work had to keep going without every decision coming back to me. You can read more about my management background here.
Here's the guide I wish I'd had.
First, the mindset shift
You may miss being the person who could just fix the problem and get on with the day.
You were probably great at your job. You shipped things, you solved problems, you were the person everyone went to when something was broken. That's why they promoted you.
Those skills still help. But if every difficult task ends up back on your desk, your team will spend a lot of time waiting for you. You need to help other people do work you used to handle yourself.
This means:
- You'll watch someone do a task slower and differently than you would, and you need to let them.
- You'll sit in meetings that feel unproductive until you realize someone needed that conversation to understand a decision or raise a concern.
- You'll end days feeling like you "got nothing done" because your old definition of productivity doesn't apply anymore.
It can take a while to notice the value of work that doesn't end with a ticket you can close.
The stuff that actually matters in your first 90 days
I'd start with these conversations and habits.
1. Build trust before you build anything else
You have a team. Some of them probably wanted your job. Some of them are skeptical. Some of them are just watching to see what kind of manager you'll be.
They'll be watching whether you keep your commitments and what happens when someone disagrees with you.
Schedule a one-on-one with every person on your team in your first two weeks. Leave enough room to ask about their experience of working there:
- What's working well for you right now?
- What's frustrating you?
- How do you like to receive feedback?
- What does your manager do (or not do) that drives you crazy?
Give them time to answer. Don't problem-solve in the moment. Don't defend the previous manager. Just take notes and say, "Thank you for telling me that."
Afterward, check back on anything you said you'd do.
2. Set expectations with your own boss
New managers make two classic mistakes: they focus entirely downward (on their team) and forget they also manage upward (to their boss). Or vice versa.
The job description probably leaves a few things out. Ask your boss:
- What does success look like in six months?
- How do you want me to communicate with you? (Weekly email? Slack? Standing meeting?)
- When should I escalate vs. handle something myself?
- What did the previous person in this role do well? What should I do differently?
Write the answers down. Reference them. Revisit them if priorities change so you aren't still working toward something your boss has quietly dropped.
3. Understand before you change
Before you change a process, find out what problem it was supposed to solve. Ask the people using it where it helps and where it gets in their way. You may discover a good reason for something that looked ridiculous from outside. You may also discover that everybody has hated it for two years and was waiting for someone to ask.
You don't need to observe an obviously harmful situation for a ceremonial month. Address urgent problems; make smaller, reversible changes with the team. Save the grand reorganization until you understand what you're reorganizing.
4. Learn to give feedback (the real kind)
It can feel awkward to tell someone their work needs to change, especially if you were peers last week. Start with a recent example.
For example: “In today's client call, you started answering twice before Maya had finished. I'd like us to let each person finish before adding to their answer. What was happening from your side?”
Then listen. Maybe there's context you missed. Maybe there isn't. Either way, you're discussing something observable and a change you can agree on, instead of presenting your interpretation of everyone's feelings as established fact.
A few useful defaults:
- Give feedback while the example is still easy to remember. If you've waited, acknowledge the delay and have the conversation anyway.
- Positive feedback is just as important as corrective. Don't only show up when something's wrong.
- Explain what worked. “The way you structured that proposal made the options easy to compare” gives someone more to repeat than “great job.”
- Give corrective feedback privately as a default. Ask how people prefer to receive recognition; not everyone wants to be the surprise subject of an all-hands announcement.
5. Protect your team's time and energy
Before you accept another request for your team, check what they're already committed to.
Your team will be bombarded with requests from other departments, last-minute "urgent" projects, and meeting invitations that have no business existing. Your job is to filter that noise so they can do their actual work.
This means learning to say no. Or, more diplomatically, learning to say "not right now" or "let me understand the priority before I commit my team."
This is terrifying at first, especially if you're a people-pleaser. It helps when your own boss agrees on the priorities too. Then you have something to refer to when the next urgent request arrives.
6. Run good one-on-ones
If you do nothing else on this list, do this one. Regular one-on-ones give you a dependable place to notice problems and offer support.
Start with 30 minutes weekly or biweekly, then adjust together based on what they need. Protect space for their concerns, rather than filling it with your status questions.
That means you don't show up with a status update agenda. You show up and ask: "What's on your mind?"
Then you listen.
Some weeks it'll be about work. Some weeks it'll be about a conflict with a coworker. Some weeks it'll be about something personal that's affecting their focus. All of that is valid.
Your role in a one-on-one is three things:
- Listen to what they're dealing with.
- Coach them through it (ask questions before offering answers).
- Remove obstacles they can't remove themselves.
Don't let one-on-ones become the first thing you drop when work gets busy. If you need to cancel, reschedule promptly and keep the new time. Reliability matters more than a perfect calendar.
Common first-time manager mistakes (and how to avoid them)
I've made all of these. Learn from my pain.
Doing the work yourself instead of delegating
It's tempting to take over when you could finish the task faster yourself. Sometimes a deadline really does require it. But if it's Tuesday and the report is due Thursday, there's probably room to let someone work through it and ask you questions along the way.
Trying to be everyone's friend
You can be friendly without being friends. You can care about your team without going to happy hour every week. The moment you need to give someone tough feedback or make a decision they don't like, the friend dynamic becomes a liability.
You can be warm and still have a conversation that disappoints someone. Be clear about what you decided and give them room to respond.
Avoiding difficult conversations
If a problem keeps coming up, talk about it while there's time to work on it. Explain what you've noticed, ask what's getting in the way, and agree on what needs to change. Waiting until the performance review gives someone very little chance to respond.
Micromanaging (because you're anxious)
New managers micromanage because they're scared. If something goes wrong, it's on them now. So they hover, check in constantly, and review everything twice.
Your team feels this. It communicates "I don't trust you." Even if that's not what you mean.
The fix: Agree on what the result needs to accomplish, where mistakes would matter, and when you'll check in. Leave room for a different method that meets those requirements.
Not asking for help
Here's Pete's blessing: you don't have to figure this out alone.
Talk to other managers. Find a mentor who's been doing this longer and can help you work out what needs attention.
And if you want structured support from someone who's been in your shoes, that's what coaching is for.
Start with one conversation
At your next one-on-one, ask what your report needs more or less of from you. Listen, choose something you can act on, and follow through. You don't need to become an entirely different person by Monday. You do need to give them a reason to believe the conversation mattered.
I no longer offer coaching sessions (here's why). If this one hit close to home, or you'd like me to write about your version of it, send me an email.