Latest / The Founder's Journey with Fexingo: First-Time Entrepreneurs, Failures, and Lessons Learned / How Founders Build Resilience Through Controlled Failure
Transcript
- Lucas: There is a persistent myth in the startup world that resilience means never breaking. You see it everywhere: the founder who claims they slept on the office floor for six months without a single setback, or the pitch deck that glosses over every missed milestone as a 'learning opportunity.' But if you look at the actually durable companies building right now in October 2026, the pattern is different. They didn't avoid failure; they engineered it. Luna: Engineered? That sounds counterintuitive. Most founders I talk to are terrified of making a mistake that costs them their runway. Lucas: Exactly. And that fear is what makes them fragile. When you treat every error as a personal indictment, you stop taking risks. But when you treat failure as a data collection method, you start moving faster. Let’s take Slack as a classic case study here. It didn’t start as Slack. It started as a gaming company called Tiny Speck. Luna: Right, the game Glitch flopped. But did they really plan for that flop? Lucas: Not exactly planned, but they had the infrastructure to pivot quickly because they had already built a communication tool internally to run the game studio. The failure of the game exposed a better product. The key wasn't that the game failed; it was that the team had created a safe space to let the internal tool flourish even while the main project was bleeding cash. Luna: So the resilience came from decoupling the side project from the core failure? Lucas: Precisely. They allowed a 'controlled burn.' If they had poured all their resources into fixing Glitch until the very last second, they might have missed the signal that their chat tool was the real asset. Today, with interest rates stabilizing but capital still being cautious, founders can't afford to be all-in on one unproven idea without an exit ramp. Luna: That brings up the question of how do you define a 'safe' failure? Isn't there a line where a mistake becomes fatal? Lucas: Yes, and that line is usually defined by your burn rate versus your remaining cash. But the cultural line is more important. Basecamp, or 37signals as they were known, has always operated on what they call 'frictional innovation.' They encourage employees to spend twenty percent of their time on internal tools that solve immediate problems, not necessarily client-facing products. Luna: I remember reading about their 'hack weeks.' Is that similar? Lucas: It is. Hack weeks allow teams to build something completely new in a week. If it works great, you keep it. If it crashes and burns, you delete it. No harm, no foul. The cost was only a week of salary and server space. This creates a psychological safety net that allows people to be creative. Without that net, everyone plays it safe, and you end up with incremental improvements instead of breakthroughs. Luna: But doesn't that waste money? For a bootstrapped founder, a week of wasted salary feels like a lot. Lucas: It does, if you view it as waste. But think of it as insurance against bigger failures. A small, contained failure teaches you what doesn't work without killing the company. The alternative is betting everything on a big bet that fails, which is what happens when you don't test assumptions cheaply. Luna: So the goal is to fail small, often, and cheaply? Lucas: Yes. And part of that is having a process called the pre-mortem. Before you launch a major feature or pivot, you assume it has already failed catastrophically. Then you work backward to ask, 'What went wrong?' This forces the team to identify risks they were ignoring because of optimism bias. Luna: That seems like a powerful way to surface hidden dangers before they become public. Lucas: It is. It shifts the conversation from 'Will this work?' to 'How could this fail?' and then you build safeguards for those specific points. It turns anxiety into action. Most founders skip this because they want to sell the vision, not discuss the disaster scenarios. Luna: Why do they skip it? Isn't due diligence standard practice? Lucas: Due diligence is usually financial or legal. Pre-mortems are cultural. They require admitting vulnerability. Founders are often conditioned to be the confident leader, so asking the team to imagine failure feels like undermining morale. But in reality, it builds trust. It shows you are realistic, not delusional. Luna: That makes sense. Trust comes from honesty about risk, not from pretending there isn't any. Lucas: Exactly. And this connects back to investor relations too. Investors today are smarter. They know every startup has risks. If you can articulate your potential failure modes and your mitigation strategies, you look more credible than the founder who says 'everything will be perfect.' Luna: Do investors actually reward that kind of transparency? Lucas: Increasingly, yes. Especially after the dot-com bust and the pandemic disruptions, the market has matured. They are looking for operators who understand fragility. They want founders who have a plan B, C, and D, not just a hopeful narrative. Luna: So building resilience is partly about managing perception as much as actual operations. Lucas: Partly. But mostly it's about operations. Because if you haven't practiced failing small, you won't know how to handle a big crisis when it inevitably hits. Panic is the enemy of good decision-making. Routine exposure to minor setbacks keeps your reflexes sharp. Luna: Like an athlete training with weighted vests so the actual race feels easier. Lucas: Perfect analogy. You are conditioning your team to handle pressure. When a server goes down, or a key hire quits, or a competitor launches a copycat, your team doesn't freeze because they have seen smaller versions of these events before. Luna: This feels like a very practical framework. How would a solo founder implement this without a team to hack? Lucas: Even solo founders can run micro-experiments. Instead of building the whole platform, build a landing page and try to sell the service manually. If nobody buys it, you failed small. You saved months of coding time. That is a controlled failure. You learned that the market doesn't want it, or at least not in that form. Luna: And you didn't burn through your life savings doing it. Lucas: Correct. The biggest failure is spending two years building something no one wants. Anything less than that is just tuition. Reframing mistakes as tuition changes your emotional relationship with the business. Luna: It takes the shame out of it. Shame makes people hide mistakes, which is dangerous. Lucas: Shame is the killer of innovation. If you punish failure, people stop innovating. They start hiding data. They start lying to you. A resilient organization needs a 'no-blame' post-mortem culture where the focus is on system fixes, not person fixes. Luna: So the metric isn't whether we failed, but what we learned from the failure. Lucas: Exactly. Did our hypothesis change? Did our product improve? If yes, the failure was successful. It sounds paradoxical, but it is the only way to scale fast without collapsing. Luna: I love that. Success through failure. It feels like the ultimate startup mantra. Lucas: It is. And it requires discipline. You have to set the boundaries of the failure upfront. Know what the cost cap is. Know what the exit criteria are. Then let it happen. Luna: Boundaries are key. Uncontrolled failure is just chaos. Lucas: Chaos is inevitable. But controlled failure is a strategy. And that distinction separates the hobbyists from the professionals. Luna: One last thing on this — do you think this applies to non-tech businesses too? Like a restaurant or a retail shop? Lucas: Absolutely. A restaurant can test a new menu section for a month. If sales drop, they pull it. Small loss, big learning. They don't overhaul the entire kitchen overnight based on a hunch. That is controlled failure in action. Luna: So it is really just about iterative testing on a small scale. Lucas: It is. Stop trying to get it right the first time. Get it wrong quickly, learn, and get it right the next time. That is the engine of growth. Luna: Clear and actionable. I think many listeners need to hear that permission to fail small. Lucas: Permission is huge. Most founders are waiting for permission to be imperfect. Give it to yourself. Luna: Thanks, Lucas. That was a great perspective shift. Lucas: Before we go, I want to mention something real. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that is literally what funds making these conversations possible without ads interrupting your day. Luna: Yeah, it is just a small group keeping the lights on, and it helps us keep digging deeper into topics like this. Lucas: If that resonates with you, check it out. Otherwise, we will see you next time. Luna: See you later. Lucas: Where will your next controlled failure lead you?