Leadership

51 Failures and a Billion-Dollar Game

Kintsugi bowl with gold-filled cracks on a dark blue and black glaze, symbolizing strength and beauty found through breakage and repair.

“The season of failure is the best time for sowing the seeds of success.” —Paramahansa Yogananda

In today’s tech world, moving quickly and staying adaptable are critical. The teams that innovate fastest aren’t the ones that avoid failure—they’re the ones that learn from it. Rovio shipped 51 failed games before Angry Birds. Google’s Borg collapsed before becoming Kubernetes.

Create Safety for Smart Risks

Encourage a fault-tolerant climate that promotes innovation, because even failed ideas sharpen what comes next.

  • Stay Positive: Maintain a solutions-focused mindset to inspire your team. Encourage members to see challenges as opportunities to learn.

  • Support Your Team: Provide clear guidance and resources, creating a safe space for them to try new things and learn from wins and losses.

Put It Into Practice

  • Take Smart Risks: Promote taking calculated gambles to spark new ideas. Try a “fail fast, learn faster” approach—test ideas quickly and adjust before investing too much. It can lead to extraordinary breakthroughs.

  • Review Regularly: Hold retrospectives to review projects and identify actionable insights.

  • Keep Improving: Use agile methods for quick changes and improvements. Test ideas quickly with MVPs and refine them using feedback.

  • Talk Openly About Failure: Make it okay to discuss failures and what you learn from them. Doing so as a group helps everyone understand problems and collaborate more effectively on solutions.

  • Celebrate Learning: Recognize and reward team members who’ve learned from their mistakes.

  • Lead by Example: Show how to handle failure by sharing your experiences and staying positive.

Failure isn't the opposite of success—it’s often the path to it. Build the culture that knows the difference, and your team will surprise you.

Let’s talk about your platform challenge

If your organization is navigating scale under regulatory complexity—or making the shift from reactive delivery to resilient platform engineering—I’d welcome the conversation.

3. Nashville Skyline
1. Nashville Skyline
3. Nashville Skyline
1. Nashville Skyline
3. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline

Let’s talk about your platform challenge

If your organization is navigating scale under regulatory complexity—or making the shift from reactive delivery to resilient platform engineering—I’d welcome the conversation.

3. Nashville Skyline
3. Nashville Skyline
3. Nashville Skyline
3. Nashville Skyline
3. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline

Let’s talk about your platform challenge

If your organization is navigating scale under regulatory complexity—or making the shift from reactive delivery to resilient platform engineering—I’d welcome the conversation.

3. Nashville Skyline
1. Nashville Skyline
3. Nashville Skyline
1. Nashville Skyline
1. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline