Why some First-Time Managers Fail (And How You Can Succeed)
Your browser doesn't support HTML5 audio
How hard can it be to lead a team?
That was the question I asked myself the first time I got promoted. My boss congratulated me, handed me the reins of a small but ambitious team, and said, “You’ll do great.” At that moment, I felt proud, capable, and slightly terrified. The title change seemed simple—just one word added to my email signature. But little did I know, it was the beginning of the steepest learning curve of my career.
What followed were months of missteps, overthinking, and occasional breakthroughs. Leading wasn’t about technical proficiency anymore; it was about people. And people, I quickly realized, don’t come with instruction manuals.
If you’re stepping into management for the first time, you’re not just taking on a new role. You’re stepping into a completely different game. This is my story of learning to lead, and the lessons I wish someone had shared with me.
Lesson 1: The Hero Complex Will Break You
In my first week as a manager, I made it my mission to fix everything. A team member struggled to complete a project? I stepped in. Another couldn’t solve a technical issue? I solved it. It felt good—like I was proving I deserved the promotion.
Then, it happened.
I stayed late every night. I was drained from juggling my own work and everyone else’s. The team had become passive, waiting for me to provide answers. My “helpfulness” had quietly turned into micromanagement, and morale was plummeting.
The turning point came when one of my team members pulled me aside and said, “I want to learn, but I don’t feel like I have space to try.”
That’s when it hit me: My job wasn’t to be the hero. It was to help others become heroes of their own work.
Key Insight:
The best leaders don’t solve every problem—they empower their teams to solve problems themselves. Leadership isn’t about doing; it’s about enabling.
Lesson 2: Feedback Isn’t a Criticism Sandwich
Early on, I followed a common piece of advice: Always sandwich criticism between two compliments. It seemed logical—people would leave the conversation feeling good while still getting the message.
But one day, I gave feedback to a team member about missed deadlines. I wrapped it between praise for their “great effort” and how “they’re so valued on the team.” The result? They walked away feeling confused and unsure what to change.
It turns out that “constructive feedback” wrapped in too much fluff is like giving someone a map without marking the destination. Clarity, not sugar-coating, builds trust.
What worked better was saying something like, “I noticed you missed the last two deadlines. Let’s figure out what’s blocking you and how I can support you in meeting them next time.” The directness was hard at first, but my team appreciated knowing exactly where they stood.
Key Insight:
Feedback isn’t about being nice or harsh—it’s about being clear. When you care about someone’s growth, you owe them the truth, delivered with kindness.
Lesson 3: Listening Is a Superpower
A few months into my role, I started every meeting with an agenda and ended it with action items. Efficient? Sure. Effective? Not always.
One day, I noticed my team seemed disengaged during our one-on-ones. Meetings felt transactional, not relational. Then a colleague asked me, “When’s the last time you listened without thinking of what to say next?”
It was a gut punch. I had been listening to respond, not to understand.
So, I tried a new approach. During one-on-ones, I asked open-ended questions like, “What’s been on your mind?” and “What can I do to help you thrive here?” Then, I let the silence sit. I listened. I didn’t rush to fill the gaps or offer solutions.
The results were profound. I learned about challenges my team was hesitant to share before. Trust deepened, and our conversations became richer.
Key Insight:
Listening is leadership. People don’t just want to be managed—they want to be heard.
Lesson 4: Your Team’s Success Is Your Success
Before becoming a manager, I took pride in my individual achievements—delivering stellar code, solving complex problems, and meeting tight deadlines. But as a manager, those victories no longer mattered.
I learned this the hard way during a quarterly review when my boss asked, “What has your team achieved?” I froze. My individual wins had blinded me to the bigger picture: A manager’s success is measured by the team’s success.
So, I shifted my mindset. I started celebrating my team’s milestones, even if I hadn’t directly contributed. I made space in meetings to highlight their achievements. Over time, the team became more collaborative and motivated, knowing their work was recognized.
Key Insight:
Your job as a manager is to build an environment where your team can excel—and then celebrate their wins like they’re your own.
Conclusion: The Shift from Me to We
Becoming a first-time manager is like learning to drive on a winding road. The rules are unfamiliar, the stakes are higher, and mistakes feel magnified. But the destination—helping others succeed—is worth every wrong turn.
To all the first-time managers out there, remember this: Leadership isn’t about having all the answers. It’s about asking better questions, fostering trust, and creating a space where people can do their best work.
You don’t need to be perfect. You just need to be present, intentional, and willing to grow alongside your team.
So, go ahead. Lead boldly. Listen deeply. And never stop learning.
Want more insights? Subscribe to my newsletter below. I share weekly lessons from my journey at Amazon, designed to help you elevate your career and lead with impact.
Don’t forget to signup for LeaderHub weekly Office Hours if you want to know more about Engineering Leadership at AWS.
You can also book a FREE 30-minute consultation to ask any question you may have about a career at Amazon, Meta, or Google.