"Congratulations. You're a manager now."

That's it. That's the whole first-time manager training. A handshake, maybe a new laptop, and a calendar full of 1:1s you have no idea how to run.

The most common story in tech? No training at all. Just a promotion, a new title, and the expectation that the same skills that made you a great engineer will somehow transfer to leading people. They don't. And the data makes that brutal.

‍

Why Most First-Time Manager Training Fails

Gallup has been tracking this for years. Managers account for 70% of the variance in employee engagement. Seventy percent. And yet most companies still promote their best individual contributors and hope the leadership part clicks.

It doesn't click. It crashes.

The reason is what John Maxwell calls the Law of the Lid. Your team's performance cannot exceed your leadership capacity. Put an undertrained manager in charge of a high-potential team and you don't just slow the team down. You create a ceiling they can't break through no matter how talented they are.

What makes it worse: the skills that made someone a great individual contributor often actively work against them as a manager. Engineers solve problems by going deep and doing. Managers solve problems by enabling others to do. That's a completely different job. Promoting someone into a role they haven't been trained for and calling it a "growth opportunity" is how you burn out your best people and lose them within 18 months.

The good news? First-time manager training works when it focuses on the right things. Not generic leadership platitudes. Not "communication is important." Specific, practical, repeatable skills for the transition from IC to leader.

Here's what actually matters.

‍

The 5 Skills Every First-Time Manager Training Must Cover

There's no shortage of management frameworks out there. But if you're building a new manager training program for a tech company, five skills move the needle more than anything else. These are the ones we've seen determine success or failure across hundreds of manager transitions.

‍

1. The Mindset Shift: From Doer to Multiplier

New managers struggle most with letting go. You spent years building expertise by doing things yourself, doing them well, and getting rewarded for it. Now your job is to help other people do things. Even when they'd do it slower or differently than you would.

This is uncomfortable. It feels like losing control. It looks slower. It is, in the short term.

But here's the truth: a manager who does everything themselves is not a manager. They're an individual contributor with a fancy title and a team that can't grow without them. The goal is to become a multiplier: someone who makes the people around them better.

The mindset shift doesn't happen from a workshop. It happens from real coaching, real feedback, and real practice. Give your new managers space to delegate and then debrief what happened. Not to criticize. To learn.

‍

2. Running 1:1s That Actually Build Trust

Most 1:1s are status updates. "What are you working on? Cool. Here's what I'm working on. Same time next week?"

That's not a 1:1. That's a report-out.

A real 1:1 is the most powerful tool a manager has. It's where trust gets built, blockers get cleared, development conversations happen, and your team members feel seen and supported. Done well, a weekly 30-minute 1:1 can prevent more issues than any offsite or team-building exercise.

The framework you use matters less than the habit. Commit to the meeting, show up prepared, and make it about the other person, not the project.

‍

3. Giving Feedback Without the Awkward Silence

Nobody gets hired to be a bad manager. But most new managers avoid feedback because they don't know how to give it without damaging the relationship.

So they say nothing. Problems compound. And when they finally say something, it comes out as either too soft to land or too harsh to recover from.

‍

4. Building Psychological Safety From Day One

Research from Google's Project Aristotle identified psychological safety as the single biggest predictor of team effectiveness. More than talent, resources, or process. Teams where people feel safe to speak up, raise concerns, and admit mistakes outperform teams where they don't. Consistently.

For a first-time manager, this is both great news and a significant responsibility.

Great news because psychological safety is buildable. It's not about personality. It's about behaviour. A manager who asks good questions, responds non-defensively to criticism, and admits when they don't know something creates the conditions for safety. A manager who punishes mistakes, shuts down dissent, and always has to be right destroys it.

The responsibility is that safety starts and stops with the manager. Your team is watching how you react when someone raises a problem. Every reaction (including the micro-expressions) sends a signal. This is why psychological safety training is a core component of manager development, not a bonus add-on.

For practical exercises and team norms, read our guide to building psychological safety in remote engineering teams.

‍

5. Delegation Without Abandonment

There's a difference between delegating and dumping. Dumping is handing someone a task and disappearing. Delegating is handing someone a task with clear context, agreed outcomes, and ongoing support.

The 10-80-10 model is a simple framework that works. Use the first 10% to set up the task clearly: context, constraints, definition of done, and who else is involved. Let the person own the middle 80% without hovering. Use the final 10% to review, give feedback, and close the loop.

Most new managers either micromanage (they own all 100%) or under-manage (they set up the task and vanish). The 10-80-10 model creates a structure that respects the other person's autonomy while keeping the manager appropriately involved.

‍

What a 90-Day First-Time Manager Training Plan Looks Like

A structured training plan beats a one-day workshop every time. Here's a realistic 90-day arc for new managers in a tech environment.

Days 1–30: Listen First, Lead Second

Resist the urge to fix anything. Your job in the first 30 days isn't to make changes. It's to understand why the team is the way it is.

Spend the first month doing what we call a Fresh Eyes Audit. Schedule a 30-minute 1:1 with every direct report. Same questions for each: What's working? What's broken? What would you do if you had my job? Map the team's existing norms, blockers, and unwritten rules. Notice the things that seem off and write them down. Don't act on them yet.

The mistake new managers make in this phase is using their fresh perspective to start changing things on day three. That signals to the team that you've made decisions before you understood the context. You'll burn through trust you haven't even built yet.

The exception: if something is actively on fire — a broken process, a toxic dynamic, a missed deadline that needs an answer this week — you act. Otherwise, you observe.

‍

Days 31–60: Build Systems

Now the listening becomes leading. The systems you put in place during this window become the operating rhythm for everything that comes after.

Establish a weekly 1:1 cadence with each report and stick to it. No cancellations unless there's an emergency. Define team norms in collaboration with the team: how do we run meetings, how do we give feedback, how do we make decisions. Write them down. Start delivering feedback in low-stakes moments using the SBI structure so the muscle is built before you need it for hard conversations. And pick one project where you delegate using 10-80-10. Just one. Get the rep before you scale it.

The mistake here is trying to build every system at once. You'll exhaust yourself and confuse the team. One system at a time, give it two weeks to settle, then layer in the next.

‍

Days 61–90: Evaluate and Adjust

By day 60, you've gathered context and started to lead. Day 61 onward is where you find out what's actually working.

Ask for feedback on yourself. Run a short 360 or anonymous pulse on your management style: what's landing, what isn't. Hold a 90-day team retro: what should we keep doing, stop doing, start doing? Revisit the team norms you set in days 31-60 and refine them based on what's emerged. Have a development conversation with each direct report about where they want to grow next.

The point of this phase is to break the assumption that "I figured it out" after 60 days. The first 90 are the easy part. The hard part is the manager who keeps adjusting at month six, month twelve, year three. The 90-day mark isn't a finish line. It's the moment you stop being a new manager and start being a manager.

The Gallup data on this is stark: managers who receive regular development conversations are 3x more likely to be engaged. That means investing in your managers has an outsized return compared to almost any other people investment.

‍

The Real Cost of Skipping First-Time Manager Training

The "figure it out" approach isn't free. It's just invisible.

An undertrained manager who quietly disengages their team costs you in turnover, missed performance, and the senior talent that eventually leaves because they're not growing. One bad manager can cost a company $126,000 per year in lost productivity and turnover costs. That estimate is conservative.

More important: first-time managers often internalize their early failures. They come to believe they're just "not a leader." That's not true. It's a skill set. It's trainable. But you have to actually train it.

If you're building a people strategy for a scale-up, the manager tier is where it lives or dies. You can have the best talent in the room and still underperform if your managers aren't equipped to lead.

That's why we built the New Manager Training Program specifically for tech companies navigating that growth phase. Not a leadership philosophy. A practical, structured system for turning your best individual contributors into your best managers.

Want the full framework? Download our free New Manager Playbook: the step-by-step guide we give every new manager in our cohort programs. It includes the 30-60-90 day plan, the delegation model, and the team norms we build in week one.

‍

‍

Frequently Asked Questions