Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Owning a Failed Merger Integration
Transcript
- Lucas: So we are fifty episodes in on this show, and I want to mark it with something that actually flips the usual narrative on its head. Luna: I'm ready. What's the flip? Lucas: Almost every promotion story we've told so far is about someone who delivered a clear win. They built something, automated something, saved money, made the boss look good. Today's story is about someone who got promoted because she owned a failure. A big, public, expensive failure. Luna: Okay, that is a different energy. Who are we talking about? Lucas: Priya Mehta. She was a mid-level operations manager at a regional credit union in the Pacific Northwest. Not a household name, roughly three billion in assets. In 2024, her credit union acquired a smaller competitor — about eight hundred million — and the integration was a disaster. Luna: Define disaster. Lucas: Systems didn't sync. Customer accounts got duplicated, then frozen. People couldn't access their money for days. The call center was slammed, and the acquiring bank's culture clashed hard with the acquired one. Within six months, they'd lost about twelve percent of the acquired members and employee turnover among the acquired staff was over thirty percent. The board was furious. Luna: And Priya was the operations manager. So she was in the thick of it. Lucas: Exactly. She wasn't the integration lead — that was a senior VP who later left. But she was the person who had to actually make the systems work day to day. She saw every single breakdown firsthand. Luna: So what did she do that was different? Most people in her position would try to lay low, wait for the dust to settle, maybe update their resume quietly. Lucas: That's the natural instinct. Instead, she wrote a post-mortem. Not a sanitized version for the board — a brutally honest one. She documented every failure point: which systems weren't compatible, where communication broke down, which decisions were rushed. She named the root causes, not the people. Luna: That takes guts. Did she send it up the chain? Lucas: She did. She sent it to the CEO and the remaining executive team. And she didn't just hand them a problem report — she included a salvage plan. A phased approach to stabilize the systems, retain the remaining members, and rebuild trust with the acquired employees. Luna: And they went for it? Lucas: They made her the integration lead. The VP who had been overseeing it resigned, and the CEO basically said, 'You already understand this better than anyone. Go fix it.' She was promoted to VP of Operations six months later. Luna: So the lesson is: if you're in the middle of a mess, don't hide — document and propose. But isn't there a huge risk that you get blamed instead of rewarded? Lucas: There is. And that's the key distinction. Priya could have been blamed if she'd just pointed fingers. But she owned her part — she acknowledged that her team had missed some testing steps — and she framed the failure as a systems problem, not a people problem. Then she became the solution. Luna: That framing is everything. It's the difference between saying 'we failed' and 'I'll fix it.' Lucas: Exactly. And here's the concrete framework she used. She applied what I'd call the 'clean hands' rule: before you write the post-mortem, make sure you've acknowledged your own mistakes first. That disarms the defensiveness. Then you can talk about the broader systemic issues. Luna: So step one: own your piece. Step two: diagnose the system. Step three: hand them a fix. Lucas: Right. And step four — this is crucial — make sure the fix is within your scope to lead. Don't propose something that requires a whole new team or a budget you don't have. Priya's salvage plan was something she could run with her existing team plus a few temp contractors. Luna: And the CEO saw that as leadership. Not just identifying a problem, but showing you can execute the solution. Lucas: Yeah. And I think this is actually a more powerful career move than delivering a clean win. A clean win — you launch a dashboard, it works — people say 'nice job.' But when you turn around a disaster, people remember. It becomes part of your story. Luna: But not all failures are recoverable. How do you know if yours is the kind you can own? Lucas: Great question. I'd say there are three signs. One: the failure was caused by process breakdown, not ethics or legal violations. If someone broke the law or lied, owning it won't save you. Luna: Fair. Two? Lucas: Two: you have a clear path to fix it. You can't own a failure you don't know how to solve. Three: the organization still has appetite to invest in the fix. If the board is ready to kill the whole project, your post-mortem is just a eulogy. Luna: So in Priya's case, the credit union was committed to making the merger work because they'd already spent tens of millions. Lucas: Exactly. They had to fix it. And she positioned herself as the person who could do it. Luna: You know, I've been thinking about this as we talk. If this episode helps someone think through their own career situation, honestly, that's the whole point. We keep this show ad-free, and listener support is what makes that possible. Lucas: Yeah, it's a small thing, but it matters. If today's episode was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Luna: No pressure, really. Just if it resonates. And now back to Priya's story — because I think the most interesting part is what happened after the promotion. Lucas: Right. So she becomes VP of Operations, and she's now running the integration that she designed. Within a year, member retention stabilized, employee turnover dropped to pre-merger levels, and she built a reusable integration playbook that the credit union now uses for any future acquisition. Luna: So she essentially turned a crisis into a competitive advantage for the organization. Lucas: Exactly. And here's the detail that sealed her reputation: she made sure the acquired employees felt heard. She personally held listening sessions with every team from the acquired bank, and she implemented several of their suggestions — things like keeping their old payroll system for a transition period, which sounds small but was a huge morale win. Luna: That's the human side of owning a failure. It's not just about systems and processes. Lucas: Yeah. And it's why the CEO later told her that her willingness to own the mess and then include the acquired team in the fix was what convinced him she was VP material. Luna: I think there's a broader lesson here for anyone listening. You don't have to wait for a merger to go wrong. Every organization has visible failures — a product launch that flopped, a project that went over budget, a process that broke. The question is whether you're willing to step into that spotlight. Lucas: Right. And I'd add: the best time to write a post-mortem is when everyone else is still in shock or blame mode. If you can be the first person to calmly say 'here's what happened and here's how we fix it,' you stand out. Luna: What about the practical mechanics? How long should a post-mortem like Priya's be? Lucas: She told me hers was about three pages. One page on what happened and the root causes, one page on her own team's mistakes, and one page on the salvage plan. Short enough to be read, long enough to be thorough. Luna: And she sent it via email with a one-sentence subject line: 'Post-mortem and proposal for merger integration recovery.' Direct, no fluff. Lucas: Yeah. And she copied only the CEO and the two other executives who needed to see it. She didn't blast it to the whole leadership team. That showed discretion. Luna: I think that's an underrated piece of career advice: know who needs to see the bad news. Don't broadcast failure. Escalate it privately to the people who can act on it. Lucas: Exactly. And if they react badly — if they blame you or shut you down — that's also useful information. It tells you the culture doesn't reward accountability, and maybe it's time to leave. But more often than not, leaders respect someone who can stare down a failure. Luna: So let's wrap with a practical takeaway. For someone listening who might be in the middle of a messy project right now, what's the one thing they should do this week? Lucas: Write the three-page post-mortem. Even if you don't send it. Writing it forces you to clarify your thinking. Then decide if the organization is ready for it. But at the very least, you'll have a document that positions you as the person who understands the problem — and that's always career currency. Luna: And if you're not in a failure situation yet, file this away. Because at some point, something will go wrong. And when it does, you'll know what to do. Lucas: Yeah. Priya's story is a reminder that the fastest path to a promotion isn't always the cleanest one. Sometimes it's through the wreckage.