Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How a Quiet Employee Landed a Global Role Without Applying
Transcript
- Lucas: So there's this story out of a mid-sized European industrial firm — I won't name them, but think precision components, not household name — where a supply chain analyst, maybe four years in, ends up being offered a global role without ever applying for it. Luna: Without applying? That's the kind of thing people assume happens to someone else. Lucas: Right. And it wasn't luck. It came down to three specific moves she made over about six months. And the interesting thing is, none of them involved asking for a promotion. Luna: Okay, I'm already curious. What was the first move? Lucas: She found what I'd call an 'orphan problem.' Something that fell between two departments — in her case, a recurring mismatch between production forecasts and raw material orders that caused a build-up of slow-moving inventory. It was costing the company roughly two million euros a year in carrying costs, but nobody owned it. Procurement blamed production, production blamed sales. Luna: And she just started working on it? Even though it wasn't her job? Lucas: Yeah, exactly. She spent maybe four hours a week for a month pulling data and finding the pattern. She didn't ask permission. She just documented the gap and built a simple spreadsheet model showing that if you adjusted the ordering trigger point by two weeks, you could reduce that inventory by about 18 percent. Luna: So she found the problem, quantified it, and had a solution. But that alone doesn't get you a global role. Lucas: No, and here's the second move — she made it visible to the right people. She didn't blast it to everyone. She sent a one-page summary to the head of supply chain, copied the regional VP, and said, 'I noticed this pattern. Here's the data. I think I can fix it if I get a little time to test it.' Luna: That's smart — framing it as an offer, not a complaint. Lucas: Exactly. And the third move — this is the one most people miss — she made it repeatable. She built a simple three-step process that anyone in the forecasting team could follow. So it wasn't just her solving a one-time problem. She created a system. Luna: And that's what turned it into a promotion-worthy story. Lucas: The VP noticed, asked her to present to the operations leadership team, and within two months they created a new global role — supply chain coordination lead — and offered it to her. She never applied. The role was designed around her. Luna: So the lesson isn't just 'be visible.' It's 'solve something visible that scales.' Lucas: And that's a very different strategy from raising your hand for every task force or sending your boss monthly status updates. It's about finding the gap that costs the business real money and owning it long enough to prove it's fixable. Luna: I think a lot of people miss that because they're focused on doing their job well, not on finding the thing that nobody's doing. Lucas: Yeah, and that's the trap. Doing your job well gets you a good performance review. Finding the orphan problem gets you a new job. Luna: It also helps that this analyst was in supply chain — a function where numbers speak loudly. But what if you're in a softer role, like marketing or HR? Lucas: The same principle applies, but the orphan problem looks different. In marketing, maybe it's the gap between the content calendar and sales enablement. In HR, maybe it's the turnover data nobody's correlated with manager training. The common thread is: find a measurable pain point that crosses departmental lines, and build a repeatable fix. Luna: I want to go back to the visibility piece, because I think a lot of people worry that sending that one-pager feels like self-promotion. Lucas: It can feel that way. But the framing matters. She didn't say 'look what I did.' She said 'look what I noticed.' That's different. It's curious, not boastful. Luna: And she offered to help fix it, she didn't demand credit. Lucas: Exactly. And the VP later said that what impressed him wasn't just the analysis — it was the initiative. The fact that she saw a problem, did the work on her own time, and came with a solution. That's rare. Luna: It's also worth saying — this isn't about working 60-hour weeks. She spent maybe four hours a week on this for a month. That's 16 hours total. Lucas: Right. It's about leverage, not hours. And that's a great place to pause and mention something — if this kind of career thinking has helped you, or if you've used a similar approach yourself, a handful of listeners chip in monthly at buy me a coffee dot com slash fexingo. That's what keeps this show ad-free and focused on practical stories. Luna: Yeah, it's a small group, but it makes a real difference in how much time we can spend finding these cases. Lucas: Exactly. And back to the orphan problem idea — once you find one, the next step is making sure your solution is visible to the person two levels up, not just your direct boss. Luna: Because your boss might be too close to it, or too protective of their turf. Lucas: Or they might not see the strategic value. The VP in this story was at a level where inventory carrying costs mattered to their bonus. The direct boss was more concerned with daily order accuracy. Different incentives. Luna: So you need to solve for the person whose pain is biggest. Lucas: Exactly. And if you frame it as saving the company money or time, you're speaking their language. Luna: What about the risk that someone else takes credit? Or that you're seen as stepping on toes? Lucas: That's real. But the way to mitigate it is to loop in the people whose toes you might step on early. She went to the procurement lead and said, 'I noticed this pattern in your data — do you have time to look at it with me?' That made them a collaborator, not a bypassed party. Luna: So it's about building allies, not burning bridges. Lucas: Right. And if someone does try to take credit, typically the sponsor who saw your work already knows where it came from. That's why the one-pager with your name on it matters. Luna: I think a lot of people also struggle with the idea of 'repeatable process.' They solve a problem and move on. But the promotion comes when you codify it. Lucas: Yeah, because that's the difference between a firefighter and a system-builder. Firefighters are valuable, but they're not promoted to run the department. System-builders are. Luna: So if someone wants to apply this tomorrow, what's the first step? Lucas: Spend one hour this week looking at your team's recurring headaches. Ask yourself: what problem shows up every quarter that nobody has permanently fixed? Write it down. Then ask: who else feels this pain? That's your orphan problem candidate. Luna: And if you don't see any? Or your company is very siloed? Lucas: Silos create orphan problems. They're full of gaps. Look at the handoffs between departments — that's where things fall through. In a siloed company, the orphan problems are actually bigger because nobody talks to each other. Luna: That's a good point. The analyst's problem was literally a handoff between procurement and production. Lucas: Exactly. And the beauty of it is, once you solve one, people start coming to you with others. You become the person who fixes the things that don't fit anywhere. That's a career-defining reputation. Luna: I'd add one thing: document it. Even if you don't send the one-pager right away, having a clear summary with numbers makes you ready when the opportunity to share appears. Lucas: 100 percent. And I think the timing right now, late May 2026, is actually quite good for this. A lot of companies are rethinking their talent pipelines after two years of restructuring. Leaders are looking for people who can step into ambiguity. Luna: So the window is open. Lucas: It is. And you don't need to apply for a job to walk through it. You just need to find the problem that's waiting for someone to own it.