Skip to content

The New Manager Checklist: 12 Moves That Separate Strong First-Time Managers From the Rest

Suprabha Sharma
Suprabha Sharma 14 min read
The New Manager Checklist: 12 Moves That Separate Strong First-Time Managers From the Rest

You got promoted. Or you got hired in. Either way, you are now responsible for other people’s output, and the first 90 days will set the tone for the next two years.

Most new manager checklists you find online are vibes lists. Build relationships. Set expectations. Have a growth mindset. Useful in theory, useless on a Tuesday morning when you have a team of six staring at you.

This is the new manager checklist we actually use with first-time managers in coaching. It comes from what we see across 5,000 plus managers in 40 plus organizations: 12 specific moves that separate the first-time managers who get promoted again from the ones who plateau.

The 12 moves are organized into three phases of the first quarter. Each move has a scenario, what to do, and the trap to avoid.

If you want the skills lens on the same job, read the top skills for a new manager. For the timeline lens, see the roadmap to the first 30 days and the 90-day leadership plan for new managers. For the tactical tips lens, see 10 tips and tricks for new managers. This piece is the do list that ties them together.

Phase 1: Week 1 Moves

Phase 1 definition: Your first week as a manager is for listening, mapping, and earning the right to make changes later. You are not here to fix anything yet.

1. Run a structured first 1:1, not a status meeting

Daniel got promoted on a Friday and had his first 1:1s the following Monday. He spent each one explaining his vision for the team. By Wednesday, three reports had texted his old peer asking what was going on.

The first 1:1 is not for you to broadcast. It is for you to learn four things from each report: what they are working on, what is blocking them, what they want from their next 12 months, and what their previous manager did that they want kept or dropped.

Use a fixed set of four to six questions and ask them in the same order with every report. You will see patterns by report number five. The trap: filling silence with your own talking. Sit with the silence. They will say more.

2. Read the team’s rhythm before changing it

Every team has a rhythm: standups on certain days, a Slack channel that is active or dead, a way Friday afternoons get treated. New managers often feel pressure to put a stamp on things, so they restructure rituals in Week 1.

Don’t. Spend Week 1 attending the team’s existing rituals as a participant. Note what works. Note what people seem to dread. Note who talks and who doesn’t. Write it down. You can change anything you want in Week 4. In Week 1, you do not have enough data.

3. Claim a quick win that helps the team, not you

Sarah’s team had been complaining for two months that a quarterly report took six hours to compile because the data lived in three tools. Sarah spent Week 1 building a simple dashboard that pulled all three. Her team noticed. They were asking her opinion on harder things by Week 3.

Pick something small, ideally a recurring annoyance the team has named, and remove it. The point is not heroism. The point is showing the team that your presence makes their week easier, not harder.

4. Name what is not changing

The biggest source of new-manager anxiety on a team is uncertainty about what you will break. Your team has working agreements with the old manager: how time off gets approved, how Slack DMs get treated after 6 PM, what the WFH expectation is.

In your first all-hands or team meeting, explicitly list the things you are keeping. “Standup stays on Tuesday and Thursday at 10. Time-off approvals stay same-day. We keep Friday focus afternoons.” This costs you nothing and buys you a quarter of psychological safety. Cover it in your first team meeting as a new manager.

Phase 2: Weeks 2 to 4 Moves

Phase 2 definition: Once you have read the team, the next three weeks are about starting to operate. This is where the delegation tax hits hardest and where most new managers regress to doing IC work.

5. Pay the delegation tax on purpose

Rachel was a strong senior engineer before she got promoted. In Week 2, she caught herself rewriting a junior’s pull request at 11 PM because it was faster than coaching them through it.

This is the delegation tax. Coaching someone through a task takes 3x longer than doing it yourself, the first time. The managers who come out ahead pay it on purpose. They block 30 minutes to walk the report through the thinking, ship slightly worse output that week, and ship 5x output by month three.

If you find yourself doing IC work after hours to feel productive, that is the signal. Stop. Hand it back. You are paid to develop people, not to ship the cleanest code on the team.

6. Calibrate where to stay close vs. let go

Not every task should be delegated. Some need your hands. The calibration question is: is this a task where the cost of a mistake is high and recoverable, or high and unrecoverable?

Recoverable mistakes (a junior writes a clunky email, a report misses a minor deadline) are coaching moments. Let them happen. Unrecoverable mistakes (a customer-facing announcement, a hiring decision, a major roadmap commitment) are where you stay close.

A useful rule: in Weeks 2 to 4, sit in on one work session per report per week. Watch them work. Don’t intervene. You will see exactly where their judgment is sharp and where it isn’t, which tells you what to coach and what to delegate fully.

7. Deliver your first hard feedback within 30 days

Eleanor avoided giving hard feedback to her most senior report for the first 60 days because the report had been there longer than her. By the time she finally raised the issue (the report was missing deadlines and other team members had noticed), it had calcified into a real problem.

The first-time managers who hold their ground give their first piece of hard feedback in Weeks 3 or 4. It does not have to be major. It can be: “I noticed you cut Maya off in standup three times yesterday. What was going on?” The point is to establish that hard conversations are part of how you operate, before there is a bigger one to have.

The trap: waiting until you have certainty. You will never have full certainty. Lead with observation, ask a question, listen.

8. Establish your escalation pattern with your boss

Your manager is now your most important relationship. They need to know two things from you regularly: what is going well that they can amplify, and what is going wrong that they will hear about from someone else.

In Weeks 2 to 4, set up a weekly written update to your manager: three bullets on wins, three bullets on risks, one ask. Send it before your 1:1, not in it. This does two things. It forces you to think about the team’s state in writing. And it means your manager never gets surprised by a problem you saw coming.

Phase 3: Months 2 to 3 Moves

Phase 3 definition: By month two, the honeymoon is over. The team has stopped extending you grace. This is where you actually take ownership of outcomes, name the people problems you have been watching, and build the relationships that make the next two years possible.

9. Ramp ownership of team outcomes

In Month 1, the team’s results are inherited. By Month 2, they are yours. This is when your manager starts asking direct questions about the team’s numbers, the team’s health, and the team’s roadmap.

The managers who make this shift in Month 2 own a team metric that shows up in a leadership review. They speak first when their team is mentioned in a cross-functional meeting. And they stop saying “the team is figuring out” and start saying “we are doing X by Y.”

The shift is from reporter to operator. If you are still narrating what the team is doing in Month 2, you have not made the move yet.

10. Name who is underperforming and what you are doing about it

By the end of Month 2, you know which one or two reports are underperforming. You have been watching for six weeks. The new managers who struggle most in our coaching data are the ones who let this slide into Month 4 and 5, hoping it self-corrects.

It does not self-correct.

Name the underperformance to the report directly, with specific examples. Document what good looks like and the timeline to get there. Then tell your own manager what you are doing about it. Do not skip that last step. Surprises in Month 6 about a long-standing performance issue are how new managers lose credibility with their boss.

11. Build the manager-skip relationship

Your skip-level (your manager’s manager) is the person who will decide whether you get a bigger team in 18 months. Most new managers wait too long to be on this person’s radar.

In Month 2 or 3, ask your manager for a 20-minute introduction with the skip. Bring two things: a one-page on what your team does, and one specific question about the broader org direction. Don’t pitch yourself. Show curiosity about the level above. The skip will remember.

Patrick did this in Month 3 of his first manager role. By the time a new team needed a lead 14 months later, Patrick was the name his skip remembered, not because he asked for it, but because he had been visible the whole way.

12. Build your own coaching habit before you need it

The new managers who plateau tend to share one trait: they stopped learning around Month 4. They got comfortable, and the next bigger problem (a layoff, a reorg, a senior hire who challenges them) caught them flat.

The ones who avoid that plateau build a coaching habit early. That can be a peer manager group, a real coach, a structured reading habit, or a tool like Risely’s daily nudges. The point is to install something now, before you need it, so that when the next hard thing hits in Month 7 you already have the muscle.

What we see in our coaching data: Across 5,000 plus managers we have coached, those who built a structured coaching habit in their first 90 days improved their target skills by 26 percent on average within 12 weeks, and 73 percent stayed highly engaged with daily nudges past the first month. The managers who waited until they hit a crisis took roughly twice as long to recover their footing.

Wrapping the 12

Read the list back. Notice what is missing: there is no “create a personal vision statement,” no “build your vocabulary,” no “read these five books.” Those are not bad ideas. They are just not what separates strong first-time managers from average ones in the first 90 days.

What separates them is the boring stuff. Listening before changing. Paying the delegation tax. Giving the first hard feedback before Month 2. Naming the underperformer. Showing up for the skip. Installing a habit before you need it.

If you do these 12 things in your first quarter, you will be in the top quartile of new managers your organization has ever had. Not because the moves are clever. Because almost no one does them.

Try Merlin for your first 90 days

Risely’s AI coach Merlin is built for exactly this window. Merlin runs structured 1:1 prep, role-plays your first hard feedback conversation before you have it, drills delegation calibration with real scenarios from your week, and sends daily nudges tied to whichever of these 12 moves you are working on.

Strong first-time managers do not figure all 12 out alone. Try Merlin free and spend 15 minutes on the move you are about to ship this week.

If you want a more guided onboarding, Risely’s new manager program wraps Merlin in a structured 90-day track with assessments and growth tracking.

FAQ

What should be at the top of a new manager checklist?

The first item is a structured first 1:1 with each direct report focused on listening, not announcing changes. Strong first-time managers spend Week 1 reading the team’s existing rhythm before touching it.

How long should a new manager checklist cover?

A useful new manager checklist covers the first 90 days, broken into Week 1 (read the team), Weeks 2 to 4 (start operating), and Months 2 to 3 (own outcomes). Anything shorter misses the calibration phase. Anything longer turns into a generic leadership reading list.

What is the biggest mistake new managers make in the first 30 days?

Changing things before they understand them. The new managers who struggle most in our coaching data tend to announce process changes, restructure 1:1 cadences, or rewrite goals in Week 1. The ones who do well watch for two to three weeks first.

How do I know if I am underperforming as a new manager?

Three signals: your 1:1s feel like status updates, you are still doing IC work to feel productive, and you have not given hard feedback to anyone. Any one of those after 60 days means it is time to recalibrate.

How is this different from a generic 30-60-90 plan?

Generic 30-60-90 plans tell you to “build relationships” and “understand goals.” This new manager checklist names 12 specific moves with scenarios, so you know what to actually do on Tuesday morning. It is the do list, not the be list. Pair it with the skills view and the 90-day plan for the full picture.

Talk to Merlin

Get personalized coaching on the skills covered in this article — powered by AI that understands your context.

Try Merlin Free
Suprabha Sharma

Written by

Suprabha Sharma

MA Clinical Psychology, The IIS University. BA Applied Psychology, Amity University.

Suprabha trained as a clinical psychologist at The IIS University, which means she spent years studying why people do what they do before she started writing about it. At Risely, she turned that lens on the workplace, covering the behavioral patterns behind team dynamics, conflict, motivation, and the dozens of small interactions that make or break a manager's day.

Take Assessment Try Merlin Free