By Andreas Pettersson, Founder, Leaders ADAPT
You got the job because you were good at the work. That is the trap. The book I wrote for managers says it in one line: most people are "promoted for being good at the work, not for being good at transferring the work." As a first time manager you now own a job nobody trained you for, and the skill that got you here is the one you have to stop using first.
I have hired more than 80 people and scaled a company past 150. The new manager I warn people about is not the weak one. It is the strong individual contributor who keeps scoring goals while the team watches from the side.
Most first time manager advice is a list of tips. This guide is a plan for the first 90 days: what changes, the four shifts, the cadence to install in week one, how to delegate, how to build authority without a title fight, and how to manage the person above you. There is also one habit I had to learn the hard way, near the end.
Quick answer: A first time manager should, in the first 90 days, meet every direct report one to one each week, learn what each person owns and needs, set explicit expectations in writing, hand over outcomes rather than tasks, hold one hard conversation early instead of letting a small problem grow, and tell their own manager about risks before deadlines, not after.
What changes when you become a first-time manager?
A first-time manager is someone leading direct reports for the first time, judged on the team's output rather than on their own work.
Everything else follows from that one sentence. Your calendar fills with conversations. Your own output shrinks, and it is supposed to. The problems that reach you are the ones nobody else could solve, which means most of them have no clean answer.
Here is the job you left next to the job you have now.
| Dimension | Individual contributor | First-time manager |
|---|---|---|
| Judged on | Own output and quality | The team's output and how it holds up without you |
| Main tool | Craft skill | Conversations: one-on-ones, feedback, delegation |
| Typical week | Mostly focused work | Mostly meetings, questions and decisions for others |
| Information | Knows their own work in detail | Knows less detail, must ask for what used to be obvious |
| Authority | Decides inside own work | Decides for others, within limits set above |
| Feedback loop | Fast: the work is done or not | Slow: results show weeks or months later |
| Main risk | Doing the work badly | Doing the team's work yourself |
The last row is the one that bites. Nobody gets fired in month two for doing too much of the team's work. They get stuck in year three for it.
The four shifts every first-time manager has to make
1. From player to bench
The line I use for this comes from sports. "The best players are not in the game, they're on the bench, overlooking everything. Can you go in and score a goal? Yeah, you can, but it doesn't scale."
It will feel worse before it feels better. When a co-founder I advise finally handed a big campaign to a junior person, I told him plainly: "there are days you're going to get pissed with it. That's okay, take 50/50 for now as a win." Half the work leaving your hands in month one is a good month.
2. From answers to outcomes
As an individual contributor you were paid for answers. Now you are paid for other people's answers. So stop handing out steps and start handing out results: what done looks like, by when, and how much authority the person has to decide along the way.
3. From being liked to being clear
New managers want the team to like them. Fine. Clarity does more for that than friendliness does.
I tell clients this directly: "Set real expectations. If your expectation is send me a text within one hour when shit happens, that's not micromanagement, that's setting expectations. If you don't set expectations, he will not please you."
4. From heads down to heads up
Your team reads your face, your silence and your calendar. If you do not tell them what is going on and why, they will fill the gap with the worst version. Say what is hard, say when it will get easier, and lead with the why.
What should a first time manager do first?
Put a weekly one-on-one with every direct report on the calendar before you do anything clever. Same day, same time, recurring, no end date.
Then use the first round of those meetings to listen. Ask what each person owns, what gets in their way, what they need from you, and what the last manager did that they want you to keep or drop. Write the answers down. You will use them for the next three months.
The second move is smaller than people expect: tell the team how you will work. When you hold 1:1s, how you want bad news (early and plain), what you will decide and what they will decide. The full list, week by week, is in the first-time manager checklist.
What should a new manager do in the first 90 days?
Think of your first 90 days as a manager in three blocks. They overlap, and that is fine. It is the same shape as most 30-60-90 day plan templates, with the goals I would actually put in each block.
- Days 1 to 30, learn the people and set the rhythm. Weekly 1:1s running, a weekly team meeting at a fixed time, one written page of expectations, and a list of what each person owns.
- Days 31 to 60, hand over outcomes. Pick three recurring things you still do and give them away with a clear result, a deadline and a check-in point. Expect some of it to come back. Hand it back again.
- Days 61 to 90, hold the standard. By now you know where the gaps are. Have the conversation you have been putting off, the one about the missed deadline or the attitude in meetings. The method is in how to have difficult conversations with employees.
At day 90, ask one question: if you disappeared for a week, what would stop? Whatever is on that list is your next quarter.
How often should a new manager hold one-on-ones?
Weekly, 30 minutes, for everyone during your first 90 days. The shipped 5-Minute Leader sets frequency by state, not seniority, and new relationships and people in transition get the weekly slot. You are in transition. So are they.
A simple split keeps the meeting from becoming a status report: about 40 percent their agenda, 40 percent your read on how they are really doing, 20 percent agreeing priorities and commitments. The question that does the most work is plain: on a scale of 1 to 10, what is your energy right now? Anything under 7 gets a follow-up.
And the rule I gave one founder, which applies double to you: never miss your one-on-ones. The first time you cancel one for something "more important", your team learns exactly where they rank. The full system is in the guide to one-on-one meetings. Later, once you have a manager or two under you, skip-level meetings do the same job one layer down.
How do you delegate as a first-time manager?
Start with your own calendar. For every task you did last week, ask: could someone on the team do this at 70 percent of my quality?
If yes, it goes on the list. Not 90 percent. Seventy.
Then delegate the outcome, not the task. "Send the weekly report" is a task. "Make sure the leadership team knows where we are every Friday without asking" is an outcome, and the person who owns it will improve the report on their own.
Check in when the work is about a quarter done, not at the end and not every hour. My shortest version of the whole method is four words: delegate, trust, but verify. The five-level approach, with the conversation that goes with it, is in delegation training.
The curse you will hit is the smart one. Your brain assumes that people can do what you can do, and you will keep being disappointed when they cannot. The answer is not to lower the bar. It is to grow the people until they reach it.
How do you build authority and trust as a new manager?
Authority is the set of decisions you are allowed to make; responsibility is the set of results you are held to. New managers almost always get more of the second than the first.
When a newly promoted leader tells me they feel stuck, I ask for one concrete decision they are responsible for but not allowed to make. There is always one. That gap is the thing to work on with your boss, not the thing to complain about to your team.
Authority grows in slices. I call it the salami strategy: you take a little more each time you show you can see the whole picture, not just your lane.
Communicate your plans before you act on them. Show the trade-offs you considered. Every clean decision earns you the next one.
Trust with your team comes from boring consistency. The 1:1 that happens. The feedback that arrives within a day or two instead of at review time. The promise you keep about the thing you said you would fix.
How do you manage people who used to be your peers?
Say it out loud in the first 1:1, because everyone is already thinking it. Something like: "This is weird for both of us. Our relationship changes a bit, and I want to talk about how."
Then treat the former peer exactly like everyone else, in both directions. Same expectations, same meeting, same standard, same credit. The two failures are the ones you would guess: being softer on friends, or being harder on them to prove you are not playing favorites. The team watches for both.
You will lose some of the casual closeness. That is a real cost, and pretending it is not makes it worse. What you keep, if you are fair, is respect, and respect is the thing a manager can actually use.
How do you manage up to your own boss as a new manager?
Your manager is now one of your main customers. Managing up is not flattery; it is making sure the person above you is never surprised. Two habits do most of the work.
First, bring bad news early. The pattern I describe to leaders: on a three-month project the person raises the flag two or three weeks before the deadline, when nothing can be fixed. Raise it at week three instead, with a plan.
Second, ask the question that changes the relationship. I recommend asking your own manager something like: what keeps you up on a Friday night, and what is coming down the pipe that I can help you attack before it is too late? It tells your boss you think about their problems, not only yours.
What skills does a first-time manager need most?
Five, in this order:
- Running a 1:1 that people want to attend.
- Handing over an outcome clearly, in about three minutes.
- Giving feedback within 24 to 48 hours, while it still means something.
- Holding one hard conversation without softening it into nothing.
- Asking for help before the deadline, not after.
None of these is a personality trait. All of them are reps. If your company offers training, take it and practice the five inside it; if it does not, the first-time manager training guide compares the options you can choose yourself. For the reading list, start with the honest shortlist of books for first-time managers.
The mistakes that follow first-time managers for years
The expensive ones are quiet: doing the team's work yourself, handing over tasks instead of outcomes, saving feedback for a review, hiding a slipping project until it is too late to save. The ten first-time manager mistakes page has each one with the fix.
Here is one of mine. I am Swedish, and the culture I grew up in does not celebrate loudly. In my US companies we had big wins that I acknowledged and did not celebrate, and people were confused about how I felt. In my own words: "I had to learn the hard way to be more positive and cheerleading and more woo." Your team needs to hear, in the room and by name, that a win was a win.
Still deciding whether to take the job?
This guide is for people already in the seat. If you have not said yes yet, take the should I become a manager fit test first. It scores whether you want the work of managing or mostly the title, and it treats a senior contributor path as a good answer.
If you are in the seat and wondering where managing ends and leading begins, the piece on leadership vs management and the transition point covers the next step up.
First time manager FAQ
What is the 30-60-90 rule for a new manager?
The 30-60-90 rule is a planning convention, not a formal standard. A new manager splits the first 90 days into three blocks: the first 30 days for learning the team and the work, the next 30 for making first changes and handing over work, and the last 30 for owning results. Each block has written goals agreed with the manager's own boss.
Can you be a manager with no experience?
Yes. Most people become managers without management experience, because the role is usually a promotion from individual contributor work. The gap closes through practice: weekly one-on-ones, delegating outcomes, giving timely feedback and holding hard conversations. Formal training helps when it includes practice, and a mentor or experienced manager to debrief with shortens the learning curve.
How long does it take to feel comfortable as a first-time manager?
There is no fixed timeline, and it varies with team size and support. A single habit, such as a weekly one-on-one, usually needs about three weeks of repetition to become automatic, and a change in how a manager thinks about the role takes longer, often a month or two of consistent practice. Comfort tends to follow a stable rhythm rather than a date on the calendar.
What are the best first time manager tips?
The most useful first time manager tips are habits rather than traits: a weekly one-on-one with each direct report that is never cancelled, written expectations, and delegating outcomes rather than tasks with a check-in when the work is about a quarter done. Feedback lands best within a day or two. Risks go to the manager's own boss early, and former peers get the same standard as everyone else.
Should a first-time manager get training?
Training helps when it is practice-based and spread over time, with real situations, role-play and follow-up. One-off lectures change little. A Chartered Management Institute survey with YouGov in 2023 found most new UK managers had no formal management training, so many first-time managers need to choose training themselves or ask their employer to fund it.
What should a new manager say to their team on the first day?
A new manager's first message should be short: what they are there to do, how they will work (weekly one-on-ones, how they want bad news, what the team decides versus what the manager decides), and that the first weeks are for listening. Big changes announced on day one usually fail because the manager does not yet know the work well enough.
The first time manager's real job
The title changed on a Monday. The job changes over the next 90 days, and only if you change the way you spend your week.
Put the 1:1s in. Hand over three things. Have the conversation you are avoiding. Tell your boss about the risk before it is a surprise.
Do that and by day 90 you will have something most first-time managers never get: a team that tells you the truth early. Everything else in management gets easier from there.
A first time manager needs a system small enough to survive a bad week
That is the reason I built The 5-Minute Leader. It packages the way I ran teams as a tech CEO for 10 years, including as one of Canon's youngest CEOs, into four protocols: a delegation protocol, a 1:1 protocol, an accountability protocol and a rhythm protocol, each with a first week you can run on Monday. The daily practice around them takes five minutes, because a habit that needs an hour a week does not survive your first bad month as a manager.
There is one question in the first week of the 1:1 protocol, the one set for Friday, that I would want every new manager to have asked by their second week. It is not the energy question. Start with The 5-Minute Leader and run the first week before you decide whether it fits.
