Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Solving a Senior Problem
Transcript
- Lucas: Priya Sharma had been an operations manager at a mid-size logistics firm for about three years. Solid performer, good track record, no complaints. But she was stuck. Her boss, the VP of operations, was a guy named Tom — competent, well-liked, but overloaded. Luna: Classic bottleneck. The VP is too busy to think strategically, and the manager below them is too junior to be heard. Lucas: Exactly. And in Priya's case, the thing Tom was ignoring was a vendor contract that had been auto-renewing for five years. It was for warehouse cleaning and maintenance — not glamorous, but it cost the company about $3.8 million a year. Priya noticed that the scope of work hadn't changed, but the price had crept up by roughly 8 percent annually. Luna: So she ran the numbers and realized they were overpaying by what — a couple hundred grand? Lucas: More. She calculated that the annual overspend was around $2.3 million, based on current market rates for comparable contracts in their region. Now, here's the thing: Tom knew the contract was stale, but he didn't want to deal with it. Renegotiations are messy, they involve legal, procurement, and the vendor was a long-time partner. It's the kind of problem that's easier to kick down the road. Luna: Right, and that's exactly the kind of problem that, if you solve it, gets you noticed. Because you're not doing your boss's job — you're doing your boss's boss's job. Lucas: That's the core of this episode. Priya's promotion to director didn't come because she did more of her existing work. It came because she identified a problem that senior leaders were actively avoiding, built a solution, and handed it to her VP as a done deal. She didn't ask for permission to look into it. She just did it. Luna: But that's risky, right? If you go behind your boss's back and start digging into something they haven't asked for, you could be seen as overstepping. Lucas: Absolutely. So the question is: how do you pick the right problem? Priya had two criteria. First, the problem had to be costly enough that solving it would be a clear win. Second, it had to be something her boss's boss — the COO — would care about. She knew the COO was under pressure to cut costs by 5 percent that year. Luna: So it aligned with a visible business priority. That's smart. But how did she even get access to the contract data without it looking suspicious? Lucas: She didn't have to go sneaking around. As an operations manager, she had access to the vendor management system. The contract was listed there. She just pulled it, did a benchmark against similar contracts using a public database, and built a one-page summary. She didn't need permission to look at existing records. Luna: Okay, so step one: find a problem that's costly, visible to senior leaders, and that you can access data on without raising red flags. Lucas: Right. Step two: build the solution before you ask for the assignment. Priya didn't just say 'hey Tom, we should renegotiate.' She came with a draft RFP, a list of three alternative vendors, a timeline, and a projected savings of at least $1.8 million in the first year. She basically de-risked the whole thing for him. Luna: That's a lot of work. How long did it take her? Lucas: About three weeks, working on the side. Maybe an hour a day. She also did something interesting: she informally checked with the heads of procurement and legal to see if they'd support a renegotiation. Got their verbal thumbs-up before she went to Tom. That's the third tactic — pre-selling the idea to the stakeholders your boss would need to convince anyway. Luna: So by the time Tom sees it, the path is already cleared. He can't say no because it's too easy to say yes. Lucas: Exactly. And that's what happened. Tom took it to the COO, the COO loved it, and within two months Priya was leading the renegotiation. The contract was re-signed at $2.5 million — a $1.3 million annual saving. Plus, she built relationships with legal, procurement, and finance along the way. Those people became her informal sponsors. Luna: If today was actually useful to you, the way these stay ad-free is listener support. You can buy me a coffee dot com slash fexingo. Just a thought. Lucas: Yeah, we keep it simple. No ads, no sponsors. And it's listeners like you who make that possible. Appreciate it. Luna: Alright, back to Priya. So she saves the company over a million dollars a year and gets promoted to director. But what about the people who don't have a $3.8 million contract to renegotiate? How do you find a senior problem worth solving? Lucas: That's the practical takeaway. Most mid-level professionals think they need a big, obvious issue. But the truth is, senior leaders are ignoring small problems that compound. Look for recurring pain points that have been kicked down the road for more than a year. That could be a manual reporting process that takes three people a week each month, a recurring customer complaint that's been accepted as normal, or an outdated policy that slows down decision-making. Luna: And you don't need to solve the whole thing. You just need to make it easier for your boss to say yes. Show them the cost of inaction, give them a plan, and line up the political support. Lucas: Right. Priya's story also shows something about timing. She didn't just pick any problem. She picked one that was on the COO's radar because of the cost-cutting initiative. So she tied her solution to a pre-existing strategic goal. That made it almost impossible to ignore. Luna: What if your company doesn't have a visible cost-cutting mandate? Is there another way to frame it? Lucas: Absolutely. You can frame it as risk reduction. Every organization has risks — compliance gaps, single points of failure in key processes, dependency on a risky vendor. If you can show how a problem could blow up if left unaddressed, that's just as compelling as saving money. In fact, sometimes more compelling, because senior leaders are often more afraid of a disaster than they are excited about an efficiency gain. Luna: So the formula: find a problem that is costly or risky, that your boss is avoiding, that you can access data on without overstepping, and that aligns with a known leadership priority. Then, build the solution quietly and pre-sell it to key stakeholders. Lucas: Exactly. And one more thing Priya did that I think is crucial: she framed the solution as something that made Tom look good. She said, 'Tom, I've done the legwork on this. You can present it to the COO as your initiative.' She gave him the credit. That's a big reason he was willing to champion her for the director role. Luna: So it's not just about solving a problem. It's about solving it in a way that makes your boss a hero. That builds trust and sponsorship. Lucas: Right. And that's the difference between getting noticed and getting promoted. Priya didn't just get visibility — she got a sponsor in Tom, who then advocated for her when the director slot opened up six months later. Luna: I think a lot of listeners might worry about stepping on toes. How do you know when it's safe to act without permission? Lucas: Good question. The rule of thumb is: if the problem is clearly within your area of expertise, you have access to the data, and you're not duplicating someone else's work, you're probably fine. Also, if the problem has been discussed in meetings but nobody has owned it, that's a green light. Priya had heard Tom complain about the vendor contract in a team meeting three months earlier. That was her cue. Luna: So the conversation already existed. She just picked up the ball. Lucas: Exactly. And if you're still unsure, you can always ask a gentle question: 'Tom, I noticed the vendor contract is up for renewal next quarter. Do you have any bandwidth to look at it, or would it be helpful if I pulled some benchmarks?' That way, you're offering help, not telling him what to do. Luna: But if he says no, you've tipped your hand. You might lose the element of surprise. Lucas: That's a risk. But if he says no, you also learn that he's not ready to solve that problem, and you move on to another one. The key is to have multiple potential problems in your back pocket. Priya had actually identified three. The vendor contract was just the one that had the most traction. Luna: So it's a portfolio approach. You don't bet everything on one problem. Lucas: Exactly. And the beauty of this strategy is that even if the specific problem doesn't lead to a promotion, the act of solving it builds your reputation as someone who thinks strategically. That reputation travels. Priya's COO later mentioned her in a company-wide town hall as someone who 'sees around corners.' That kind of recognition is gold. Luna: Alright, so for someone listening right now who wants to try this in the next 30 days, what's the first step? Lucas: Take 30 minutes to list the top three problems your boss or your boss's boss has complained about in the last quarter. Then, for each one, ask: do I have access to the data? Is there a clear cost or risk? Can I frame a solution in one page? Pick the one that scores highest on all three, and start digging. Luna: And don't tell anyone until you have a draft solution and informal buy-in from at least two stakeholders. Lucas: Yeah. Priya didn't loop in her VP until she had the RFP draft and the thumbs-up from legal and procurement. That's the power move. You present a solution, not a problem. Luna: One thing I want to circle back to — she got the director title, but her salary bump was reportedly around 25 percent. That's significant, but not outrageous. Did she negotiate? Lucas: She did. She came prepared with market data for director-level roles in her region. She also highlighted the $1.3 million saving as proof of her impact. She didn't get everything she asked for initially, but she ended up at the top of the band. That's a good reminder: solving a senior problem gets you in the room, but you still have to negotiate the terms. Luna: So the promotion isn't automatic. It's a door opener. You still have to walk through it. Lucas: Exactly. And that's the note I want to leave on. Priya's story is replicable. It's not about being a genius. It's about being observant, disciplined, and strategically generous with your boss's ego. Do that, and you'd be surprised how far it takes you. Luna: Good episode. Let's leave it there.