Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Ask for a Career Pivot Without Starting Over
Transcript
- Lucas: Alright, let's start with a listener question. Priya writes in: 'I'm a senior supply chain analyst at a mid-size manufacturing company. I've been doing this for eight years. I want to move into product management, but every product job posting I see wants prior product experience. I feel like I'd have to start over as an associate and take a massive pay cut. How do I pivot without losing all my seniority?' Luna: Oof. That 'start over' fear is real. I hear it from friends all the time — they look at a job description, see '3–5 years of product management experience,' and just close the tab. Lucas: Exactly. And the instinct is to focus on what you don't have. But I want to reframe this using something I call the 'adjacent skills' framework. The idea is pretty simple: most careers aren't islands. They share a continental shelf with other roles. Supply chain and product management — they're much closer than they look on paper. Luna: Okay, sell me on that. What's the overlap? Because on the surface, one is about logistics and inventory, the other is about features and roadmaps. Lucas: Right, but think about what a supply chain analyst actually does day-to-day. You're forecasting demand, you're managing cross-functional teams — procurement, warehousing, transportation — you're making trade-offs between cost and speed, you're using data to make decisions, and you're constantly communicating with stakeholders about timelines and constraints. Luna: So you're basically saying that's the same muscle as a product manager? Prioritizing features, managing engineers and design, balancing scope against deadlines? Lucas: It's not identical, but it's remarkably similar. A friend of mine — let's call him Marco — made this exact move three years ago. He was a logistics manager at a B2B software company that did hardware fulfillment. He wanted to go into product. He didn't quit. He found one project: the company was building a new inventory forecasting tool, and he volunteered to be the 'business stakeholder' on the product team. Luna: So he basically did product work on the side while keeping his logistics job. Lucas: Exactly. For six months, he attended the product stand-ups, wrote user stories for the procurement side, helped with user acceptance testing. By the end, he had a concrete case study he could point to. When a product associate role opened up, he applied internally and the product director already knew he could do the work. He didn't start as an associate — they gave him a 'product manager' title with a six-month ramp-up period. Luna: That's the bridge title idea — a way to move laterally without resetting your level. Did he take a pay cut? Lucas: No, and that's the important part. His base stayed the same. The company adjusted his bonus structure to align with product metrics instead of supply chain metrics. So his total comp actually went up slightly in year two. But the key was that internal transfer — he didn't have to walk into a new company and negotiate from scratch. Luna: So for Priya, the first step is to find a project at her current company where she can start doing product-adjacent work, even informally. Lucas: Yes, and I'd go a step further. I'd recommend she identify a specific problem the product team is grappling with — something that intersects with supply chain. Maybe the product team is trying to improve the customer experience around order tracking, or they're building a feature that depends on inventory data. She can approach the product manager and say, 'I've been thinking about how we handle X. I'd love to help map out the requirements from the operations side.' Luna: That's a lot less intimidating than applying for a job cold. And it gives her evidence for the conversation with her own manager. Lucas: Right. Once she's done that project — even a small one — she has a concrete example of product thinking. She can then ask her manager for a 'stretch assignment' that's closer to product work. At many companies, you can negotiate a 'transition period' where you split your time — say, 60 percent supply chain, 40 percent product — for a quarter. That's the bridge. Luna: But what if her company doesn't have a product team? Or what if they're not open to internal moves? Some managers get territorial. Lucas: That's a real risk. In that case, she needs to build the evidence externally. She could do a side project — maybe a fake product launch for a hypothetical feature, documented on a personal blog or a public Notion page. Or she could take a certification course like a product management certificate from a reputable university, but not just for the credential — she should use it to build a portfolio. One concrete example: she could analyze a product she uses and write a one-page product critique with suggested improvements. Luna: I like that because it shows initiative without requiring permission from her current boss. Lucas: Exactly. And when she applies externally, she can frame her eight years of supply chain experience as a superpower, not a limitation. She can say, 'I understand the operational reality that your product decisions will affect. I've managed complex logistics and I know how to work with ambiguity. Here's how that translates to product management.' The hiring manager who's been burned by a product manager who didn't understand the supply chain will see that as a huge asset. Luna: So the core message to Priya is: you don't have to start over. You have to reframe and build a bridge. Pick one project, do it well, and use that to negotiate your way into the role. Lucas: Exactly. And I'd add one more tactical piece: when she goes for the conversation with her manager or a hiring manager, she should prepare a 'skills translation' document. A two-column table: on the left, the product management requirement from the job description. On the right, her exact supply chain experience that maps to it. That makes it impossible for them to say she doesn't have the skills. Luna: That's a concrete tool. Listeners, if you're in a similar spot, start that document today. And if you've gotten value from this episode — maybe it helped you think through a career move — consider supporting the show. A couple of dollars a month is genuinely what keeps these going. You can find us at buy me a coffee dot com slash fexingo. Every bit helps us stay ad-free and focused on questions like Priya's. Lucas: Yeah, and we read every message we get from supporters. It's a small community, but it's a real one. Alright, back to Priya's pivot: one thing I want to emphasize is timing. She shouldn't wait until she's burnt out on supply chain to start building the bridge. Start now, even if it's just an hour a week reading product management blogs or listening to a product podcast. The goal is to build momentum before you feel stuck. Luna: That's a good place to leave it. Priya, we'd love to hear how it goes. And to everyone else, send us your questions. We'll tackle them on a future episode. Lucas: Thanks for listening. See you next time.