Latest / The Internal Move Podcast with Fexingo: Lateral Roles, Internal Transfers, and Staying at Your Company / How an Internal Transfer Can Help You Build a Cross-Functional Skill Set
Transcript
- Lucas: You've heard the advice a hundred times: if you want to grow your skill set, move to a new company or go back to school. But there's a third path that doesn't get nearly enough attention, and it's the internal transfer as a deliberate reskilling vehicle. Luna: You mean using an internal move specifically to learn a new function, not just to escape a bad situation or get a title bump? Lucas: Exactly. I'm thinking of a case from a mid-size B2B SaaS company I know — call it CloudHarbor, about eight hundred employees. A marketing manager named Priya had been in brand marketing for five years, and she realized the whole industry was shifting toward data-driven decisions. She wanted to learn product analytics, but she didn't want to start over at a new company as a junior analyst. Luna: So she looked internally. That makes sense — she already knew the product, the customers, the stakeholders. She just needed the technical reps. Lucas: Right. She started by shadowing the product analytics team for two weeks. She went to their stand-ups, sat in on their sprint reviews, even asked one of the senior analysts to let her pair on a dashboard project. That gave her enough confidence to propose a six-month rotation to her manager and the analytics director. Luna: A rotation is smart because it's lower risk for both sides. If it doesn't work, she goes back to marketing. But what did she actually negotiate into that rotation? Lucas: She negotiated three things. First, a dedicated mentor on the analytics team who would give her weekly code reviews. Second, a budget to take an online SQL and Python course — about eight hundred dollars. Third, a clear set of deliverables by month four: she had to build a churn analysis dashboard from scratch, using real data, and present it to the VP of Product. Luna: That's a concrete learning plan. I've seen the opposite happen — someone assumes that just being in a new role will automatically teach them stuff, and they end up doing the same tasks they already knew. Lucas: Yeah, that's the trap. An internal transfer without a learning framework is just a lateral move with a different org chart. Priya was deliberate. She even documented her learning objectives with her current manager before she left marketing, so they both had a record of what she was going to build. That made it easier to transition back if needed, but also gave her accountability. Luna: And what happened after the six months? Lucas: She didn't go back to marketing. The analytics team offered her a permanent role, and she took it. Within a year she was leading a small team doing product analytics for the growth vertical. Her marketing background actually turned into an advantage — she could translate business questions into analytical models better than someone who'd only ever done data. Luna: So the cross-functional piece is key. She didn't just learn SQL; she brought her existing knowledge into a new context. That's something an external hire can't replicate easily. Lucas: If today was actually useful to you — if you're thinking about a career move or how to build a broader skill set — the reason we can keep having these conversations without ads is listener support. You can help keep the show going at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. Luna: Yeah, and it really does make a difference. Even a small contribution helps us stay independent and focused on practical advice. Lucas: So back to Priya's story — there's another angle I want to pull out. When she negotiated the rotation, she also asked for the analytics team to treat her like a junior for the first three months. That meant she attended their beginner training sessions, even though she was a senior marketing manager. She was willing to be a novice again. Luna: That's hard for a lot of people. You have to swallow your pride. But it's exactly the right move if you actually want to learn. Lucas: Exactly. And it's easier to do that inside a company where people already know your reputation. If she'd joined a new company as a junior analyst, she would have had to prove she was competent from day one. Internally, people already respected her, so they gave her the space to learn. Luna: That's a huge hidden advantage of the internal transfer. You're a known quantity, so you get more grace to be a beginner. But you also need to be explicit about wanting that grace. Lucas: Right. The other thing Priya did was set up a monthly check-in with her old marketing manager for the first three months. That way the bridge wasn't burned — she kept her network warm. And it also served as an informal feedback loop: her old boss could tell her if she was losing touch with business context. Luna: That's smart. Too many people treat an internal transfer like a clean break. But the whole point of staying at the same company is that your relationships carry over. Lucas: There's a cautionary tale here too. I had a colleague named Derek who transferred from finance to operations at a large retail company. He thought that just being in ops would teach him supply chain. But he didn't ask for any training, didn't get a mentor, and his new manager assumed he already knew the basics because he came from a 'quantitative background.' Luna: And what happened? Lucas: He floundered for six months. His projects were late, he kept making forecasting errors that the warehouse team caught, and eventually his manager put him on a performance improvement plan. He ended up leaving the company entirely. And the sad part is, he had the raw ability — he just assumed the transfer itself would teach him. Luna: So the lesson is: treat an internal transfer like a mini degree program. You need a curriculum, not just a new desk. Lucas: Exactly. And part of that curriculum is identifying the specific skills you want to build. For Priya, it was SQL, Python, and stakeholder presentation. For someone else, it might be project management, client negotiation, or UX research. The key is to name them upfront and build a plan around them. Luna: And then you also need to think about who will teach you. Priya had a dedicated mentor. Derek had nobody. Lucas: Right. So when you're in conversations about a potential transfer, ask specifically: 'Who will be my primary mentor or buddy for the first ninety days? Can we schedule weekly one-on-ones for skill building?' If the answer is vague, that's a red flag. Luna: What about the training budget? Not every company has eight hundred dollars to spare for a course. Lucas: True, but you can be creative. Some companies have a learning reimbursement program that covers any course approved by your manager. Others have a corporate account with LinkedIn Learning or Coursera. And if there's no budget at all, you can ask for time — two hours a week of protected learning time, no meetings. That's often easier to get than cash. Luna: I like that. Time is a form of budget. And it signals that the manager is invested in your growth. Lucas: Yeah. And one more thing — Priya made sure her learning objectives were tied to a real business problem. She didn't just say 'I want to learn Python.' She said 'I want to build a churn analysis dashboard that the product team can use to reduce customer loss by five percent.' That made it a win for the company, not just a personal development project. Luna: So she sold it as a business case, not a career request. That's a smart framing. Lucas: It is. And it's a framing that works especially well inside the same company, because you already know what the business needs. You can point to a specific gap and say, 'I can help fill that gap if I build these skills.' Luna: Alright, so let's say someone wants to do this. What's the first step? They're in, say, customer support and they want to move into product management. How do they start? Lucas: First, they should map the skill gap. Talk to a product manager in their company — ideally more than one — and ask what the top three technical or strategic skills are for a junior PM. Then audit themselves honestly. Maybe they already have great user empathy from support, but they need to learn prioritization frameworks and basic data analysis. Luna: And then what? Do they just ask their manager for a transfer? Lucas: Not immediately. They should first build a small proof of concept in their current role. For example, they could volunteer to help the product team with user research calls, or analyze support ticket trends and present findings to the PM. That gives them a portfolio piece and a reason to start the conversation. Luna: So it's like a mini internal internship before you even ask for the transfer. Lucas: Exactly. When you eventually sit down with your manager, you can say, 'I've already done X, Y, and Z on my own time. I've built the foundation. Now I want to formalize it with a rotation.' That's much more persuasive than just saying you're interested. Luna: And if your manager says no? Lucas: Then you evaluate why. Sometimes it's a timing issue — maybe the team is understaffed and they can't lose you right now. In that case, you can negotiate a deferred transfer: 'Can we revisit this in six months? In the meantime, can I spend a few hours a week shadowing the other team?' If the manager is just blocking you because they don't want to lose a good employee, that's a different problem — and it might tell you something about the company culture. Luna: Yeah, at that point you might need to consider an external move. But I think the internal path is worth trying first, especially if you want to build cross-functional skills without starting over. Lucas: I agree. And I think the big takeaway from Priya's story is that an internal transfer can be the most efficient way to reskill — if you treat it with the same seriousness as a degree program. You need a plan, a mentor, a timeline, and a deliverable. Without those, you're just changing chairs. Luna: And that's a missed opportunity, because you already have the network and the context. That's a huge head start. Lucas: So if you're thinking about building a new skill this year, don't assume you have to leave your company to do it. Look at the team next door. They might be looking for someone just like you. Luna: And that's where we'll leave it. Thanks for listening.