Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Onboard a New Manager Without Losing Your Team
Transcript
- Lucas: So you've got a high-performing team. They've got their rhythm, their inside jokes, their shorthand. And then a new manager walks in from outside the company — or someone gets promoted over them — and within weeks, the vibe fractures. People start updating their LinkedIn profiles. Sound familiar? Luna: I've seen it happen twice. Once when we brought in a director from finance who had zero context on how the engineering team actually operated. It was like dropping a cactus into a fish tank. Lucas: Right — and that's exactly what we're unpacking today. There's a 2023 study from MIT Sloan that looked at what they call 'successor syndrome' — basically, the hidden turbulence that hits when a new manager takes over an intact team. The researchers found that about 35 percent of high-performing team members consider leaving within six months of a new manager's arrival, even if the manager is perfectly competent. Luna: Thirty-five percent — that's huge. And it's not because the new manager is bad. It's because the team's social and trust architecture just got rebuilt without their consent. Lucas: Exactly. And the fix isn't about being a 'better' manager faster. It's about doing three specific conversations in the first thirty days that most organizations skip entirely. I want to walk through a real case I saw at a mid-size SaaS company — about two hundred employees. They promoted a senior individual contributor named Priya to manage her peer group of five data scientists. She was brilliant, well-liked, had been there four years. And within a month, she was ready to quit. Luna: What went wrong? She knew the work, she knew the people — that's supposed to be the ideal promotion candidate. Lucas: On paper, yes. But nobody had prepared her for the fact that her closest work friend, Jen, had also applied for the manager role. Jen didn't get it. And Priya had never had a conversation with Jen about their new dynamic. So every decision Priya made — approving a vacation request, assigning a project — Jen interpreted through the lens of 'she's pulling rank because she got the job.' Luna: Ouch. That's a trust deficit that starts before the manager even says a word. Lucas: Exactly. And it's not just about the also-ran candidate. The MIT study identified three zones of friction: role ambiguity — the team doesn't know what the new manager's authority really means; relationship rupture — existing bonds get strained; and process disruption — the new manager changes workflows without understanding why the old ones existed. Luna: So what's the first conversation Priya should have had? And when? Lucas: Day one — or better yet, before the promotion is announced. The first conversation is what I call the 'expectations audit.' It's a one-on-one with each team member where you ask three questions: What do you need from me in this new role? What are you worried about? And what does success look like for you in the next quarter? No agenda beyond listening. No defending, no explaining. Just gathering data. Luna: That sounds simple, but most new managers skip it because they think they already know the answers. Especially if they're internal. Lucas: Exactly. Priya told me later she assumed her team would be relieved she got the promotion — they trusted her. But Jen wasn't relieved. She was resentful. And a junior analyst was terrified that Priya would now have access to his performance review history. Different people, different fears. Lucas: The second conversation happens in week two, and it's the 'stakeholder map.' The new manager sits down with the team and together they map out every person who depends on their output — product managers, sales, support, execs — and what each stakeholder actually values. Not what's on the org chart. What they care about day to day. Luna: So it's not about hierarchy. It's about dependencies. I love that. Lucas: Right. Because one thing the MIT study found was that teams with a new manager experienced a 20 percent drop in cross-functional collaboration in the first quarter — simply because the new manager didn't know who to trust externally. The team already had those relationships, but the new person inadvertently became a bottleneck. Luna: So the stakeholder map makes those relationships explicit — and the team can coach the new manager on who to talk to and how. Lucas: Exactly. And then the third conversation — this is the one most people forget entirely — is the 'trust ledger.' Somewhere in weeks three or four, the new manager asks each team member: 'What's one thing I did this week that built trust, and one thing that eroded it?' Luna: That takes guts. You have to genuinely want the answer, not just perform vulnerability. Lucas: Absolutely. And it only works if the manager doesn't get defensive. Priya tried this — she asked her team to be honest. One person told her that when she jumped in to 'help' with a data pull during a crunch, it felt like she was checking up on them. She meant well, but the signal was mistrust. She had to hear that and just say, 'Thank you. I'll stop doing that.' Luna: That's hard. But it's exactly the kind of feedback that prevents the silent exodus. Lucas: It is. And I think this is a good moment to mention something that keeps this show ad-free and independent. If you've ever used one of these frameworks at work — or if a conversation like the trust ledger has saved you from a bad hire — you can support us at buy me a coffee dot com slash fexingo. It's a simple way to keep the episodes free for everyone, and it genuinely helps us keep doing the deep-dive episodes rather than chasing ad revenue. Luna: Yeah, and honestly, the conversations we have here — they're the ones I wish I'd had when I stepped into my first management role. So if the show's added value for you, that's the place. Lucas: Alright — back to the three conversations. So Priya went through all three. The expectations audit revealed Jen's resentment. The stakeholder map showed her that the product team felt ignored by data science. And the trust ledger caught her tendency to helicopter-tutor instead of delegate. Six months later, her team's engagement scores were higher than before the transition, and Jen had become one of her strongest allies. Luna: What changed for Jen specifically? That's the hardest relationship to salvage. Lucas: Priya had a direct conversation — not in the audit, but separately — where she said, 'I know you wanted this role. I want you to succeed here, and I want to make sure you feel like your contributions are visible. Can we design a project together where you get the lead on something you care about?' Luna: So she didn't try to pretend the resentment didn't exist. She named it and offered a path forward. Lucas: Exactly. And that's really the core of the whole framework — you can't resolve a trust issue you haven't acknowledged. The MIT study calls this 'role negotiation.' It's the idea that both the manager and the team need to actively renegotiate their relationship, not just assume it carries over from the previous structure. Luna: I want to zoom out for a second. This framework — expectations audit, stakeholder map, trust ledger — it works for external hires too, right? Lucas: It does, but external hires have an extra challenge: they don't have any trust capital to start with. So the first thirty days should be a 'listening tour' — no major changes, no new processes, just meeting people and asking the same three questions from the audit. The data from the study shows that external managers who made at least one operational change in the first month had a 40 percent higher attrition rate in their teams over the next year. Luna: Wow. So the urge to 'add value' early actually backfires. Lucas: It's counterintuitive. You're hired to bring fresh perspective, but if you impose it before you understand the existing culture, your team reads it as disrespect. The best external managers spend the first thirty days asking questions, not giving answers. Luna: So for a new manager listening right now — maybe you just got promoted, or you're about to — what's the one thing you do in the first week? Lucas: Schedule thirty-minute one-on-ones with every direct report. No agenda. Just ask: 'What should I know about this team that isn't written down anywhere?' That question alone surfaces the unwritten rules — which meeting is actually the decision-making meeting, whose opinion really matters, what landmines to avoid. It's the single highest-leverage move. Luna: And if you're a team member whose team just got a new manager — what do you do? Lucas: I'd say two things. One, be explicit about what you need — don't assume they'll figure it out. And two, give them the gift of honest feedback early. If they're open to it, you can shape their behavior before bad patterns solidify. A senior engineer at Priya's company told her in week two: 'When you assign work, give me the 'why' not just the 'what.' That simple sentence probably saved them months of friction. Luna: I love that. It's a two-way street. The team has to meet the manager halfway. Lucas: Exactly. Management transitions are fragile moments. But they're also opportunities — if you handle them deliberately, you can build a stronger foundation than you had before. The worst-case scenario is pretending nothing changed. Luna: So next time you see a new manager walking in, don't just hand them the keys. Hand them a stakeholder map and a trust ledger. Lucas: And a coffee. Definitely a coffee. Alright — that's our episode for this week. We'll be back next Monday with another framework you can actually use on Tuesday.