← Back to Insights March 10, 2025

The First 60 Days as a New Manager - What Nobody Tells You

By Priya Nair · 9 min read

You spent three years getting excellent at your job. Now your job has completely changed. The skills that earned you the promotion - technical depth, execution speed, individual contribution quality - are not the skills you need to succeed in the role you just started. No one tells you this clearly enough, and that gap is where most first-time managers struggle.

The first 60 days as a manager are not about proving you can still do the work. They are about establishing the practices and relationships that will determine whether your team trusts you enough to do its best work under your direction. Those are different goals, and chasing the wrong one in the first two months creates problems that take much longer to unwind.

Stop Doing the Work Yourself

The hardest behavioral shift for most new managers - especially those promoted from high-performing individual contributor roles - is stopping doing the hands-on work. When a new manager sees a problem, every instinct tells them to fix it themselves. They know how. It would take them 20 minutes. Waiting for a direct report to solve it will take three days.

That instinct is the enemy of team development. Every time a manager solves a problem that a direct report could have solved (with support), the manager has done two things: they've resolved today's issue, and they've denied the direct report the growth opportunity that comes from working through a hard problem. Done repeatedly, this dynamic creates dependent teams that wait for their manager to do the hard things. That's not a team - it's a manager with helpers.

The discipline required here is significant. When a direct report brings you a problem, the question is almost never "how do I solve this?" It's "how do I help this person build the skill to solve this themselves?" That shift in frame - from fixer to developer - is the core cognitive work of the first 60 days.

Meet Every Direct Report Individually in Week One

Before you set any direction, establish any expectations, or introduce any changes, meet individually with every person who reports to you. These are not 1:1 kickoff meetings. These are listening sessions with one purpose: understanding what each person values, what they're working on, and what they think is getting in the way of the team's best work.

The questions that matter most in these early conversations: What are you most proud of in your work right now? What's the biggest obstacle to your team doing its best work? What do you wish your last manager had done differently? What would make this role the best professional experience you've had?

You are not required to act on every answer. But you are required to remember and reference them. A manager who asks these questions in week one and never mentions them again communicates that the asking was performative. A manager who says "you mentioned in our first conversation that X was a problem - I've been working on that" establishes immediately that listening is followed by action.

Map Your Stakeholder Landscape

New managers typically focus inward - on their direct reports - and miss the horizontal stakeholder relationships that determine how much the team can actually get done. In most organizations, your team's effectiveness is heavily determined by your working relationships with people who do not report to you: product managers, finance partners, legal, other team leads, your own manager.

In the first 30 days, meet with each key cross-functional stakeholder. The goal is not to establish yourself or announce changes. The goal is to understand: What does this person need from my team? Where have the previous handoffs been broken? What would make this partnership work better from their perspective?

These conversations also surface context your direct reports may not have. A cross-functional partner might mention that a longstanding process is inefficient in a way that's invisible from inside your team. Understanding the landscape from the outside helps you prioritize which internal problems are worth solving first.

Decide What Not to Change

New managers often feel pressure to establish their identity by making changes. This is usually counterproductive. Change signals disruption before you've demonstrated the trust that makes disruption acceptable. The team is watching to see whether you understand the work before you start adjusting it.

The more productive discipline is deciding explicitly what not to change in the first 30 days. Pick two or three things the team is doing well and name them publicly. "The way you're handling client onboarding is clean - I'm not touching that." It communicates that you see the work accurately, that you're not changing things for the sake of change, and that good existing practices will be protected.

This restraint also buys credibility for the changes that actually need to happen. When you do change something, the team knows it's because the thing needed changing - not because you're asserting your authority or following a new-manager checklist.

Establish Your Communication Norms Early

The first 60 days is when your communication norms get established, whether intentionally or not. If you respond to Slack messages at 11pm, you've implicitly communicated that 11pm responses are expected. If you cancel three 1:1s in the first month, you've communicated that 1:1s are low-priority. These patterns set in fast and take significantly more effort to change later.

Be deliberate about what you're establishing. Define your expected response times for different message types. Name when you are and are not available. Be consistent about keeping 1:1s. Hold your first team meeting and explain how you will run them. The more explicit you are about your communication norms, the less ambiguity the team has to fill in with assumptions - and the less anxiety generated by working out what "the new manager" is actually like.

The Competence Trap

A specific failure pattern among technically strong first-time managers: they solve problems competently but don't explain their reasoning. The team sees the outcome but not the thinking. When this happens consistently, direct reports stop bringing problems early because they've learned the manager will just solve them. They start filtering what they share and escalating only when things are already bad.

The antidote is narrating your reasoning out loud, especially in the first 60 days. "Here's why I'm making this call: the risk of delaying is higher than the risk of moving forward now, because..." This transparency does something the fast-correct answer does not: it teaches the direct report to make similar decisions independently. After six months of narrated reasoning, your direct reports will be better at the judgment calls that you've been making in front of them.

Your First 90-Day Check-In

At the 60-day mark, do a deliberate self-assessment. Ask your direct reports anonymously: "What's one thing I'm doing that's helping the team? What's one thing I should do differently?" Ask your own manager for honest feedback. Ask the cross-functional stakeholders you've been building relationships with.

The willingness to solicit feedback at 60 days - before the formal review cycle - communicates that you take the manager role seriously enough to actively monitor your own performance. It's also practically useful: the feedback you receive at 60 days is still early enough to change course before patterns calcify.

For a deeper look at the 1:1 practices that make the first-time manager transition smoother, read our guide on how great 1:1s work. The quality of your 1:1s in the first 60 days is the strongest predictor we've found of team trust levels at the 6-month mark.