Latest / Executive Careers with Fexingo: VP, C-Suite, and Senior Leadership Career Strategy / How Senior Leaders Turn Career Stumbles Into Strategic Narrative
Transcript
- Lucas: There's a moment in every senior leader's career that they'd rather delete from the record. For one Fortune 500 COO I know, that moment was the ERP migration that cost the company roughly $150 million in lost productivity and write-offs. Luna: Ouch. That's the kind of story that usually gets buried in a confidentiality agreement. Lucas: Right. And the conventional advice — apologize, learn, move on — would have told him to never speak of it again. But he did something different. He turned that disaster into the centerpiece of his narrative when he went for a CEO role eighteen months later. Luna: How do you spin a $150 million mistake into a leadership strength without sounding like you're spinning? Lucas: That's exactly the question. And the answer isn't spin. It's something I think of as strategic narrative reframing. You take the raw event and you re-present it through three lenses: decision context, early-warning signals, and the systemic fix. Let me walk through each. Luna: Good. Start with decision context — because that's usually where leaders get defensive. Lucas: Exactly. Most senior leaders, when asked about a failure, jump straight to what they learned. But the listener — whether it's a board, a recruiter, or a CEO — needs to understand why the decision made sense at the time. In this COO's case, the company had grown through acquisition and was running seventeen different ERP instances. The board had been pushing for consolidation for two years. The vendor promised a twelve-month implementation. Everyone signed off. Luna: So you're saying he wasn't reckless — he was acting on a reasonable strategy with incomplete information. Lucas: Exactly. Decision context doesn't excuse the outcome. It just shows you had a defensible rationale based on the data you had. That's different from saying 'I had no choice.' The best narratives acknowledge the pressure points without shifting blame. Luna: Second lens: early-warning signals. I'd imagine this is where most people fumble. Lucas: They do. Because the instinct is to say 'We caught it early and course-corrected.' But if you caught it early, why did it still cost $150 million? The COO's version was more honest. He said: 'By month four, we saw integration testing failure rates above 40 percent. I should have paused the go-live timeline then. I didn't, because we were under board pressure to hit the year-end deadline. That was my mistake.' Luna: That's powerful because it shows self-awareness and accountability without self-flagellation. Lucas: And it's specific. A vague 'we saw some issues' wouldn't land. The 40 percent testing failure rate is a concrete detail that a board member can visualize. It signals that he was in the details, not just managing from PowerPoint. Luna: Third lens: the systemic fix. What did he actually change? Lucas: He implemented what he called a 'decision gate' process for all future IT projects over $10 million. Before any go-live, the project team has to present a risk dashboard to an independent committee — not the project sponsor — with mandatory stop or go criteria. He also created a post-mortem culture where teams publish 'lessons learned' documents without attribution. The ERP disaster became a case study that other divisions use. Luna: So he institutionalized the fix. That's the difference between 'I learned my lesson' and 'I made sure no one else has to learn it the hard way.' Lucas: Which is exactly the credibility marker boards look for. They want to know you can turn a scar into a system. And this is actually a good moment to mention something about how we keep this show ad-free. We deliberately don't run ads on Executive Careers — and that's possible because listeners who find value in these conversations sometimes choose to support the show. If that's you, the link is buy me a coffee dot com slash fexingo. No pressure at all. Now, back to the narrative framework — because there's one more piece I think is critical. Luna: Yeah, I was going to ask about the interview itself. How does this actually come up in a conversation? Lucas: Great question. The COO told me he prepares a two-minute version of the story that starts with the decision context, moves to the early-warning signal, lands on the systemic fix. He practices it until it sounds unrehearsed. And he never — I mean never — uses the phrase 'I learned a lot.' Luna: Really? That's the go-to line for most people. Lucas: It's a red flag to experienced interviewers. It's vague and it sounds like a deflection. Instead, he says something like: 'Here's what that experience taught me about governance. I now believe that any major implementation needs an independent risk review before the final go-ahead. I built that into our process.' You're not saying you learned — you're showing what you now do differently. Luna: That's a subtle but powerful shift. It moves from passive to active. From student to architect. Lucas: Exactly. And it works because it's concrete. Let me give you another example from a different industry. A friend of mine was a chief marketing officer at a consumer goods company. She launched a premium product line that flopped — $40 million in write-downs within two quarters. Luna: Oof. What was the decision context there? Lucas: The company had been losing share in the premium segment for three years. Competitors were taking margin. The board wanted a bold move. She commissioned consumer testing that showed 70 percent of target customers said they'd pay a 30 percent premium for the new features. But the testing didn't account for the fact that the economy was about to turn, and the launch coincided with a consumer spending slowdown. Luna: So the context was reasonable but the timing was unlucky. How did she frame the early-warning signals? Lucas: She said that eight weeks after launch, the reorder rate was less than half of what the model predicted. She could have pulled the product and cut losses, but she pushed for a second marketing spend because she believed the concept was still strong. That was the mistake. She admitted she was too attached to the idea to read the data objectively. Luna: That takes real vulnerability. Most CMOs would blame the economy. Lucas: And that's exactly why her narrative is stronger. She owns the attachment. Then she describes the systemic fix: she now requires that every product launch has a pre-defined 'kill threshold' — a metric that, if triggered, automatically triggers a review by a committee that doesn't include the product champion. She also changed the incentive structure so that pulling a failing product is rewarded, not penalized. Luna: I love that. It's a governance change, not just a personal resolution. And it signals to a board that she can design systems that protect the company from her own biases. Lucas: Exactly. And that's the core of the strategic narrative. You're not trying to make the failure look smaller. You're making yourself look bigger by showing you can extract a systemic lesson from it. Luna: Let me ask a practical question. For a listener who has a career stumble they've been trying to minimize or explain away — how do they start building this narrative? Lucas: First, identify the specific, numerical outcome. 'I was responsible for a project that went 40 percent over budget and missed the deadline by six months.' Not 'a project that had challenges.' Second, write down the decision context in two sentences. Third, identify one early-warning signal you missed or ignored, with a number if possible. Fourth, describe one systemic change you made as a result. Practice that four-sentence story out loud. Luna: And if they don't have a systemic fix yet — maybe the stumble was recent — what then? Lucas: Then you be honest that you're still working on it. But you should have a hypothesis. Say: 'I'm still analyzing what went wrong, but my initial hypothesis is that our risk assessment didn't account for supply chain volatility. I'm designing a new framework now.' That's still a narrative of agency, not victimhood. Luna: I like that. It shows you're a problem-solver even in real time. Lucas: One more thing. Never — in an interview or a board conversation — say 'it was a team failure' or 'we all made mistakes.' Even if true, it sounds like you're diffusing responsibility. Own your piece specifically, then talk about the team dynamic as context. Luna: So the formula is: own it, quantify it, explain the context, show the warning you missed, then describe the system you built. Lucas: That's it. And if you do that, the stumble becomes one of the most compelling parts of your career story. It shows you're human, you're honest, and you're the kind of leader who turns problems into processes. Luna: I think the takeaway is that senior leaders who try to hide or minimize their failures actually damage their credibility. The ones who lean in with a structured narrative build trust. Lucas: Exactly. And trust is the only currency that matters when you're interviewing for a CEO seat or a board position. The COO I mentioned at the top? He got the CEO role. And in his first board meeting, the chairman said, 'We hired you partly because of how you handled the ERP disaster. You didn't flinch.' Luna: That's the best endorsement you could get. And a good reminder that the narrative you build today might be what lands you your next role. Lucas: Alright, that's our show for today. Next week we're going to talk about how senior leaders use reference calls strategically — not just as a checkbox, but as a way to reinforce their narrative. Luna: Looking forward to it. Thanks for listening.