You got promoted because you were great at your job. Now your job is to make other people great at theirs. Nobody taught you how to do that.

That's not a complaint. That's the story of almost every manager in tech. The transition from individual contributor to manager is one of the hardest role changes in a career, and most companies hand you a new title, a slightly larger Slack status, and exactly zero guidance on how to lead.

Research from the UK's Chartered Management Institute puts a number on it: 82% of managers step into the role without any formal management or leadership training. They call them "accidental managers." That study was UK-based, but anyone who's worked in tech knows the pattern travels. The cost shows up everywhere, in disengagement, in turnover, in teams that quietly stop speaking up. This is the gap that formal new manager training is designed to close, but the first 90 days are on you.

‍

Why the First 90 Days Make or Break You as a Manager

Michael Watkins, who wrote the book on leadership transitions, found that a new leader's success or failure is usually decided in the first three months. And the mistakes that derail new managers are almost never technical. They're human.

They show up in a predictable handful of ways. Trying to fix everything before you understand anything. Avoiding the hard conversation. Saying yes to keep the peace. Mistaking the skills that made you a great individual contributor for the skills the new job actually needs.

The first 90 days aren't about proving yourself through what you do. They're about proving yourself through how you lead.

‍

Phase 1: Listen Before You Lead (Days 1 to 30)

The single most important thing a new manager can do in the first month is resist the urge to fix things.

You were promoted because you could see problems and solve them fast. That's still your job, but the how has changed completely. Jumping in with answers before you understand the team's context is how you lose credibility within weeks.

Instead, spend the first 30 days obsessively listening.

Listening with intent has a shape. Book a 30-minute one-on-one with every direct report in the first two weeks, and ask each of them the same three questions: what's working, what's getting in your way, and what you'd want from me as your manager. Talk to your peers and your own manager about how your team's work connects to theirs. Watch how the team already operates before you change any of it, which meetings matter, how decisions actually get made, who people go to when they're stuck. And write down every problem you notice. Just don't fix any of them yet.

These conversations will surface the real team dynamics faster than any onboarding doc. You'll learn who the informal leaders are, where the communication breakdowns live, and what people have been afraid to say out loud.

You'll also do something more important: you'll signal that you're here to lead with them, not at them. That's the foundation of psychological safety, the belief that it's safe to speak up, take risks, and be honest. You build it in the first month by listening and then acting on what you hear.

By the end of Day 30, you should be able to answer a few questions without guessing. Who the real influencers on the team are, the people others follow regardless of title. Where the friction lives, and whether it's about process, priorities, or people. What the team is proud of, and what they've quietly given up on. If you can't answer those yet, you've been talking more than listening. Go back.

‍

Phase 2: Build Rhythm, Earn Trust (Days 31 to 60)

Month two is where you stop observing and start operating. Carefully.

You now have enough context to identify the quick wins: small improvements that don't require big changes, don't threaten anyone's identity, and show the team you're actually listening. Fix the meeting that always runs over. Unblock the process everyone complained about. Have the one awkward conversation that's been avoided for months.

Quick wins matter not because they're strategically important, but because they build trust. Teams form opinions about new managers fast. If someone can say "the new manager already fixed X" in month two, you've created an early advocate.

The most valuable thing you can do in month two is set a consistent operating rhythm. That's the set of recurring meetings your team can count on: weekly one-on-ones with every direct report, thirty minutes each, their agenda before yours. A weekly team meeting built around coordination and blockers, not status theatre. And a regular way for the team to see what's coming, whether that's a monthly review or a shared doc you keep current.

The rhythm matters more than the format. A new manager who shows up consistently, runs organized meetings, and follows through on what they said they'd do earns enormous credibility. Consistency is trust in operational form.

Give feedback early, even when it's uncomfortable. New managers often wait for the annual review to address performance issues because they're afraid of damaging the relationship. This is the mistake that turns small problems into unfixable ones.

Use the SBI model: Situation, Behaviour, Impact. Keep it concrete:

"In yesterday's sprint planning (Situation), when you interrupted the engineer twice before she finished her thought (Behaviour), I noticed two other people stopped contributing for the rest of the meeting (Impact). Can we talk about how to run that differently?"

This isn't harsh. It's respectful. The alternative, saying nothing and letting resentment build, is what actually damages relationships. Understanding different communication styles through a tool like DISC helps you tailor how you deliver feedback to the person in front of you.

‍

Phase 3: Set Direction, Define Success (Days 61 to 90)

By day 60, you know the team. You've built some trust. Now it's time to step into the actual job of a manager: defining where you're going.

Month three is where you move from reactive to intentional.

Build a simple 90-day team plan. One page, no more. It names the two or three priorities the team will focus on next, says what success looks like for each one in plain language, and makes clear who owns what. Don't over-engineer it. A one-page plan your team helped shape is worth more than a beautiful spreadsheet nobody reads. The act of building it together, asking the team to help define what success means, creates ownership and alignment at the same time.

Then prepare a debrief for your own manager. On or around Day 90, sit down with them and walk through four things: what you've learned about the team, what you've changed and why, what you're going to focus on next quarter, and where you need their support to pull it off. Keep it to a single page or a short conversation. The point isn't to perform. It's to get aligned before small gaps become real ones.

This conversation shows you're thinking like a leader, not just a doer.

‍

A Tale of Two New Managers

In our work with tech teams, we've seen two kinds of new manager emerge at the 90-day mark.

The difference wasn't talent or intelligence. It was the sequence.

‍

The Traps That Catch Every New Manager

No 90-day plan survives first contact with a difficult team dynamic. Four traps catch almost everyone.

The first 90 days will be uncomfortable. That discomfort is the job. Lean into it.

Want a structured guide for your first 90 days, with 1:1 templates, feedback scripts, and team meeting agendas? Download the free New Manager Playbook. Built for first-time managers in tech.

‍

Frequently Asked Questions: