Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Recover From a Failed Project Without Losing Credibility
Transcript
- Lucas: So you just led a big project and it crashed. Not just missed a deadline — crashed. Now what? Luna: That's the moment most people go into hiding. And that's exactly the wrong move. Lucas: Right. Our instinct is to pull back, say as little as possible, hope it blows over. But in a knowledge-work environment, quiet after a failure is read as either clueless or guilty. Luna: There's actually a term for that. In organizational psychology, it's called the 'spiral of silence.' You stay quiet because you fear isolation, but that silence actually isolates you faster. Lucas: Exactly. So let's talk about a concrete case. I've been following a mid-sized SaaS company — we'll call them CloudSync — that launched a new integration product last year. It was meant to be their Q4 growth driver. Instead, it had a critical data migration bug that corrupted client records for two weeks. Luna: Ouch. That's the kind of failure that gets people fired. Lucas: It could have. But the product manager, a woman named Priya, handled it in a way that actually strengthened her reputation inside the company. She used a three-phase framework that I think is replicable. Luna: Okay, I'm listening. What's phase one? Lucas: Phase one is owning the failure publicly and specifically. Within 48 hours of the bug being confirmed, Priya sent a company-wide email — not just to her team, but to the entire engineering and customer success org. She described exactly what went wrong: a schema mismatch between the legacy data structure and the new pipeline that their QA process missed. Luna: That's brave. Most people would try to frame it as a team failure or blame the testing process. Lucas: She did take responsibility, but she also made it clear she had identified the root cause. That's key — owning it doesn't mean saying 'I have no idea what happened.' You own the outcome and show you understand the mechanism. Luna: So phase one is 'I own this, and here's why it happened.' Then what? Lucas: Phase two is what I'd call narrative reframing. Every failure produces learning — but you have to articulate that learning in a way that's useful to others. Priya wrote a postmortem document that she shared not just internally but — with some anonymization — on their engineering blog. She framed it as 'What We Learned From Our Biggest Data Migration Mistake.' Luna: That's smart. It turns the failure from a liability into a signal of rigor and transparency. Lucas: Right. And it does something else — it gives other teams permission to talk about their own failures. That builds a culture where you're seen as a leader, not a scapegoat. Luna: Okay, so phase one is ownership, phase two is reframing. What's phase three? Lucas: Phase three is rebuilding trust through small, visible wins. Priya didn't try to launch another big feature right away. She focused on three quick, low-risk fixes over the next month: a better error-handling message, a faster rollback procedure, and a one-page checklist for future integrations. Each one was a small victory that she communicated to stakeholders. Luna: So she used what you might call 'earned recovery.' You don't ask for trust back — you demonstrate it incrementally. Lucas: Exactly. And within three months, her team was actually seen as more reliable than before the failure, because they had proven they could handle a crisis and improve the system. Luna: It's counterintuitive. Failure, handled well, can be a career accelerant. Lucas: It really can. And look, this is one of those things where a small group of listeners already keeps this show going — a handful of people chip in monthly at buy me a coffee dot com slash fexingo, and that's what funds us making episodes like this without ads. So if this kind of deep-dive career content is useful to you, that's literally why that page exists. Luna: Yeah, and it's a way to keep this completely listener-supported. No sponsors, no agenda. Lucas: Anyway, back to the failure framework. The part that I think most people miss is that the recovery window is actually very short. Research from the Journal of Applied Psychology shows that colleagues form a stable impression of your competence within about three interactions after a visible failure. Luna: So you don't get weeks to sulk. You have to act fast. Lucas: Exactly. Priya's first email went out within 48 hours. Her postmortem was published within two weeks. The small wins started appearing within a month. She compressed the whole recovery cycle into a quarter. Luna: What about the emotional side? It's hard to project confidence when you feel like a failure. Lucas: It is. But here's the thing — you don't have to feel confident. You just have to act competent. The spiral of silence is driven by fear, but the antidote is structured action. If you have a plan — own, reframe, rebuild — you can execute even when you're anxious. Luna: That's almost a life skill, not just a career skill. Lucas: It is. And there's one more layer I want to add. The recovery isn't just about the project — it's about your network. After a failure, people gossip. The grapevine fills the void if you don't. So you need to proactively manage your narrative with key stakeholders: your boss, your skip-level, your cross-functional partners. Luna: So you're saying don't just send a company-wide email. Have one-on-one conversations. Lucas: Exactly. Priya scheduled 15-minute check-ins with each of her main stakeholder leads. She said, 'Here's what happened, here's what I'm doing about it, here's what I need from you.' That turned potential critics into collaborators. Luna: Because people are more forgiving when they feel looped in. Lucas: Right. The worst thing you can do is make people hear about the failure from someone else, or from the rumor mill. If you control the narrative, you control the interpretation. Luna: So let's say someone listening just had a project fail. What's the one takeaway? Lucas: Don't hide. Own it specifically, reframe it as learning, and then deliver three small wins fast. That sequence is proven to rebuild trust faster than any apology alone. Luna: And if your boss is the one who failed? Same framework? Lucas: That's a different episode, but the short answer is — you can't control their actions, but you can protect your own reputation by documenting lessons learned and being visibly helpful in the recovery. You want to be seen as part of the solution, not part of the problem. Luna: I think that's a good place to leave it. Failure is inevitable. How you recover is a choice. Lucas: And with a good framework, it's a choice that can actually advance your career.