Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Owning a Failing Project
Transcript
- Lucas: There is a career move that sounds insane on paper but works more often than you would think: volunteering to take over a project that is already failing. Luna: Yeah, because on one hand you are inheriting a mess. On the other, nobody else wants it, so you have zero competition for visibility. Lucas: Exactly. And if you pull it off, you are not just the person who fixed a broken project — you are the person who walked into a burning building. That narrative carries weight in promotion conversations. Luna: So today we are talking about a specific case? Lucas: Yes — a mid-level marketing analyst at a large Fortune 500 retailer. Let us call her Priya. About eighteen months ago, her company launched a customer segmentation project. The goal was to use purchase data to create behavioral clusters for targeted email campaigns. Luna: Classic retail analytics project. How did it fail? Lucas: It missed every internal milestone for seven months. The original lead, a senior data scientist, had built a model that was technically elegant but operationally useless. It classified customers into thirty-seven segments, which the marketing team could not act on. So the project went into a holding pattern, and the lead left the company. Luna: And Priya was an analyst — not even a manager yet. Did she just walk into her VP's office and say 'I will take it'? Lucas: Pretty close. She scheduled a fifteen-minute conversation with the VP of marketing. But she did not go in complaining. She went in with a one-page document that had three sections: what she believed was wrong, what she thought the path to a fix looked like, and what she needed in terms of authority to make it happen. Luna: She framed it as a proposal, not a complaint. That is smart because the VP already knew the project was a problem. Lucas: Exactly. Priya's diagnosis was that the project had failed because it optimized for analytical completeness instead of marketing utility. Thirty-seven segments is too many. So her first step — once she got approval to lead — was to collapse the segmentation down to five clusters. She based that on interviews with the email marketing managers about what they could actually execute. Luna: So she started by understanding the user of the output, not the data. Lucas: Right. And then she built a transparent recovery plan. Every Monday for twelve weeks, she sent a one-paragraph email to the VP plus two directors. It had three bullet points: what we learned last week, what we are doing this week, and one request if they had feedback. No jargon, no excuses about the previous failure. Luna: That weekly discipline alone probably changed how senior leaders saw her. Most people hide when things are broken. Lucas: And the content of those emails mattered. She reframed every setback as a discovery. When a cluster turned out to be too broad, she wrote: 'We learned that high-frequency buyers in apparel behave completely differently from high-frequency buyers in home goods. We are splitting that cluster into two and adjusting the campaign templates accordingly.' She never said 'we made a mistake.' She said 'we learned something that changes the approach.' Luna: That is a language shift that anyone can adopt. It is honest but it signals forward motion. Lucas: By week nine, the new segmentation was live in a pilot with three email campaigns. Open rates went up twenty-three percent and click-through rates went up fourteen percent compared to the previous broadcast approach. That gave her hard numbers to point to. Luna: So the project was a success. But how did that turn into a promotion? Lucas: This is where it gets specific. Priya did not ask for a promotion immediately. She waited about six weeks after the pilot results came in. Then she scheduled a career conversation with her VP. But she started it with a question that flipped the dynamic. Luna: What was the question? Lucas: She asked: 'If you were in my shoes, what would you have done differently on the segmentation project?' The VP gave her genuine feedback — she should have involved the marketing managers earlier, she could have done a faster prototype. Priya took notes, thanked her, and then said: 'I agree. And I have been thinking about what I want to do next. Given what you just saw and what I learned, I would like to move into a role where I lead similar turnaround efforts.' Luna: She led with a request for feedback before making her ask. That is disarming. It shows confidence without arrogance. Lucas: And the VP did not say yes on the spot. But three weeks later, Priya was promoted to a director-level role. The official title was Director of Marketing Analytics, but the real job was 'fix our broken data projects.' The VP essentially created the role for her. Luna: It is a great story, but the risk is real. What if the project had stayed failing despite her best effort? Then she is associated with two failures instead of one. Lucas: That is the downside. Priya mitigated it two ways. First, she never claimed the original failure was her fault — she always said 'this project has had challenges.' Second, she set small milestones with visible checkpoints. By week four she had already shown that the new segmentation made sense to the marketing team. Even if the overall numbers had not improved, she would have had evidence that she moved the needle in the right direction. Luna: So she created a paper trail of progress regardless of the final outcome. That makes it harder for people to scapegoat you. Lucas: Exactly. And she also lined up informal sponsors before the formal ask. Two of the directors who received her weekly updates had already told the VP that Priya was doing great work. By the time she had the career conversation, the VP had heard positive signals from other people. Luna: That is a classic promotion play — but it is easier to execute when you are visibly running a visible project. And a failing project that you turn around is about as visible as it gets. Lucas: Right. And I think the lesson here is not 'go find a failing project.' The lesson is: if you see a project that is in trouble and you have a credible idea for how to fix it, raising your hand is a high-upside move. The downside is manageable if you structure the recovery the way Priya did — transparent, small wins, constant communication. Luna: I would add one caveat. Do not volunteer for a project that is failing because of politics or a toxic stakeholder. That is a trap. But if it is failing for technical or operational reasons, that is a problem you can solve. Lucas: Good filter. Priya also did a quick audit before she raised her hand. She talked to three people who had been on the project team — not to gossip, but to understand why it stalled. She concluded it was a methodology problem, not a people problem. That made the decision easier. Luna: And then she did the work. It sounds simple in retrospect, but the execution is the hard part. She had to rebuild the model, manage stakeholders, and communicate progress — all while doing her regular job, presumably. Lucas: She did. And that is another reason the promotion made sense for the company. She was already performing at the next level. The title just caught up. Luna: So if someone listening is sitting in a meeting next week and a senior leader says 'the XYZ project is behind schedule and we need someone to take it over,' what should they do? Lucas: Do not answer immediately. Say you need twenty-four hours to think about it. Then do the quick audit Luna mentioned. If the root cause is technical or operational, and you have a clear path to a fix, go back with a one-page proposal. If the root cause is political or the project is fundamentally unsound, politely decline. Luna: And if you do take it, remember Priya's playbook: diagnose without blaming, set weekly transparent check-ins, reframe setbacks as discoveries, and build sponsorship before you ask for the promotion. Lucas: One more thing — the question she opened the promotion conversation with. 'What would you have done differently?' That is worth memorizing. It shows you care about growth, and it invites the other person to coach you, which makes them invested in your success. Luna: That is a great note to end on. Next episode we will look at a different angle — how one employee got promoted by building a financial model that the CFO started using. That story involves a lot of late nights and a very nervous presentation to the executive team. Lucas: Looking forward to it. For now, if this episode made you think of a project at your own company that could use a reset, maybe that is your signal.