The moment you step into a leadership role, your job fundamentally changes—but most people don't realize it until they've already failed. You can't keep doing the work you were good at. You can't control every decision. And you definitely can't be the person who knows the most about every project. The transition isn't about getting smarter; it's about getting a completely different identity. Find a mentor at your new level, stop trying to do everything yourself, and accept that you don't need to understand every technical detail anymore.
The Identity Shift: You're Not an Executor Anymore
When you were an individual contributor or a middle manager, your value came from execution. You shipped things. You solved problems. People respected you because you delivered.
The moment you move up, that stops being true.
I've watched dozens of founders and executives trap themselves here. They get promoted to VP or become a founder, and they spend the first 6–12 months trying to be the smartest person in the room. They review every code commit. They rewrite emails. They jump into meetings to "make sure things are done right."
Then they burn out or their teams resent them.
Your new job is to:
- Make decisions about direction, not execute the direction
- Hire and develop people better than you at what you used to do
- Remove blockers so others can move fast
- Build systems that work without you in the middle
This feels like a demotion to people who got their identity from hands-on work. It isn't. It's harder. But you have to genuinely believe it before your behavior changes.
One way to cement this: stop having all the context. Delegate a project completely. Don't ask for updates. Ask for outcomes. The discomfort you feel is the old identity dying. That's the point.
The Delegation Trap: Responsibility Without Control
Every leader I know who struggles with delegation makes the same mistake. They delegate the task but keep the decision-making. They empower people to "move forward"—as long as it's the way they would have done it.
That's not delegation. That's remote control.
Real delegation means:
- You own the outcome, not the process. Your person owns how they get there.
- You set the boundary, then get out of the way. "This needs to land by Friday, budget is $50K, and we need three vendor options." Done. Don't ask about the spreadsheet structure.
- You accept that 80% their way is better than 100% your way. Different doesn't mean worse.
- You only step in if they're heading toward a failure you can't recover from. Not if they're doing it differently than you would.
When you first delegate like this, two things happen:
- You feel anxious because you're not controlling the process
- Your team feels trusted for the first time and delivers faster
The anxiety is withdrawal from control. Sit with it. It passes.
Practical test: Next time someone on your team says "I have an idea that's different from what you suggested," your first response should be "Tell me more" instead of "Here's why that won't work." This single behavioral change will unlock faster decision-making and better results.
Finding Your Mentor at the New Level—Non-Negotiable
This is the part most people skip, and it's why they struggle.
You cannot level up without someone who's already operating at the level above you. Not your peer. Not your therapist. Someone who's been a founder when you're becoming a founder. Someone who's managed 100+ people when you're learning to manage 20.
Your old mentors were great for getting you here. But they optimized for a different game.
I've worked with founders who spent two years solving problems that would have taken two weeks of conversation with someone six months ahead of them. The mentor doesn't need to be famous or even well-known. They just need to have been where you're going and still be available.
I've written in more depth about building this kind of relationship when the person you need is several levels above you, in mentoring practices for middle managers.
Where to find them:
- Your industry's angel investors or early-stage VCs. They've seen 50 companies go through exactly what you're going through.
- Peers who made the leap 2–3 years before you. They remember the traps clearly.
- Paid advisory boards or coaching. Sometimes the best mentors are the ones who've committed to helping you for a fee.
- Communities and masterminds for your specific level. General founder networks are noise. Find groups where everyone's at your stage.
Once you find them, be specific about what you need. "Help me figure out how to build a leadership team" beats "advise me on growing the company."
Most people won't turn down a direct, specific ask from someone they respect.
The Technical Knowledge Trap: Stop Trying to Know Everything
If you were an engineer, you'll want to stay current with the tech stack. If you were a salesman, you'll want to close deals yourself. This is a slow poison.
Your new job is to understand enough to make good decisions. Not to be the expert.
This shows up as:
- Sitting in engineering standups when you should be in board meetings
- Personally managing your biggest client when you should be building the account structure
- Reviewing every proposal when you should be coaching your team on judgment
You stay on top of your domain by:
- Learning from your team's updates, not by doing the work
- Reading broadly about where the industry is going (not diving into implementation details)
- Asking good questions instead of checking the work
- Staying hands-on for decisions, not execution. You should understand the tradeoff between moving fast and quality, not write the code.
One practical rule: If you're doing any task someone else on your team could do in the next 6 months, you're in the wrong seat. Train them. Move on.
Personal brand also shifts here. You stop being known as "the person who builds amazing X." You start being known as "the person who finds and develops people who build amazing X." That's a harder identity to own, but it scales indefinitely.
The Speed of Decision-Making vs. Buy-In
As an individual contributor, you could make decisions fast because you had all the context and only had to execute them yourself. As a leader, decisions are slower because you need buy-in from people who have to live with the consequences.
Most new leaders respond by making faster unilateral decisions. Their teams resent it. Execution slows. They think they need to be "more decisive." Actually, they need to be more collaborative before the decision.
How this works:
- Gather input from the people closest to the problem before you decide
- Explain your thinking explicitly when you make the call
- Be open to pushback, especially from people who'll execute it
- Decide and commit. Debate is over; now everyone rows the same direction
This takes longer than you dictating from above. But execution is faster because people actually understand why and believe in the direction.
New leaders often skip steps 1–3 because they can, and step 4 because they doubt themselves. That's the worst combination.
Consider working with a corporate trainer or coach who specializes in leadership transitions. It's the fastest way to see your blind spots.
What Success Looks Like: The Concrete Checklist
You'll know you've made the transition when:
- You have a mentor. Not "thinking about getting one." Actually talking to someone monthly who's done this before.
- You delegate 80% of your to-do list. You spend your time on direction, people, and strategy. Not tasks.
- Your team moves faster without you in meetings. They should be making decisions in your absence.
- You can't do your team's job anymore. By choice. You've delegated technical work completely.
- You're uncomfortable half the time. Growth always feels like you're in over your head. If it feels fine, you're not pushing the boundary.
- People listen to you less because you talk less. Silence and presence matter more than being the smartest voice.
- Outcomes improve when you step back. The real test: Does removing yourself from the execution make things worse or better? If it's the latter, you've crossed the threshold.
If you're at 4+ of these, you've made the shift. If you're at 1–2, you're still clinging to your old identity. That's okay. It's just time to let go.
FAQ
What if I can't find a mentor at my new level?
Then you're not looking wide enough or not offering enough value. Mentors invest in people who are serious. Be explicit about what you need, show you're willing to implement, and be respectful of their time. If it's truly impossible (you live in a small market, no one in your network), consider paying for a coach or joining a peer mastermind where you get mentorship from multiple people at your level. It's worth the investment.
How do I know if I'm delegating too much?
You're delegating too much if decisions are falling through cracks and outcomes are slipping. You're delegating the right amount if outcomes improve and you're spending your time on things that actually require your level. The difference is: bad delegation leaves work undone. Good delegation with poor judgment from your team shows up as mediocre outcomes. Fix the judgment, not the delegation.
Isn't it irresponsible to not know every detail about what my team does?
It's actually irresponsible to try to know every detail yourself. If your team is constantly explaining everything to you, they're being pulled away from their work. Your job is to build systems where you can see the critical metrics without being in the weeds. Dashboard, monthly reviews from managers, quarterly strategy meetings—that's how you stay informed without micromanaging.
How long does the identity shift usually take?
Three to six months if you're intentional about it. A year or two if you're figuring it out by accident. Most people aren't intentional—they just keep doing the old thing until something breaks. If you're working with a mentor or coach, you can compress it to 2–3 months. The identity shift is the hard part, not the skills.
What's the biggest mistake new leaders make in the first 90 days?
They try to prove they're still competent at their old job. They want to show they can still code, still close deals, still know the details. This signals to the team that the old role is still what matters, so everyone stays focused on execution instead of building systems. The first 90 days are about signaling what the new role is, not proving you haven't forgotten the old one. Do one thing your team can't do: set direction, hire better people, or remove a big blocker. Do it visibly. Everything else gets delegated.
Do I need to read books or take courses to make this transition?
No. You need a mentor, clear examples of what the new role looks like, and willingness to feel uncomfortable. Books help, but they won't get you there. The real learning happens through doing and feedback from someone who's already made the climb. If books worked, everyone who read about leadership would be a great leader. They're not. Work with someone. See your blind spots. Change behavior. That's the path.
