Latest / The Internal Move Podcast with Fexingo: Lateral Roles, Internal Transfers, and Staying at Your Company / The Manager Trap of Internal Transfers
Transcript
- Lucas: We’ve spent the last twenty episodes dissecting the mechanics of the internal transfer. How to ask for it, how to frame it, what to do when you’re trying to escape a bad situation. But I think we’ve been looking at the wrong variable. The one that actually determines whether an internal move succeeds or fails isn’t the role itself, or the salary bump, or even the team’s technical capability. It’s the person who holds your performance review. Luna: So you’re saying the manager is the bottleneck? That feels like a cliché, Lucas. Isn’t every manager a bottleneck if they’re incompetent? Lucas: It’s not about competence alone. It’s about alignment. When you stay in a role, you have months or years to build trust with your manager, to learn their communication style, to understand what ‘good’ looks like to them. When you transfer internally, you start from zero. You have to rebuild that entire dynamic from scratch, often while still being expected to perform at a high level immediately. Luna: That makes sense. You lose all the social capital you built in your old department. So how do you vet a new manager before you make the jump? Do people actually interview their future bosses? Lucas: Rarely. And that’s the mistake. Most candidates treat the internal transfer like a job application where they are the only ones being evaluated. They focus on the skills gap, the projects, the tech stack. They don’t spend enough time assessing the human element. I want to talk about three specific patterns of managers that signal a transfer is likely to fail, and how to spot them early. Luna: Okay, lay them out. What’s the first red flag? Lucas: The first pattern is the micromanager who mistakes control for care. These managers are often high performers themselves, so they assume everyone else needs that same level of direction. If you’re moving into a role where you need autonomy, this is a disaster. You’ll spend eighty percent of your energy reporting on work instead of doing it. Luna: I’ve seen that. It’s exhausting because you feel like you’re constantly proving you exist. Is there a way to test for this during the interview process? Lucas: Yes. Ask them about their last promotion. Did they promote someone by giving them more ownership, or did they promote someone who just worked longer hours under their direct supervision? Watch their body language. If they hesitate, or if they describe their best employee as the one who never surprises them, run. That’s not leadership; that’s risk aversion. Luna: Right. Because if they promoted the person who never surprised them, they probably micromanaged them into submission. That’s not a scalable model. Lucas: Exactly. The second pattern is the invisible manager. This is common in large organizations where leaders are stretched across multiple teams or divisions. They might be well-meaning, but they are perpetually unavailable. You transfer into the role, and suddenly you realize no one is making decisions. You’re waiting for approvals that never come, or guidance that never arrives. Luna: That’s worse than the micromanager in some ways. At least with micromanagement, you know what’s expected. With invisibility, you’re flying blind. How do you distinguish between a busy manager and an absent one? Lucas: Look at their calendar habits and their communication rhythm. In the interview, ask: 'What does a typical feedback cycle look like here?' If they say 'we ad-hoc it' or 'just ping me,' that’s a warning sign. You want a manager who has structured touchpoints. Even if they’re busy, they should have protected time for their direct reports. If they can’t protect thirty minutes a week for you, they won’t protect it for your career. Luna: Thirty minutes is reasonable. But what if the manager is great, but the team culture is toxic? Does that count as a management failure? Lucas: Absolutely. A manager is responsible for the culture of their team. If the team is siloed, political, or hostile, that reflects directly on the leader. You might think you can rise above it, but you can’t. Culture eats strategy for breakfast, and it eats careers for lunch. If the team doesn’t trust each other, they won’t trust you either. Luna: So you’re suggesting that we should treat the manager and the team as a single unit when evaluating a transfer. Not just the job description. Lucas: Precisely. Now, let’s talk about the third pattern, which is the most dangerous because it’s the hardest to see until it’s too late. It’s the manager who sees you as a replacement. Not for their job, necessarily, but for their current workload. They bring you in to handle the dirty work, the tedious tasks, the projects nobody wants. Once you’re in, you’re stuck. You become the specialist in something nobody else wants to do, and your path to promotion is blocked because you’re too valuable in your current grunt-work role. Luna: Oh, that’s brutal. It’s like being trapped in a golden handcuff situation. You’re useful, but you’re not growing. How do you avoid getting sucked into that trap? Lucas: Ask about the trajectory of the role. Who held this position before you? Where did they go? If the previous person stayed for five years and hasn’t moved up, ask why. If they left after six months, ask why. The history of the role tells you everything about its potential. Also, listen for words like 'critical infrastructure' or 'core operations.' Those are often code for 'maintenance mode.' You want roles labeled 'growth,' 'innovation,' or 'expansion.' Luna: So you’re advising listeners to reverse-engineer the role’s history before they even apply. That’s smart. It shifts the power dynamic a bit. Lucas: It does. But here’s the hard truth: sometimes, despite all your due diligence, the manager turns out to be a mismatch. You’ve transferred, you’ve started, and three months in, you realize you hate working for them. What do you do then? Go back to your old team? Luna: That seems risky. Would my old manager even take me back? Or would I be seen as a failure for leaving and coming back? Lucas: It’s awkward, yes. But staying in a bad relationship is worse. If you transfer internally and the fit is wrong, you have two options. One, you try to fix it. You have a direct conversation with your manager about your working style, your expectations, and the friction points. Sometimes, awareness is enough to change behavior. Two, you accept that the experiment failed and look externally. There is no shame in realizing an internal move was the wrong choice. In fact, it’s a valuable data point for your next decision. Luna: I think a lot of people feel trapped by the sunk cost fallacy. They think, 'I already made the move, I can’t go back.' But really, they’re just delaying the inevitable pain. Lucas: Exactly. The sunk cost of the transfer—losing your old colleagues, resetting your reputation—is real. But the cost of staying with a bad manager is compounding. Every month you stay, your network atrophies, your skills stagnate, and your morale drops. It’s a slow leak. Luna: So, to summarize, when considering an internal transfer, prioritize the manager over the title. Vet them for micromanagement, invisibility, or exploitation. Check the role’s history. And have a plan B if it doesn’t work out. Lucas: And remember, you are not obligated to accept a role just because it’s available. You have optionality. Use it. Don’t let the convenience of staying in-house override the quality of your daily work life. Luna: Before we wrap up, I want to circle back to something we mentioned earlier about building trust from scratch. How long does that usually take? Lucas: Roughly ninety days to establish basic competence, another ninety to build trust. So, six months minimum before you’re truly operating at full capacity. If your manager expects instant synergy, they’re unrealistic. Luna: Six months. That’s a long time to be on probation in your own career. Lucas: It is. Which is why choosing the right manager is so critical. It’s the foundation of that entire timeline. Luna: This has been incredibly practical. I think a lot of people overlook the human element in these transitions. Lucas: They do. But humans drive businesses. If the human connection is broken, the business logic doesn’t matter. Luna: Yeah, exactly. Well, we’re approaching our time limit, and I want to pause here for a moment because we’ve been talking a lot about the personal investment required to make these moves successfully. Lucas: Right. And that investment often extends beyond just your time. It’s about supporting the ecosystem that helps us think through these complex career decisions without the noise of generic advice. Luna: If you’ve found value in how we break down these professional challenges, consider supporting the show directly. It keeps the content independent and ad-free. Lucas: You can find us at buy me a coffee dot com slash fexingo. No pressure, just appreciation if it resonates. Luna: Thanks for listening. Now, back to the topic. Lucas: One final thought on that nine-month timeline for trust. Have you ever experienced a manager who accelerated that process? Someone who got it right immediately? Luna: I had one once. She just asked me what I needed to succeed and then stepped back. It felt like magic compared to the usual chaos. Lucas: That’s rare. But it proves the point. When it works, it’s transformative. When it fails, it’s paralyzing. Knowing the difference is your superpower. Luna: Superpower. I like that. Thanks, Lucas. Lucas: Thanks, Luna. Let’s keep asking the hard questions.