Latest / The Internal Move Podcast with Fexingo: Lateral Roles, Internal Transfers, and Staying at Your Company / How an Internal Transfer Can Help You Escape a Dead-End Project
Transcript
- Lucas: You know that feeling when you're six months into a project and it's clear — crystal clear — that this thing is going nowhere? Luna: Oh, absolutely. The meetings get longer, the goals get fuzzier, and everyone's just waiting for the axe to fall. Lucas: Exactly. And if you're on that project, your career is basically treading water. So today I want to talk about one of the smartest moves you can make when you're on a dead-end project: an internal transfer to a team that's actually growing. Luna: I love this angle. Because a lot of people think they just have to ride it out or quit. But there's this middle path. Lucas: Right. And the key is recognizing the signs early. I'm not talking about a project that's just a little behind schedule — every project has that. I'm talking about the kind where the core assumption has been disproven, but leadership won't pull the plug. Luna: So what are the actual red flags? Lucas: First, the budget keeps getting cut but the scope doesn't change. Second, your skip-level manager stops asking about it. Third — and this one's brutal — people start self-demoting off the project. If you're the last one who hasn't found an exit, that's a signal. Luna: Yeah, I saw that at a previous company. There was this big data integration project. Everyone knew it was doomed when the VP stopped attending the weekly stand-up. Lucas: That's the moment. And if you're on that project, you have maybe two or three months before your reputation gets tarred by association. So you need to act. Luna: But how do you actually start the conversation about an internal transfer without looking like you're bailing on a sinking ship? Lucas: That's the art of it. You don't lead with 'the project is doomed.' You lead with 'I want to contribute to a high-growth area.' Frame it as a positive pull, not a negative push. Luna: So you're saying you need a narrative that's about your growth, not about the project's failure. Lucas: Exactly. Let me give you a concrete example. There was a marketing coordinator at a mid-sized tech firm — let's call her Priya. She was assigned to a product launch for a new analytics tool. Six months in, beta feedback was terrible, the product lead left, and the launch got delayed indefinitely. Luna: Classic dead-end. Lucas: Right. So Priya looked at where the company was actually seeing growth — and it was the customer retention team. They were launching a loyalty program that had strong executive sponsorship. She started going to their brown-bag lunches, she volunteered to help with a survey they needed, she built relationships on that team. Luna: So she was networking internally before she even asked for the transfer. Lucas: Exactly. When she finally talked to her manager, she said 'I've been learning a lot about retention marketing, and I think my skills could have more impact there. I'd love to explore a move that helps the company focus on our highest-growth initiative.' Her manager couldn't argue with that — it was framed as a business decision. Luna: And what about the manager's reaction? Some managers get defensive. Lucas: Some do. But if you've built enough goodwill and you're not the only person on the project, most managers would rather help you transfer than lose you entirely. Priya's manager actually agreed to a two-week cross-training period so she could transition smoothly. Luna: That's smart. It also protects the manager — they can say they facilitated a talent movement rather than lost a resource. Lucas: Right. And here's the thing — Priya's story has a happy ending. She moved to the retention team, the loyalty program was a success, and she got promoted within a year. Luna: But what about the people who stay on the dead-end project? What happens to them? Lucas: Usually one of two things. Either the project gets officially killed and everyone gets scattered to less desirable roles, or it limps along for another year and those people have a big gap on their resume where they didn't accomplish anything tangible. Luna: So the cost of staying is actually higher than the cost of moving, even with the awkwardness of the transfer conversation. Lucas: Much higher. And that's why I think timing is everything. The best time to transfer is when your project still has enough momentum that your departure isn't the thing that kills it. If you wait until it's obviously dead, you look like you're jumping off a corpse. Luna: So you want to transfer while the project is still breathing, but on life support. Lucas: Exactly. And you want to transfer to a team that has clear, measurable goals and executive visibility. Not just any open role — one that's tied to a priority the CEO talks about. Luna: How do you figure out which teams those are? I feel like sometimes the real growth areas aren't obvious from the org chart. Lucas: You're right. The org chart tells you reporting lines, not influence. So you have to do a little reconnaissance. Look at who gets called into the all-hands to present. Look at which teams are hiring even when there's a hiring freeze elsewhere. Look at where the best people are moving to internally. Luna: That's actually a great heuristic — follow the talent. If the top performers are all migrating to a certain team, that's a strong signal. Lucas: Absolutely. And one more thing — talk to your mentor or a trusted skip-level. They often have visibility into which projects are being prioritized in the next quarter. They can give you the inside scoop on where the company is really placing its bets. Luna: So let's say you've identified the right team. What's the actual mechanics of the transfer request? Do you go to your manager first, or the hiring manager? Lucas: Conventional wisdom says go to your manager first — and that's usually right. But if you have a really strained relationship or you know they'll block you, sometimes it's better to have a casual conversation with the hiring manager first, just to gauge interest. But tread carefully. If word gets back to your manager before you've told them, it can feel like a betrayal. Luna: So ideally, you want to build the relationship with the new team first, then have a transparent conversation with your manager. Lucas: Exactly. And be prepared for pushback. A good manager might ask 'What if the project turns around?' Or 'Can you wait three months?' You need to have a clear answer ready. Something like 'I've thought about it a lot, and I believe my skills are better suited to where the company is growing. I'd love to help with the transition so the project isn't hurt by my departure.' Luna: That's a respectful way to hold your ground without being confrontational. Lucas: Right. And sometimes the manager will surprise you. They might say 'I've been thinking the same thing — you'd be great over there.' I've seen that happen. Luna: That's the ideal scenario. But I think a lot of people are afraid to even start the conversation because they worry about looking disloyal. Lucas: That fear is real, but I'd argue that staying on a dead-end project is actually the less loyal move. You're essentially coasting, collecting a paycheck while the project burns. A proactive internal transfer shows you care about the company's success, not just your own comfort. Luna: That's a really reframe. It takes the selfish edge off and makes it about contribution. Lucas: Exactly. And that's the narrative you want to own. You're not escaping — you're re-deploying to where you can add the most value. Luna: It reminds me of something we talked about a while back — that internal transfers are actually a way to learn company blind spots. Knowing which projects are dead and which are alive is a kind of corporate intelligence. Lucas: Yeah, that episode was about institutional knowledge. And this is a practical application of that same insight. The people who navigate a dead-end project well are the ones who read the tea leaves early and act. Luna: So if someone is listening and they think they might be on a dead-end project right now, what's the first concrete step they should take today? Lucas: I'd say two things. First, objectively assess the project. Write down the last three milestones and whether they were met. Look at the budget and timeline trends. If more than half the milestones are missed and the budget is shrinking, that's a red flag. Second, start having informal conversations with people on teams that seem energetic and well-resourced. Ask them what they're working on. Just listen. Luna: And don't complain about your current project during those conversations, right? Keep it positive. Lucas: Absolutely. Never badmouth your current project. That just makes you look negative. Instead, say something like 'I'm really interested in what your team is doing — the customer retention work sounds exciting.' People want to work with someone who's enthusiastic. Luna: And that's a good lead-in to something I wanted to mention. If we've helped you think through a career move or decision like this one, we'd love for you to consider supporting the show. It's what keeps us ad-free and focused on the practical stuff. Lucas: Yeah, listener support really does make a difference. If you've gotten value from episodes on internal transfers or navigating office dynamics, you can help us keep going at buy me a coffee dot com slash fexingo. Luna: We really appreciate it. Now, back to the dead-end project — Lucas, you mentioned that timing is everything. What about the risk that you transfer and then the new project also turns out to be a dud? Lucas: That's a real risk. No move is a guarantee. But you can mitigate it by doing your homework. Look for projects that have already shipped something. Look for teams that have a clear roadmap for the next two quarters. Avoid projects that are still in 'exploration phase' with no deadline. Luna: So you want to see evidence of execution, not just PowerPoint slides. Lucas: Exactly. And one more thing — talk to people who've been on the team for a while. Ask them what a typical week looks like. If they can't describe it in concrete terms, that's a yellow flag. Luna: So the same detective work you'd do for an external job, you do internally. Lucas: Exactly. And the advantage is you have way more data. You can see who's on the team, you can check their track record, you can even look at their internal performance reviews if you're friendly with someone in HR. It's a much richer information environment than external hiring. Luna: That's a huge advantage. So if you're on a dead-end project, don't wallow — start scouting. Lucas: Yeah. And remember, every company has dead-end projects. It's not a reflection on you. What matters is what you do about it. The people who advance are the ones who recognize the situation early and make a move. Luna: So to sum up: recognize the signs, build relationships on growing teams, frame your move as a contribution, and execute before the project collapses. Lucas: That's the playbook. And one last thought — if you transfer successfully, you'll also build a reputation as someone who can read the business and make strategic decisions. That's a career asset that outlasts any single project. Luna: It's a good note to end on.