Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Transition From Peer to Boss
Transcript
- Lucas: You get promoted. You're thrilled. You walk into your first team meeting as the new manager, and suddenly the person who used to sit next to you and complain about the boss is now looking at you like you're the boss. That's a weird feeling. Luna: It is. And it's one of the hardest transitions in leadership. I've seen really good individual contributors stumble here because they underestimate how much the dynamic shifts. Lucas: Exactly. So today we're going to get specific about one case: Priya. She's a senior software engineer at a mid-size SaaS company called LogiFlow, forty people in engineering. She gets promoted to team lead over a group of four developers she's worked with for two years. Two of them are close friends — they grab lunch together regularly. Luna: And that friendship is exactly the tightrope. She doesn't want to lose the connection, but she also can't have them treating her like the old Priya when she needs to assign work or give feedback. Lucas: Right. So the first thing we talk about is the very first team meeting after the promotion. Priya's instinct is to downplay the change — say stuff like 'I'm still the same person, just with a new title.' But that actually backfires. Luna: Because it's not true. The title changes the relationship whether you want it to or not. Pretending it doesn't creates confusion. Lucas: Exactly. Better approach: she opens the meeting by acknowledging the elephant. Something like 'Look, I know this is a little awkward. I was your peer two days ago. I'm going to be learning this role, and I'll probably make mistakes. But here's what's changing and what isn't.' Luna: That's disarming. It gives people permission to feel the awkwardness without pretending. Lucas: And then she lays out three specific things that change and three that don't. The things that change: she now owns the priorities for the team, she's the one who gives performance feedback, and she's the escalation point for blockers. The things that don't change: they still do code reviews together, she still cares about their growth, and they can still be honest with her. Luna: So she's drawing a line, but also leaving a bridge. I like that. Lucas: Now, the next step is harder. She needs to have a one-on-one with each former peer. And this is where most new managers mess up — they think they can just schedule the regular weekly one-on-one and talk about projects. But there's a specific conversation that needs to happen first. Luna: The 'new rules' conversation. What does that look like for Priya? Lucas: She books thirty minutes with each person. She starts by saying, 'I want to make sure our working relationship is clear and comfortable. Here's what I'm thinking: I'll still be direct with you, but now I might also need to give you feedback you don't love. And I need to know if you're okay with that.' Then she asks them: 'What do you need from me as your manager that you didn't need from me as a peer?' Luna: That question is gold. It flips the script from 'I'm your boss now' to 'I want to serve you better.' Lucas: Exactly. And the answers can be surprising. One of Priya's friends said, 'I need you to stop texting me after 9 p.m. about non-urgent stuff because now it feels like pressure.' Another said, 'I need you to be more explicit about what you expect from me — as a peer we just figured it out, but now I need clarity.' Luna: That's really useful. Most new managers don't ask, they assume. Lucas: So that's step one and two: the team meeting acknowledging the shift, and individual conversations setting new norms. Step three is what I call the 'transition charter' — a one-page document Priya writes for herself and shares with her manager, not necessarily the team. Luna: What goes in it? Lucas: It answers three questions: What am I stopping doing that I used to do as an individual contributor? What am I starting doing that's new? And what am I keeping the same? For Priya, stopping: writing production code for the main product — she only fixes critical bugs now. Starting: attending the weekly planning meeting with the VP. Keeping: still doing code reviews twice a week, still being available for whiteboard discussions. Luna: That charter is a reality check. It forces her to see the trade-offs. Lucas: And it prevents the biggest mistake new managers make: trying to do both jobs — their old one and the new one — and burning out. If Priya doesn't stop coding, she'll never have time to lead. Luna: Right. And her team will be confused about whether she's a player-coach or just a player with a title. Lucas: Exactly. So she shares that charter with her manager, gets alignment, and then she can confidently say no to coding requests because she has a clear agreement. Luna: Alright, let's talk about the awkward social stuff. Priya and her two friends — what does she do about lunch? Lucas: This is where it gets really practical. She doesn't have to stop being friends. But she does need to create some separation. A simple tactic: she rotates lunch invites. One day with the whole team, one day alone, one day with a different group. She doesn't always sit with her old crew. That sends a subtle signal that she's now everyone's manager, not just their friend. Luna: And if a friend starts venting about another team member in a way that's inappropriate for a manager to hear? Lucas: She has a script for that. She says, 'I hear you, and I want to help, but I think this is something you should bring up directly with that person. If you want me to mediate, we can set up a three-way meeting.' She redirects without shutting down the friendship. Luna: That's a clear boundary. And it protects her from being put in a position where she has to act on gossip. Lucas: Exactly. Now, one more piece: the first time she has to give critical feedback to a former peer. Let's say Priya's friend, Alex, has been shipping sloppy code. She can't let it slide because they're friends. Luna: How does she handle that differently than she would with a stranger? Lucas: She starts by naming the elephant again. 'Alex, this is awkward because we're friends, and I need to give you some feedback that's hard for me to say. But here's what I'm seeing: the last two pull requests had bugs that got caught in review. That's not like you. What's going on?' Luna: So she acknowledges the relationship, states the observation, and then asks a question instead of accusing. Lucas: Right. And then she listens. Nine times out of ten, there's something behind it — a personal issue, a misunderstanding about the deadline. By framing it as concern rather than criticism, she preserves the friendship and addresses the performance. Luna: Seems like the theme here is: don't pretend nothing changed, but don't let the change destroy the relationship. Lucas: That's it. And honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. We keep the show ad-free, and listener support is what makes that possible. Luna: Yeah, we really appreciate it. It's a small gesture that goes a long way for us. Lucas: Alright, back to Priya. One last tactic: the 'transition timeline.' She maps out the first two weeks — day one through day fourteen — with specific actions each day. Day one: team meeting. Day two through five: one-on-ones. Day six: share charter with her manager. Day seven: stop coding. Day eight: observe a team retro without running it. And so on. Luna: That's concrete. Most new managers just wing it and then wonder why they're overwhelmed. Lucas: Exactly. Having a plan reduces the anxiety of the unknown. And it signals to the team that she's intentional about the transition. Luna: So for someone listening who just got promoted — what's the one thing they should do tomorrow? Lucas: Schedule those one-on-one conversations with each former peer. Not to talk about projects — to talk about the relationship. Ask the question: 'What do you need from me as your manager that you didn't need from me as a peer?' That one conversation can prevent months of awkwardness. Luna: I think that's great advice. Priya's story is a good reminder that the transition is hard, but it's manageable with the right moves. Lucas: And we'll be back next time with more practical tactics for new managers.