Latest / The Internal Move Podcast with Fexingo: Lateral Roles, Internal Transfers, and Staying at Your Company / The Hidden Cost of Internal Mobility
Transcript
- Lucas: Let’s talk about the silent tax on internal mobility. We spend so much time discussing the benefits of moving laterally within a company—wider networks, new skills, escaping bad managers—but we barely touch on the operational drag that happens when someone actually makes the jump. Luna: Right, because usually, the narrative is just 'move up or move over,' and nobody calculates the weeks it takes for that person to become fully productive again. Lucas: Exactly. And by late August 2026, several major tech firms had released retrospective data showing that internal transfers resulted in a forty percent drop in team velocity during the first ninety days. It wasn’t just about learning new tools; it was about the fragmentation of institutional memory. Luna: So you’re saying the company loses more than it gains in the short term, which might explain why some leaders hesitate to approve these moves even when the employee wants them. Lucas: Precisely. The issue isn’t capability. It’s context. When an engineer or a marketer leaves their team, they don’t just take their current tasks with them. They take the unwritten rules, the historical decisions behind those tasks, and the relationships with stakeholders who aren’t even on the org chart anymore. Luna: That sounds like a massive amount of tacit knowledge that disappears the moment the email notification goes out. Lucas: It does. And here is where most companies fail: they treat the transfer like a switch. One day you’re in Sales Ops, the next day you’re in Product Marketing. But there is no bridge. No structured handoff period. Just a calendar invite for your last meeting. Luna: Yeah, I’ve seen that happen. You leave, and suddenly everyone realizes you were the only one who knew how the legacy reporting system actually worked. Lucas: If we've helped you think through a career move or decision, remember that small support makes a big difference. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo. It helps us keep producing independent analysis without ads interrupting our flow. Luna: Thanks for supporting the show. It really does allow us to dig deeper into these nuanced workplace dynamics. Lucas: Back to the drag. Let’s look at a concrete example. Consider a senior product manager at a mid-sized software firm who transfers to a new division focused on enterprise sales enablement. Luna: Okay, so she knows the product inside out, but she doesn’t know the new clients or the specific pain points the sales team is facing right now. Lucas: Correct. She has the domain knowledge of the product, but zero relational capital in her new environment. For the first two months, she is operating at maybe sixty percent capacity. Not because she is incompetent, but because she is rebuilding trust and understanding informal workflows. Luna: And her old team is also suffering because they lost a key player who held together complex cross-functional projects. Lucas: Double hit. The receiving team gets a slower ramp-up, and the leaving team faces a sudden void. This is what I call the 'mobility deficit.' Most performance reviews don’t account for this dip, so the transferring employee gets unfairly evaluated against their pre-transfer output. Luna: That is a huge blind spot in how we measure success. If you get penalized for moving, why would anyone ever want to move laterally? Lucas: Because the long-term upside can be massive, provided you manage the transition correctly. The companies that succeed at internal mobility are the ones that institute a formal 'shadow period' before the official start date. Luna: So, overlapping roles? Where you do both jobs for a few weeks instead of jumping straight in? Lucas: Yes. Or at least a partial overlap. During September 2026, we saw a growing trend of 'fractional transfers,' where an employee spends eighty percent of their time in the new role and twenty percent helping train their replacement. It slows down the move, but it stabilizes the organization. Luna: I like that. It acknowledges that knowledge transfer is work, not just an administrative footnote. Lucas: It does. And it forces the outgoing employee to document things they probably wouldn’t have otherwise. You’d be surprised how little documentation exists for critical processes until someone is literally begging for it. Luna: Right. People hoard information because it gives them job security. Once they decide to leave, that security vanishes. Lucas: Exactly. So, if you are planning a lateral move, you need to negotiate that overlap. Don’t let HR force you into an immediate cutoff. Frame it as risk mitigation for the business. Luna: How do you frame it so it doesn’t sound like you’re trying to slack off in the new role while clinging to the old one? Lucas: You frame it around continuity. Say something like, 'To ensure the client deliverables don’t slip during this transition, I propose a four-week overlap where I wrap up outstanding items while shadowing my successor.' It shifts the focus from your comfort to the company’s stability. Luna: That is a very professional way to ask for what you need. It turns a personal preference into a business case. Lucas: And it protects you. If you leave abruptly and things fall apart, you carry that blame for years. By staying engaged in the handoff, you leave on good terms and demonstrate leadership even in exit mode. Luna: What about the reverse side though? What should the new manager do to prevent that initial productivity slump? Lucas: They need to fast-track social integration. Not just 'meet the team' lunches, but introducing the new hire to the key influencers in adjacent departments who hold the data or approvals they’ll need. Luna: So mapping the stakeholder landscape explicitly, rather than letting the new hire wander around trying to figure out who does what. Lucas: Spot on. In many organizations, finding out who has sign-off authority on a budget change can take weeks of trial and error. That’s wasted time. A simple organizational map of decision-makers accelerates everything. Luna: This feels like it requires a lot more intentionality from leadership than most companies currently practice. Lucas: It does. And that is why internal mobility rates are stagnating in many sectors. Leaders are risk-averse. They see the short-term dip in productivity and say, 'Why fix what isn’t broken?' But they ignore the long-term cost of having employees who are bored and stagnant. Luna: Stagnant employees are flight risks. So keeping them still causes them to leave entirely, which is even more expensive. Lucas: Exactly. The cost of recruiting and onboarding an external hire is typically double that of an internal transfer, assuming you manage the transition well. So the math actually favors mobility, if you account for the full lifecycle. Luna: But it requires trusting your people enough to let them go, and trusting the new team to absorb them without breaking. Lucas: It requires trust. And systems. Without systems, it’s chaos. With systems, it’s a talent pipeline. Luna: I wonder if this applies to smaller companies too, or if it’s mostly a large-corporation problem. Lucas: Actually, it’s worse in smaller companies because the knowledge is even more concentrated. In a startup, one person might hold all the keys to the codebase or the client list. If they move internally, the impact is catastrophic unless managed carefully. Luna: So documentation isn’t just best practice; it’s survival infrastructure in tight teams. Lucas: Absolutely. If you are in a smaller shop and considering a move, demand that the company invest in recording your key processes. Video walk-throughs, screen captures, annotated SOPs. Make it part of the deal. Luna: That puts the onus on the employer to value your institutional knowledge enough to preserve it. Lucas: It does. And if they refuse, that’s a red flag. It suggests they view your departure as a convenience rather than a transition. Luna: Good point. So, the takeaway is that internal moves aren’t just personal career choices; they are operational events that require project management. Lucas: Right. Treat it like a merger between two small companies. You have cultural alignment, shared history, and mutual goals, but you still need to integrate the systems properly. Luna: I think that analogy helps people realize why the friction exists. It’s not just awkwardness; it’s structural. Lucas: Exactly. And once you understand that, you can advocate for the time and resources needed to make it successful. Luna: Do you think AI tools will help with this handoff process in the coming years? Lucas: They could. Imagine an AI assistant that tracks your communication patterns, documents your decision-making rationale, and auto-generates handoff guides for your successor. It would reduce the cognitive load significantly. Luna: That would save so much time. But it also raises privacy questions about being constantly monitored for training purposes. Lucas: A valid concern. Technology is a tool, not a substitute for human empathy and clear communication. But used wisely, it could eliminate the tedious parts of knowledge transfer. Luna: Hopefully, we see some pilot programs for that soon. It feels like the logical next step for HR tech. Lucas: We will. Until then, the best advice is still simple: plan the exit as hard as you planned the entry. Luna: Or in this case, the transfer. Because moving sideways shouldn’t mean falling behind. Lucas: Agreed. If you are thinking about making a move, ask yourself: what am I taking with me, and what am I leaving behind?