The week I got promoted, I read a book on direct, unfiltered feedback and decided, correctly, that I'd been too hands off. So I started giving it constantly, exactly in the blunt style the book described. Within a month, two people on my team had stopped bringing me problems early. Early problems were where the bluntness landed hardest, so they waited until issues were bigger and harder to walk back before mentioning them at all.
The book wasn't wrong. I just never checked whether my team had the footing to receive that style yet. Nobody had ever given them direct feedback before. They needed a runway into it, not the full weight of it on day one.
If that feels a little too familiar, you're not doing this wrong. You're doing something almost every new manager does. Nobody hands you a manual when you get promoted. What you usually get instead is a title, a headcount, and the silent expectation that you'll figure the rest out. So you reach for something that already worked somewhere else. A book. A course. The style of a manager you respected. And you apply it, mostly whole, to a team and a context it was never written for.
That's one of the most common first time manager mistakes, and it rarely comes from neglect. It comes from applying someone else's answer to a question that was actually about you and your specific team.
Good at the Work Isn't the Same as Good at Leading It
The most common path here starts before the promotion even happens. You got the role because you were excellent at the individual work, not because anyone tested whether you could lead. So the actual mechanics of managing, having a hard conversation, making an unpopular call, coaching someone through a slump, get treated as an afterthought. You default to what you already know how to do, which is the work itself, and leadership becomes something that happens to you instead of something you actively do.
The Trap of a Single Framework
The second trap is subtler, and it usually comes from good intentions. You read one book, take one course, or watch one leadership style up close, and you adopt it wholesale. Not adapted, not tested, just applied. It becomes the answer to every situation instead of one input among several.
The problem isn't the framework itself. Most of them hold real insight. The problem is treating a method built for a different team, a different industry, a different personality, as a plug and play solution for yours. A framework that tells you to step back and trust your team works differently on a team that's never been given clear standards than it does on one that has. Applied without that context, "trust your team" quietly becomes "leave your team alone."
"Leave your team alone" has a name worth knowing: abdication. It's not laziness, and it rarely feels like giving up. It's still showing up, still holding the title, but quietly stepping back from the parts of the job that are uncomfortable, the hard conversation, the unpopular call, the coaching that takes real time, and calling that distance trust instead of naming it for what it is. That's exactly the gap I fell into. The book told me to be direct. It never told me to check whether my team had the footing to receive it yet.
Two Things That Can Look Identical
From the inside, empowerment and abdication can feel like the exact same decision. It helps to put them side by side, because now that you know what each one actually is, the difference isn't the intention behind them, it's what happens next.
| Empowerment | Abdication |
|---|---|
| Sounds like "come to me if it's genuinely above your judgment." | Sounds like "figure it out, I trust you," said to someone who was never told what good looks like in the first place. |
| A bad outcome gets reviewed together, and the lesson gets carried forward. | A bad outcome gets discovered later, after it's already cost something, and nobody agreed on what should have happened instead. |
| Runs on a standard that applies to everyone on the team. | Runs on a favorite, the one person who always seems to know what the manager actually wants, and who everyone else quietly routes through. |
If you recognized your own team more in the right column than the left, that's not a character flaw. It's usually just a leadership style applied without a floor underneath it.
Empowerment Has a Floor
Real empowerment gives people room to operate and still leaves something under them. They know what good looks like. They know who to go to when a call is genuinely above their judgment. They know someone will back them if they make a reasonable decision and it doesn't work out. A borrowed framework, applied without adjusting for your actual team, tends to remove that floor while still calling itself empowerment. I didn't mean to remove mine. I just didn't notice it was gone until my team started managing me instead, filtering what they told me so the bluntness had less to land on.
Closing Thoughts
The book, the course, the manager you admired, none of them are the problem. The problem is skipping the step where you ask whether their answer fits your team, your context, your moment. Leadership methods are a starting point, not a script. The managers who figure this out early are the ones who stop asking what the framework says and start asking what this team actually needs from them right now.