Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / The Manager Identity Crisis
Transcript
- Lucas: There is a specific kind of panic that sets in about six weeks after you accept a management promotion. You are no longer the person who fixes the code or closes the deal, but you haven't yet figured out what you are actually responsible for producing. Luna: It is that sudden vacuum where your daily validation disappears because you can no longer point to a completed task on your own name. Lucas: Exactly. And the worst part is that the very behaviors that made you eligible for the promotion—your individual excellence, your deep technical knowledge—are now viewed as micromanagement or even insecurity by your team. I have been thinking about this through the lens of a recent case involving a senior software engineer named David who moved into a director role at a mid-sized fintech company. Luna: David sounds like someone who used to stay up late debugging his colleagues' code before he realized he was holding them back. Lucas: He absolutely did. For the first month, David treated his new role as an extended individual contributor position. He would sit in on design reviews not to facilitate, but to correct architecture choices in real time. He was technically right, but his team started going silent in meetings because they knew he would just override them anyway. Luna: So he was solving problems instead of teaching people how to solve them, which creates a dependency trap. Lucas: Right. And the metric he cared about—shipping features—started to lag because everyone was waiting for his approval. The irony is that by trying to be the hero, he became the bottleneck. His direct reports were disengaged, and the quality of their proposals dropped because they stopped bringing him half-formed ideas and only brought him finished ones that he would then tweak. Luna: That is a classic identity crisis. You are trying to prove you are still valuable by doing the old job better than anyone else, but the new job requires you to make yourself obsolete. Lucas: Precisely. The shift from being a player to being a coach is psychologically jarring because your ego is wired for execution. When you stop executing, you feel like you are slipping. But if you keep playing, the team loses its autonomy. Luna: It feels like you have to voluntarily step down from your pedestal to let others climb it, which is terrifying when you have spent years building that pedestal. Lucas: It is terrifying. And most managers don't realize they are stuck in this phase until their quarterly review shows that their team's output has plateaued despite their increased hours. The solution isn't just delegation; it is redefining your success metrics entirely. Luna: Instead of measuring what you ship, you measure how many people can ship without you. Lucas: Yes. We call this the force multiplier effect. A good manager doesn't add one unit of output; they enable five units of output across the team. But to do that, you have to tolerate mistakes that you could avoid if you just did it yourself. Luna: Tolerating mistakes means accepting that the first version might be imperfect, whereas as an individual contributor, you had the luxury of perfectionism. Lucas: Perfect. And here is the hard truth: your first six months will feel less productive than your last six months as an individual contributor. That is the price of admission for leadership. Luna: If the listener is currently in that six-month window, they need to hear that feeling useless is actually a sign that they are doing the job correctly. Lucas: I want to pause here for a moment. If these conversations about navigating career transitions and management pitfalls have helped you clarify your next move, please consider supporting the show directly. Your support allows us to keep these episodes ad-free and continue digging into the details that matter most to your professional growth. You can find us at buy me a coffee dot com slash fexingo. It really helps sustain the research behind these discussions. Luna: We appreciate every bit of help that lets us keep this resource independent and focused on the long-term career strategy listeners deserve. Lucas: Back to David. After that first month of silence, his VP sat him down and asked a simple question: who is making decisions today that used to require my input? Luna: That is a brutal question because it forces you to look at your calendar and see how much time you are spending acting as a gatekeeper. Lucas: It was. David looked at his week and realized he had approved forty-two small technical decisions. Forty-two things that should have been handled by two junior engineers with a clear playbook. Luna: So the fix wasn't to work harder, but to document the rules so the junior engineers didn't need him. Lucas: Exactly. He spent the next three weeks writing decision logs and escalation paths. He forced himself to stay out of the room during the initial design phases, observing only. It was painful because he saw bad ideas forming, but he held his tongue. Luna: Holding your tongue when you see a mistake is the hardest skill for any new manager to learn. Lucas: It is. Most people intervene immediately to save face. But David learned that if he intervened too early, he robbed his team of the learning opportunity. He started asking questions instead of giving answers. How did you arrive at that conclusion? What happens if this assumption is wrong? Luna: Shifting from provider of solutions to facilitator of thought processes. That changes the entire dynamic of the meeting. Lucas: It does. And slowly, the team started bringing him earlier drafts. Not because he demanded them, but because they realized he was interested in their reasoning, not just their results. Luna: That trust rebuilds quickly once they see you are not there to police them, but to expand their capability. Lucas: By month four, David was spending half his time on cross-functional alignment, connecting his engineering team with product and sales. This is another huge shift. Individual contributors rarely think about how their work fits into the broader revenue engine. Luna: So the manager becomes the translator between the technical reality and the business goal. Lucas: Right. And that translation work is invisible to outsiders but vital for the team's morale. When engineers understand why their feature matters to the customer, they write better code. It gives their work meaning beyond just ticket closure. Luna: Meaning is a powerful motivator. You cannot code your way to motivation, but you can context-code your way there. Lucas: I love that phrase. Context coding. Because without context, you are just moving pixels or text. With context, you are solving a human problem. Luna: Which brings us back to the identity crisis. If you define yourself by the code you write, you lose yourself when you stop writing code. If you define yourself by the problems you solve through others, you gain power. Lucas: Power through leverage. That is the key word. Your leverage comes from your team's collective intelligence, amplified by your strategic direction. Luna: But that leverage only works if you trust them enough to let them stumble occasionally. Lucas: Always. And you have to communicate that trust explicitly. You have to tell them, I am stepping back so you can step up. If you don't say it, they will assume you are hiding incompetence. Luna: Assuming incompetence is the default setting for many teams when a new manager suddenly stops fixing their tickets. Lucas: Spot on. So the narrative you build in those first ninety days is critical. Are you the super-player who finally has authority, or are you the enabler who clears the path? Luna: It is a choice you make every single day in every single interaction. Do I jump in, or do I ask the question? Lucas: Every day. And the answer usually depends on whether you are protecting your ego or protecting the team's growth trajectory. Luna: Choosing growth over ego is the difference between a manager who burns out and a leader who scales. Lucas: Scaling. That is the ultimate goal. You want to build a machine that runs better when you are away than when you are in the room. Luna: Which seems counterintuitive when you are working so hard to prove your worth, but it is the only sustainable model. Lucas: Sustainability beats intensity. Intensity gets you the promotion. Sustainability keeps you there. Luna: So the next time you feel the urge to fix everything, remember that your job is to build the system that fixes itself. Lucas: Build the system. Trust the system. Let the system shine. Luna: A challenging but necessary perspective for anyone stepping into leadership. Lucas: It is. And for those listening who are currently wrestling with that transition, ask yourself what one decision you can hand off today without losing sleep. Luna: Start small. Build the muscle of letting go. It grows stronger with every iteration. Lucas: Agreed. We will leave you with that thought as you navigate your own next steps.