Latest / The Internal Move Podcast with Fexingo: Lateral Roles, Internal Transfers, and Staying at Your Company / How an Internal Transfer Can Help You Renegotiate Your Role Scope
Transcript
- Lucas: You know that moment when you've been in a role long enough that you can do parts of it on autopilot, but the autopilot parts are exactly the parts you hate? Luna: Oh, I know that feeling. The tasks that used to challenge you become routine, but somehow they still take up half your week. Lucas: Right. And for a lot of people, an internal transfer feels like the only escape hatch. You think, 'If I can just move to a new team, I'll get to do the interesting stuff again.' But here's what I've noticed — a lot of people treat the transfer as a lateral move that just happens to have a different title, and they don't actually change what they do day to day. Luna: They end up with the same low-value tasks, just in a different color spreadsheet. Lucas: Exactly. So today I want to talk about a specific case where someone used an internal transfer to renegotiate her role scope — not just her title or her pay, but the actual content of her job. Her name is Jenna, she's a senior marketing manager at a midsize consumer goods company. She'd been in brand marketing for about three years, and she was drowning in legacy reporting. Luna: Legacy reporting — that's the stuff that was designed for a previous team structure and nobody ever retired. Lucas: Precisely. Every Monday she pulled a 47-row spreadsheet that three other teams also pulled. No one read it. But it had been on her plate since before she joined. So when a product marketing role opened up on the same floor, she applied. But she didn't just apply for the job description as written. Luna: She brought a wish list? Lucas: She brought a negotiation. She went into the transfer conversation with her future manager and said, 'I want to move into product marketing, but I want to redesign the role so it doesn't include the three things that made me miserable in brand.' And she had specifics. One, drop the legacy reporting. Two, add a direct line to the product strategy team — not just the marketing team. Three, secure a formal mentorship budget so she could learn the product side faster. Luna: A mentorship budget — that's smart. Most people don't think to ask for that during a transfer. Lucas: Most people don't think to ask for anything during a transfer. They're so grateful to get the move that they accept the role as-is. But Jenna's manager actually said yes to all three. Why? Because Jenna framed it as making her more effective in the new role, not as a demand. The legacy reporting? She said, 'If I'm not pulling that spreadsheet, I can spend that time on competitive analysis that directly feeds product strategy.' The direct line? She said, 'I'll have faster feedback loops, which means fewer misaligned campaigns.' The mentorship budget? She said, 'I'll ramp up in half the time.' Luna: So she tied every ask to a business outcome. That's the opposite of 'I want this because it's better for me.' Lucas: Exactly. And the interesting thing is, her manager told me later that he was actually relieved she brought it up. Because he'd inherited that role from someone who'd left abruptly, and the job description was basically a photocopy of the previous person's responsibilities. He hadn't had time to rethink it. Jenna gave him permission to update it. Luna: That's a huge insight — your future manager might secretly want you to reshape the role because they know it's outdated but don't have the bandwidth to redesign it themselves. Lucas: Right. So let's break down the three elements Jenna renegotiated, because they form a framework anyone can use. Element one: subtract what's not valued. Luna: The legacy reporting — that was pure subtraction. Lucas: Pure subtraction. And she had evidence: she'd asked around and confirmed that the report hadn't led to a decision in over a year. So she could say, 'This is a candidate for retirement.' Element two: add a structural connection that gives you leverage. Luna: The direct line to product strategy. That's not just a nice to have, it changes what you work on. Lucas: It changes your input into the product roadmap. Instead of being told, 'Here's the launch date, go write copy,' she'd be in the room when they decided what to launch. That's a completely different job. Element three: invest in your ramp-up. The mentorship budget. That one's interesting because it's not about the role itself — it's about the transition. Luna: But it signals that she's serious about becoming excellent in the new role. It's a commitment device. Lucas: And it's a concrete ask. 'I want $2,000 to work with a product marketing coach for three months.' Her manager said yes on the spot because it's a rounding error in the department budget and it directly addresses the risk of her failing in the new role. Luna: I want to talk about timing, because I think a lot of people wait until they've already accepted the transfer to ask for changes. By then, the job description is set. Lucas: The window is before you say yes. Jenna had an informal conversation with her future manager before she even formally applied. She said, 'I'm interested, but I want to talk about the shape of the role first.' That conversation is where she floated her three elements. The manager said yes in principle. Then she applied. The formal offer was basically a formality. Luna: So the leverage is in the exploratory phase, not the acceptance phase. Lucas: You have maximum leverage before they've invested in the hiring process. Once they've written the offer letter, they want you to say yes, but they're also thinking about the backfill on your current team. The window narrows fast. That said, I should mention that not every manager is going to say yes to three big changes. Jenna's case was unusually clean. Luna: Yeah, but even getting one of those three would have been a win. The subtraction alone would have made her happier. Lucas: True. And the subtraction is often the easiest to negotiate. Because if you can show that a task has zero downstream value, the manager has no reason to keep it. The hard one is the addition — the direct line to another team — because that involves getting another person's buy-in. Jenna had already built a relationship with the product strategy lead during a cross-functional project. That wasn't luck; she cultivated it. Luna: So part of the prep is doing the relational groundwork before you even know you'll want the transfer. Lucas: Exactly. And we do talk a lot on this show about building coalitions before you move — we had an episode on that. But Jenna's story adds a layer: she didn't just build relationships for visibility. She built them so she could point to a specific person and say, 'Lisa on product strategy and I already have a working rhythm. If I report into her team's meetings, we'll hit the ground running.' Luna: That's a concrete example of how internal transfers can help you test a new location or team before committing — another topic we've covered. But the scope renegotiation piece is something I don't think we've dug into before. Lucas: No, we haven't. And I think it's because a lot of career advice treats the job description as fixed. The assumption is, 'You're applying for an existing role; take it or leave it.' But internal transfers are different. You're already inside the company. You have context, relationships, and credibility. You can say, 'I'm not applying for the role as written. I'm applying for a version of the role that serves the business better.' Luna: And that version might not exist yet. You're essentially co-creating it with your future manager. Lucas: That's the frame. And it's a subtle but powerful shift. Instead of saying, 'I want this job,' you say, 'I want to solve this problem for you, and here's the role that would let me do it.' Luna: You know, that reminds me of something. If we've helped you think through a career move or decision, listener support is what keeps this show ad-free and independent. There's no paywall, no sponsor breaks. It's just the conversations. If that's been useful to you, you can support us at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. Lucas: And that support genuinely allows us to keep diving into stories like Jenna's without worrying about ad revenue. So, back to the framework. Once you've negotiated the scope, there's a second move that Jenna made after she started the role that I think is worth highlighting. Luna: What was that? Lucas: She documented the changes she negotiated and sent a one-page summary to her manager and the product strategy lead. It wasn't a formal contract. It was just: 'Here's what we agreed — I'll own X, Y, Z, and I'll be in this meeting weekly. If anything shifts, let me know.' She told me she did it because she wanted to prevent scope creep. Luna: Smart. Because without documentation, the old tasks have a way of finding you. Lucas: Exactly. And three months in, she said the legacy reporting never came back. The product strategy meetings gave her a seat at the table for two new product launches. And the mentorship budget paid for a coach who helped her understand the product lifecycle. She said her job satisfaction went from a 4 out of 10 to a 9. Luna: That's a huge swing. Lucas: Huge. And it wasn't because she changed companies. It wasn't because she got a big pay raise — she actually got a modest salary bump, maybe 8 percent. The transformation was in the work itself. She was doing more of what she was good at and less of what drained her. Luna: So the takeaway for anyone considering an internal transfer: before you accept, pause and ask yourself, 'What would make this role actually different from my current one?' And then have the conversation. Lucas: And not just about pay. Ask about the tasks you'll own, the meetings you'll attend, the decisions you'll influence. If you don't ask, the default is that you inherit whatever the previous person left behind. And chances are, they left behind some legacy reporting. Luna: Or three spreadsheets that nobody reads. Lucas: Right. So next time you're eyeing an internal move, I'd encourage you to treat the job description as a starting point, not a finished product. You have more leverage than you think. You're an insider. Use that. Luna: And maybe start building that relationship with the product strategy lead before you even know you'll need it. Lucas: Now that's a career move.