"You're a Manager Now" and Other Lies Your Boss Told You
Congratulations. You’re a manager now.
Here’s your new title, a calendar invite for a leadership meeting, and absolutely no guidance on how to do this job. Oh, and you start Monday. Good luck.
That was essentially how it went for me. One day I was an engineer shipping code, feeling useful, getting that dopamine hit every time tests passed. The next day I had “Manager” in my title and a vague expectation that I would now magically know how to lead humans. As if the title itself would trigger some latent superpower that had been dormant inside me, waiting for the right LinkedIn update to unleash it.
Spoiler: it did not.
The Title Is Not a Magic Wand
Here’s the lie nobody tells you upfront: the title doesn’t come with authority. It comes with a Slack channel, some new recurring meetings, and a front-row seat to everyone else’s problems. But respect? Trust? The ability to actually influence anything? You’ll need to earn those the hard way.
I remember my first week as a manager, walking into a team standup like I owned the place. I was the boss now, right? I had opinions. I had ideas. I was ready to lead.
My team looked at me like I was a substitute teacher.
And honestly? They were right to. What had I done to earn their trust as a leader? Nothing. I’d written good code. I’d been reliable. I’d shipped features. But none of that qualified me to suddenly have opinions about their careers, their conflicts, or their workloads. I was running on borrowed credibility, and that loan comes due faster than you think.
The myth of instant authority is seductive because it feels like it should be true. You got the promotion. You beat out other candidates. Someone important decided you were ready. Surely that means something?
It means someone took a bet on you. That’s it. Now you have to prove they weren’t an idiot for doing so.
You Just Lost the Thing You Were Good At
Let’s talk about the part that really stings.
You were good at your old job. That’s why they promoted you. You could solve hard problems. You knew the codebase. You were the person people came to when something was broken. You had value that was obvious and measurable.
Now? Now you’re supposed to stop doing that thing.
Wait, what?
Yeah. That thing that made you successful, that gave you identity, that made you feel competent and useful? Put it down. You don’t get to do that anymore. Or at least, you shouldn’t. Because if you’re still writing code all day, you’re not doing your actual job.
This is the grief nobody warns you about. You will mourn your old role. You will miss the clarity of a well-defined task. You will long for the days when “done” meant something you could point to. See that feature? I built that. That’s mine.
As a manager, your output is invisible. It’s in the meetings you had that prevented a crisis. It’s in the conversation you facilitated that helped two engineers stop hating each other. It’s in the roadmap prioritization that nobody noticed because it just... worked. You will do good work and feel like you accomplished nothing.
For a while, you might try to cling to the old identity. You’ll tell yourself you’re a “technical manager” or a “player-coach.” You’ll sneak in code reviews at 10 PM. You’ll take on that one small feature because “it’ll be faster if I just do it.”
This is a trap.
The more you hold onto the old job, the worse you’ll be at the new one. And worse, you’ll be silently telling your team that you don’t trust them to do the work. That their code isn’t good enough. That you need to be there to save them.
Let go of the keyboard. It’s going to hurt. Do it anyway.
Your Team Is Not an Array of Resources
Here’s something that tripped me up hard in my first year: I kept thinking about my team like a system.
Which makes sense, right? I’m an engineer. Engineers think in systems, abstractions, and patterns. So when I looked at my team, I saw capacity. I saw skill matrices. I saw a collection of resources that could be allocated to problems.
Turns out, people really don’t like being treated as interchangeable units in a resource allocation spreadsheet. Who knew?
Actually, everybody knew. I was just too deep in my own abstraction to notice.
People are not predictable. They have context you don’t have access to. They have bad days, personal crises, hidden anxieties, and past experiences that shape how they react to every damn thing you say. They have preferences and pet peeves and things that motivate them that are completely unique.
When you treat people like resources, you miss all of this. And then you’re blindsided when someone quits and you “had no idea they were unhappy.” Or when your perfectly logical argument fails to convince anyone. Or when a decision that seemed obvious to you lands like a bomb in the team.
The job isn’t optimizing a system. It’s building relationships, one awkward coffee chat at a time.
What I Wish Someone Had Told Me
If I could go back and talk to myself on Day One of this job, here’s what I’d say:
You’re going to feel like a fraud. That’s normal. You are, technically, a fraud. You’ve never done this job before. You’re figuring it out as you go. That doesn’t make you bad at it. It makes you new at it. There’s a difference, even though it won’t feel like one.
The skills that got you here won’t save you. Your technical ability, your problem-solving brain, your attention to detail? All useful. But not sufficient. You need new skills now. Listening. Facilitating. Giving difficult feedback. Having patience when you want to scream. These are learnable, but you’re starting from scratch again. Welcome back to being a junior.
It’s okay to be bad at this. In fact, you will be bad at this. For a while. Maybe a long while. That’s the deal. You can be bad at it and still keep trying. You can fail a conversation and try again tomorrow. The only unforgivable sin is pretending you have it all figured out when you obviously don’t.
The Actual Job (Since Nobody Explained It)
So what are you actually supposed to do all day?
Not code. We covered that.
Not be the smartest person in the room. That’s not your role anymore, and honestly, it’s a relief once you accept it.
The actual job is less glamorous than the title suggests. It’s:
Clearing blockers. Half of management is just asking “what’s in your way?” and then going to fight whoever put that thing there. You become a professional obstacle remover. Sometimes the obstacle is a process. Sometimes it’s another team. Sometimes it’s an executive who doesn’t understand what you do. Sometimes it’s you.
Having uncomfortable conversations. Feedback, performance issues, team conflicts, salary discussions, career disappointments. All the conversations nobody wants to have? Those are yours now. Congratulations.
Making boring decisions. Should we use this tool or that tool? Who gets assigned to this project? What’s the priority order? These are not exciting decisions. But someone has to make them, and if you don’t, nobody will, and everything will grind to a halt.
Representing your team. Upward, outward, everywhere. You are now the translator between your team and the rest of the org. You shield them from bullshit. You advocate for their needs. You explain what they’re doing in terms executives can understand. You are the buffer.
Your output is now your team’s output. This is the hardest mindset shift. You don’t produce work anymore. You enable work. Your success is entirely measured by what your team ships. If they’re winning, you’re winning. If they’re struggling, that’s on you to figure out why.
It’s weird. It’s uncomfortable. And it takes a long time to stop feeling like you’re doing nothing even when you’re doing everything right.
Why You Might Survive Anyway
I know this all sounds grim. And honestly, the first year of management often is. But here’s the thing: you might actually be okay at this.
Not because you’re naturally gifted. Not because you have some special leadership gene. But because you’re willing to be honest about what you don’t know.
Self-awareness beats confidence every time.
The worst managers I’ve worked with were the ones who thought they had it figured out. They’d read one book, attended one workshop, and now they were experts. They gave feedback without listening. They made decisions without context. They confused certainty with competence.
The best managers? They ask questions. They admit when they’re wrong. They say “I don’t know, let me find out.” They treat every interaction as a chance to learn something about their team.
Asking for help isn’t weakness. It’s the job. You can’t know everything. You’re not supposed to. Your strength is in building a team that collectively knows more than you ever could, and then getting out of their way.
Find a mentor. Find a peer group. Find someone you can text at 9 PM when you’re spiralling about a hard conversation you have to have tomorrow. This job is too lonely to do alone, and anyone who tells you otherwise is either lying or burning out.
Permission to Struggle
Look. I’m not going to wrap this up with some inspirational bullshit about how you were born for this and everything’s going to be fine.
Maybe you’ll be great at management. Maybe you’ll hate it and go back to engineering. Maybe you’ll be mediocre for three years and then something will click. All of those are valid outcomes.
What I can tell you is this: you have permission to be bad at this right now.
You have permission to feel like you’re failing. To have hard days. To make mistakes. To give feedback that lands poorly and have to clean it up. To feel like an imposter in every meeting you walk into.
That’s not evidence that you’re in the wrong job. That’s evidence that you’re in a new job, and you’re still learning.
The title is a lie. The authority is a myth. The confidence is a performance. But the work? The work is real. And if you keep showing up, keep listening, keep trying to be a little better than you were yesterday?
You might just figure this out.
Or at least, you’ll fail in more interesting ways.