The first-time manager's playbook

Almost everything written for new managers is about what to start doing. The harder and more useful half is what to stop, because the behaviour that got you promoted is frequently the behaviour that will make you a poor manager.

What is the actual job now?

Producing results through other people, which is a different job rather than a bigger version of the old one.

The specific difficulty is that your old work still exists and you are still good at it. It is visible, satisfying, and finishable, and management is none of those things. So under pressure, new managers retreat into the work they know — picking up the tricky ticket, rewriting the deck themselves, taking the difficult client call — and tell themselves they are helping.

Every one of those decisions takes a development opportunity away from someone and adds you to the critical path. Six months later the team has not grown and you are the bottleneck.

The test worth applying weekly: what did I do this week that only a manager could have done? If the answer is nothing, you did your old job.

What should the first month be?

Listening, deliberately and on a schedule.

Book a proper one-to-one with everyone in the first fortnight and ask the same four questions of each: what is working, what is broken, what do you want to be doing more of in a year, and what should I know that I would not think to ask. Write the answers down.

The patterns across those conversations are the most valuable information you will get all year, and the window closes fast — after a month people start telling you what they think you want to hear. The mechanics of running these properly are in your first 1:1 as a new manager.

Resist fixing anything during this period except the obviously broken. You will be tempted, because fixing things is how you demonstrated value in your old role.

What is the one change to make early?

One visible thing that removes friction, in the first fortnight.

Not a reorganisation. Something small and unambiguously good: cancelling a status meeting nobody needs, unblocking an approval that has been stuck, getting a tool people keep asking for. It signals that you can actually move things and that you were listening.

Then stop, for about a month. A new manager who changes six things in three weeks has demonstrated that they judged everything before understanding any of it, and the team will wait out the rest of the changes rather than engage with them.

How do you set expectations without sounding officious?

Say them out loud once, plainly, and then be consistent.

New managers assume standards are obvious because they were obvious to them as an individual contributor. They are not obvious. What time do people need to be reachable, what gets escalated versus decided locally, what does "done" mean, how much notice for time off, when is it acceptable to miss a deadline if you flag it early.

Most of the performance conversations a new manager ends up having in year one trace back to an expectation that was never stated. It is much easier to say "I'd like risks raised the day you spot them, not at the sprint review" in week two than to have the conversation in month five about why a risk arrived late.

What is the most common first-year mistake?

Delaying the first small difficult conversation.

There is always one available in the first month — someone consistently ten minutes late to stand-up, a handover that keeps being skipped, a person who talks over others. It is minor, which is exactly why it is the right one to start with: low stakes, and you already know what you would say.

New managers leave it. The reasoning is always the same — I am new, I do not want to come in heavy, I will let it settle. What settles is the behaviour, into a norm. Six weeks later the same conversation now includes an implicit "and why did you not mention this before."

Have the small one in week three. The structure for it, and for the larger ones that follow, is in the complete guide to difficult conversations for new managers.

How do you manage people who were your peers?

By making decisions differently, not by discussing the change at length.

Name it once in the first one-to-one — "this is odd for both of us and I'd rather say so than pretend otherwise" — and then let your behaviour do the work. The awkwardness is resolved by consistency, particularly the first time you make a call that a friend on the team disagrees with.

Two specific traps. The first is over-correcting into formality, which reads as a personality transplant and is more unsettling than the promotion. The second is preserving one friendship in particular, which every other person on the team will notice within a fortnight and will interpret as the real decision-making channel.

If someone on the team applied for the job you got, address it directly and early rather than hoping it fades.

How do you handle not knowing the answer?

Say so, then say when you will know.

New managers over-index on appearing certain, usually because they associate authority with having answers. The team reads it accurately as bluffing, and it costs more credibility than the admission would have.

"I don't know" on its own is not enough, though — it leaves the person with the problem and no path. The complete version has three parts: I do not know, here is who I will ask or what I will check, and I will come back to you by Thursday. Then come back on Thursday even if the answer is still no.

There is one thing worth being certain about even when you are not sure: decisions you have made. Explaining a decision tentatively invites re-litigation of it every week. You can hold a decision firmly while being honest that you might be wrong — "this is the call, and if it turns out badly we'll change it" — and that combination is what people actually want from a manager.

What should you measure in the first ninety days?

Whether the team's output depends less on you than it did in month one.

That is deliberately awkward to measure and it is the right thing to look at. Concrete versions: how many decisions came to you that could have been made without you, how many things you personally delivered, whether anyone other than you talked to the stakeholder.

The instinct is to measure activity — meetings held, tickets closed, plans written. All of that can go up while the team gets more dependent on you, which is the failure mode that looks like success for about two quarters.

What is worth doing before you need it?

Practising the conversations you have not had yet.

The first time most new managers deliver bad news, negotiate a deadline with a stakeholder, or tell someone their work is not good enough is live, with a real person, with real consequences. Nobody would run an important client pitch that way, and the management equivalent gets no preparation at all.

Saying the opening out loud once, in advance, is the highest-return five minutes available — why rehearsing a conversation works covers what that actually changes and why thinking it through in your head does not do the same job.