Latest / The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org / How Stripe Fixed Engineering Trust Through Incident Transparency
Transcript
- Lucas: Let's talk about the moment every CTO dreads: the system goes down, payments stop processing, and the phone starts ringing off the hook. For a long time, the standard playbook was to stay silent, fix it in the dark, and hope nobody noticed. But look at what Stripe has done differently over the last few years. They didn't just build better redundancy; they built a culture where admitting failure publicly became a feature, not a bug. Luna: That sounds counterintuitive when you're trying to protect your stock price or your reputation. Why would you invite scrutiny? Lucas: Because opacity creates anxiety, and anxiety kills trust faster than any outage does. When Stripe publishes detailed post-mortems that explain exactly what went wrong, who made the call, and how they're preventing it next time, they're signaling maturity. It tells customers, 'We messed up, but we understand why, and we have it under control.' That’s a different kind of security than firewalls provide. Luna: So it's less about technical reliability and more about psychological safety for the client? Lucas: Exactly. Let's pause here for a second. If these conversations are useful for what you're building or running, remember that listener support keeps this show ad-free. You can find us on buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Thanks for keeping the lights on. So, back to Stripe. How do you actually operationalize that level of honesty without making engineers terrified to ship code? Lucas: They decouple blame from accountability. In many tech companies, if you break production, you get yelled at. At Stripe, the rule is bluntly stated: no one gets fired for breaking things, but everyone must fix them. The focus shifts entirely from 'who did it' to 'what failed in our process.' This removes the fear of reporting errors early, which means smaller issues get caught before they become massive outages. Luna: That requires a huge shift in mindset. Most leaders still treat errors as personal failures rather than system flaws. Lucas: It does. And it extends to the customer-facing side too. When an outage happens, Stripe doesn't just send a generic 'we're experiencing issues' email. They send updates that read like technical logs but are written for humans. They tell you what they've tried, what they've ruled out, and what the next update will be. It turns a passive waiting period into an active collaboration. Luna: I've seen that happen with other platforms where silence feels like denial. Does that level of detail ever backfire? Like, revealing too much technical debt? Lucas: It can, if you're not careful. But the key is that the details are always paired with a remediation plan. You don't just say, 'Our legacy database schema caused a lock contention.' You say, 'Our legacy database schema caused a lock contention, so we are implementing a sharding strategy by Q1.' The transparency is only valuable if it's anchored to action. Luna: So the narrative isn't just 'oops,' it's 'here's the fix.' That changes the whole dynamic. Lucas: Right. And it builds a feedback loop. Customers start reading those post-mortems because they learn something. They see how a sophisticated engineering team thinks. That educational aspect turns a negative event into a brand-building opportunity. It positions the company as an expert, not just a vendor. Luna: That’s a high bar though. Not every company has the bandwidth to write detailed technical narratives after every hiccup. Lucas: True. But even small teams can adopt the principle. You don't need a full blog post. A simple Slack channel update or a status page note that explains the root cause and the next step is enough. The consistency matters more than the volume. If you only communicate when everything is perfect, people assume you're hiding something when it isn't. Luna: What about the internal culture impact? Does constantly talking about failures make the team burn out? Lucas: Actually, it often reduces burnout. When failures are hidden, they linger as unspoken resentments or recurring glitches. When they're aired, discussed, and fixed, they're resolved. It clears the air. Engineers feel safer taking ownership because they know the system supports them. It stops being a game of hide and seek. Luna: So transparency acts as a pressure valve? Lucas: Precisely. It releases the tension before it builds up. And let's not forget the competitive advantage. In a market where AI tools and automated services are commoditizing basic functionality, trust becomes the primary differentiator. People pay for reliability, but they stay for integrity. Luna: Integrity is hard to scale though. How do you keep that culture consistent across hundreds of engineers? Lucas: You bake it into the onboarding process. From day one, new hires are taught that a post-mortem is a learning document, not a disciplinary record. They're encouraged to participate in reviews immediately. It becomes muscle memory. Over time, the default reaction to an error isn't panic; it's analysis. Luna: That's a long-term play. It takes years to build that kind of institutional habit. Lucas: It does. But the payoff is significant. Companies that master this don't just recover faster from outages; they innovate faster because their teams aren't paralyzed by fear. They ship bold features knowing that if something breaks, the system will catch it and learn from it. Luna: So the ultimate goal isn't zero downtime, it's zero shame? Lucas: Zero shame, yes. And maximum learning. Because once you remove the emotional weight of failure, you can tackle the technical complexity head-on. That's where real engineering excellence lives. Luna: It seems like the biggest hurdle is just getting leadership to stop viewing transparency as a liability. Lucas: That's the first step. Leaders have to model the behavior. If the CEO apologizes sincerely and details the fix, the rest of the organization follows. If leadership hides behind legal disclaimers, the engineers will too. Culture flows top-down. Luna: Do you see other companies adopting this, or is Stripe pretty unique in its execution? Lucas: Others are trying, but few match the depth. Some companies post apologies that feel scripted. Others share vague summaries. Stripe stands out because they dive into the technical weeds while keeping the language accessible. It shows respect for both the technical community and the general user base. Luna: Respect for the audience's intelligence. That's a refreshing approach. Lucas: It is. And it forces the company to be better. When you promise to explain everything, you have to understand everything. There's nowhere to hide your ignorance. Luna: So transparency enforces competence? Lucas: In a way, yes. It raises the floor. You can't fake deep understanding when you have to write it down and publish it. It compels rigorous thinking. Luna: That's a powerful incentive structure. Much stronger than just hitting uptime metrics. Lucas: Absolutely. Uptime is a lagging indicator. Trust is a leading indicator. Build the trust through honest communication, and the uptime numbers tend to follow as a result of the improved processes. Luna: So for CTOs listening, the takeaway is to start sharing your failures before they become disasters? Lucas: Start small. Share a minor issue. Explain the fix. See how your team and your customers react. You'll likely find that they appreciate the clarity. It opens the door to deeper engagement. Luna: And it makes the eventual big wins feel earned, not just lucky. Lucas: Exactly. Success is sweeter when you've been honest about the struggle to get there. It makes the journey shared, not solitary. Luna: I wonder if this approach works for non-technical products too. Can a marketing team use post-mortems? Lucas: The principle applies anywhere. If you launch a campaign that flops, analyzing why and sharing those insights builds credibility. It shows you're thoughtful and adaptive. It's universal leadership behavior, regardless of the domain. Luna: So it's really about intellectual honesty? Lucas: At its core, yes. Intellectual honesty builds authority. And in business, authority is currency. Luna: Interesting. I think most leaders underestimate how much power there is in just saying 'we don't know yet, but we're figuring it out.' Lucas: That phrase alone can defuse a lot of tension. It invites collaboration instead of confrontation. It turns enemies into partners. Luna: Partners in solving the problem. Lucas: Exactly. And that's the shift. From defending against criticism to inviting help. It changes the entire tone of the organization. Luna: It sounds like a lot of work upfront, but the return on investment in trust is massive. Lucas: It is. And in a world where skepticism is the default, being the company that tells the truth might be your strongest moat. Luna: A moat built on honesty. That's a compelling image. Lucas: It's not just an image. It's a strategy. One that pays dividends every time things go wrong, which, in tech, is inevitable. Luna: So the question isn't whether you'll fail, but how you'll talk about it when you do. Lucas: Precisely. How you handle the fall defines your rise.