While I hold a different role now, I do remember being a new manager and making every mistake in the book. What I see today is frustrating: most managers I work with are also repeating those same patterns. Over the next few weeks, I’m writing about what actually changes when you move from individual contributor to manager—how the role changes and why the skills that got you promoted won’t get you there. Hoping that by sharing my experience, I can help some of the new managers move past the first hurdle and grow faster.

This first piece is about the biggest trap: still executing tasks that you’re no longer paid to execute. If you recognize yourself here, keep reading.

---

You got promoted because you were reliable. You shipped things. You solved problems. You were the person who got stuff done. So why does being a manager feel like you’re not doing your job?

Because you’re still measuring yourself by the wrong currency.

The problem (why its tempting to stay in execution)

Here’s what happens to most new managers: You feel most confident when you’re executing. You understand the work. You control the outcome. So you slip back into it. You stay in the details. You redo your juniors’ work because it’s faster. You own the deliverables. You become the bottleneck. I did all of this. And I felt justified doing it.

In my mind, I was pulling my weight. I was ensuring quality. I was being responsible. What I was actually doing was preventing my team from learning and burning myself out in the process. I was redoing their work while they watched and waited—and then I wondered why they weren’t developing as fast as I wanted.

The real problem? I measured my job by the wrong metric. I felt most productive when I was executing. But execution wasn’t my job anymore. It was theirs.

The diagnostic moment (when you realize something is wrong)

The moment of truth came when I went on vacation. Nothing moved. Decisions didn’t get made. Projects stalled. And when I came back, I was exhausted instead of rested—frustrated instead of rejuvenated.

That’s when I realized: I hadn’t created a team. I’d created a dependency. The moment you become the single point of failure, you’ve built something fragile. And you know it, because the anxiety follows you everywhere—even on vacation.

The turning point (what changed)

I made a decision: I was going to stop redoing their work. I was going to let them make mistakes. And I was going to let them learn from the consequences. This sounds simple. It wasn’t.

It required psychological safety—creating an environment where people could admit mistakes without fear. It required patience—watching them struggle with things I could solve in less time. It required trust—believing that the struggle itself was the learning.

A note on hybrid roles: Now, I should be clear—not every manager role is purely leadership-focused. Many managers are expected to code, ship, or execute core work themselves. If that’s your situation, the principle doesn’t change—it just gets more nuanced. The question isn’t whether you execute. It’s: “Am I executing work that my team should be owning, or work that genuinely requires my role and seniority?” And more importantly: “Am I using execution as an escape from the harder leadership work?”

The trap is the same. You still become the bottleneck. You still prevent your team from growing. You still avoid the messy work of management. The solution just requires better boundaries and ruthless prioritization.

What actually changed (the new approach in action)

Instead of telling people what to do, I started asking questions. What happened here? What would you do differently? What did you learn?

The stronger thinkers? They thrived on this. The exposure, the productive struggle—it accelerated their growth. There’s no better way to learn to ride a bike than to do it and fall so many times that you know exactly what not to do.

One of my juniors made a calculation error on a marketing platform and exceeded the budget. Real money. Real consequence. When they came to me, I stayed calm. We figured out how it happened together. We discussed how to fix it. And we talked through how to avoid a repeat. That junior never made that mistake again. Why? Because they felt the weight of the mistake and owned the responsibility for preventing it.

But this doesn’t work for everyone in the same way.

Some juniors need clarity and direction first. They want to be told exactly what to do—and that’s okay. You start there. Then gradually, you shift toward more thinking. Eventually, you push back: “I need you to try first.” If that still doesn’t work, you have an honest conversation about organizational fit. Not everyone is ready for that growth trajectory.

The key is matching the challenge to the person’s capability.

What this actually freed up (your real job becomes visible)

Here’s what surprised me: Once I stopped executing their work, I had bandwidth to see what actually needed doing. The work that requires your experience and judgment:

• Setting direction (where are we going and why?)
• Bringing pieces together (connecting dots across teams and projects)
• Managing stakeholder relationships (navigating different motivations, politics, and constraints)
• Project P&L (understanding the financial reality of what you’re building)
• Vetting junior work (catching gaps, blind spots, and quality issues before they reach stakeholders)
• Developing capabilities (growing your team from where they are to where they need to be)

This is the work that only you can do right now. Not because you’re the smartest person in the room. But because you have the perspective, experience, and organizational credibility to handle complexity that your team can’t yet. This is what you’re actually paid for.

You still execute when needed. During crises. When you need to model how something’s done. When you’re unblocking a critical path. But you execute at a higher level—solving the problems that only your experience can address.

The reality check (Its harder than it sounds)

All of this sounds neat and tidy. It’s not. Of all the high-level work, stakeholder management is the most difficult. And I’ll be honest: It’s still a work in progress.

Here’s why: Execution is predictable. People aren’t.

You can control whether a calculation is correct. You can’t control whether a stakeholder is going to move the goalposts, change their mind, or get political. You can’t control their timeline, their budget constraints, or their organizational pressures.

What you can do is figure out their motivation. And align with it to get to yes. That takes observation. Conversation. Patience. Understanding that their priorities might be completely different from yours—and that’s not wrong, it’s just different.

It’s the skill that separates good managers from great ones. And it’s uncomfortable because you can’t control the outcome.

The reflection (what now?)

Ask yourself:

• What work am I personally doing right now that truly only I can do? (Setting direction? Managing stakeholders? Building team capability?)
• What work am I doing that I’ve become the bottleneck for? (Things my team should be doing? Work that’s keeping me stuck in execution?)
• What would change if I stepped back from the second category? (More time for the first? A team that owns their work? Actual rest when you’re on vacation?)

The guilt you feel about not being in the trenches? That’s the signal you’re actually starting to do your real job.