Strategy & Positioning 10 guests | 20 insights

Recovering From Failure

Turn product setbacks and stalled growth into strategic breakthroughs and pivots.

Includes our free 8-email course on making your product team AI-native. Unsubscribe anytime.

The Guide

5 key steps synthesized from 10 experts.

1

Conduct a brutal audit of market pull

Analyze retention data and talk to 5 to 10 potential customers to identify if you are solving a high pain problem. Look for persistent lukewarm interest where users sign up but never return. If growth depends on manual pushing rather than a self sustaining machine, you are likely on a melting island and need to change course immediately.

Featured guest perspectives
"My takeaway is that you should have a hard conversation with your co-founder around the three-month mark, and depending on how it’s going (see below), either re-commit or change the idea. Then schedule a yearly check-in. If things are clicking, full speed ahead. If things feel meh, at least spend a few days talking about other potential directions."
— Lenny Rachitsky
2

Diagnose the failure using the Four Ps

Evaluate your current persona, problem, promise, and product to isolate exactly which lever is failing to gain traction. Determine if the issue is a lack of differentiation or a workflow that is foreign to existing user habits. Use root cause analysis to simplify complex features that failed to meet their intended goals.

Featured guest perspectives
"You've got the persona, the problem, the promise, and the product. Lattice kept the first one but changed the others. Vanta changed all four."
— Todd Jackson
"And the product was fine, it worked, but it really wasn't differentiated. And in many ways, I think, again, I think I've had these reflections more sense than at the time, that I had some of the time, but why use this instead of Yahoo Yellow Pages? But more than anything else, why use this instead of the Yellow Pages? It was a digital version of something that had come before."
— Bret Taylor
3

Search for the hidden pivot idea

Look within your current product for a single feature or internal tool that shows strong organic traction or emotional reaction from users. Successful pivots often emerge from technical foundations that perform well even when the rest of the product fails. Evaluate if you can maintain the core problem while radically changing the delivery model to reduce adoption friction.

Featured guest perspectives
"Usually a successful pivot gets warmer instead of colder from what you're an expert at and somehow builds on what you learned on the prior idea. Right? And so in the case of Brex, it was they had worked on a FinTech company in Brazil when they were younger, and so I'm like, 'You need to work more on the thing all about and not the thing nothing about.'"
— Dalton Caldwell
"We started that as a B2C and then we realized that this is way harder than we think it is, and we ended up with converting that into B2B, which turns out to be very successful for us. And so occasionally there are companies that you start your journey with one perception and you change that and that will happen multiple times."
— Uri Levine
"That being said, the majority of pivots emerged from founders narrowing their focus to a single feature or piece of tech that was showing pull. A surprising number of successful pivots (over a fourth of this list!) came from finding pull for a piece of tech the team built for themselves while building their original, unrelated, business."
— Lenny Rachitsky
4

Reinvent the company stance and values

Transition to a wartime mindset to aggressively eliminate legacy projects and cultural bloat that hinder survival. Reframe the product purpose around a singular, high value user objective rather than internal business needs like traffic or upselling. Be prepared to scrap even stable technical foundations if they no longer serve as a platform for growth.

Featured guest perspectives
"I said, we need to become a wartime company. If we don't fight for this, we are dead. I jumped hard on AI, but I also restarted the culture. I rewrote the values designed to be a sharp knife to cut out the parts of the company that I just knew wouldn't be effective."
— Eoghan McCabe
"And then we realize because it's so new, it's just so unstable. It don't know where the bug come from. It's from your source code or from the underlying libraries? Then we have to restart the company, rebuild the whole thing."
— Ivan Zhao
5

Set a decisive timeline for the shift

Establish structured check ins at the three month and one year marks to evaluate if the new direction is generating pull. Execute pivots quickly to manage opportunity cost and maximize your shots on goal. If market pull remains elusive after several years of focused effort, acknowledge it honestly and consider returning capital or seeking a soft landing.

Featured guest perspectives
"My takeaway is that you should have a hard conversation with your co-founder around the three-month mark, and depending on how it’s going (see below), either re-commit or change the idea. Then schedule a yearly check-in. If things are clicking, full speed ahead. If things feel meh, at least spend a few days talking about other potential directions."
— Lenny Rachitsky
"~40% of startups pivoted at least once before landing on their winning idea—oftentimes more than once."
— Lenny Rachitsky

Get this guide as an AI skill for Claude Code

Includes our free 8-email course on making your product team AI-native. Unsubscribe anytime.

Install This Skill

Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.

Quick Install (Recommended)

Install this skill directly using npx:

npx skills add RefoundAI/lenny-skills --skill recovering-from-failure

Or install all 76 skills:

npx skills add RefoundAI/lenny-skills
View on GitHub →
Manual Installation
1

Download the skill

Download Skill (.zip)
2

Add to your project

Create a folder in your project root and add the skill file:

.claude/skills/recovering-from-failure/SKILL.md
3

Start using it

Claude will automatically detect and use the skill when relevant. You can also invoke it directly:

Help me with recovering from failure

Guest Perspectives

Deep dive into what 9 podcast guests shared about recovering from failure.

Bret Taylor 2 quotes
Listen to episode →
"They gave me another shot to do a V2 of it and I got the impression it wasn't like my last shot, but I certainly was feeling a little dejected from going from a hot shot, new PM to a new thing. So, we spent a lot of time thinking about how can you make something that's just much more compelling and not just a digital version of the Yellow Pages and not just so similar to some of the other products out there."
Tactical:
  • Analyze the fundamental reasons why a high-visibility product failed to differentiate from existing solutions.
  • Seek a 'second shot' by demonstrating a deep understanding of how to make the next version much more compelling.
  • Focus on creating a native experience that leverages the platform's strengths rather than just digitizing old habits.
"And the product was fine, it worked, but it really wasn't differentiated. And in many ways, I think, again, I think I've had these reflections more sense than at the time, that I had some of the time, but why use this instead of Yahoo Yellow Pages? But more than anything else, why use this instead of the Yellow Pages? It was a digital version of something that had come before."
Tactical:
  • Question the fundamental reason why a user would switch from their current status quo to your product.
  • Look for technical or product problems that stem from simply 'digitizing' old manual experiences.
  • Analyze whether your product is a 'me too' version of an incumbent or if it offers a truly unique value proposition.
View all skills from Bret Taylor →
Dalton Caldwell 1 quote
Listen to episode →
"Usually a successful pivot gets warmer instead of colder from what you're an expert at and somehow builds on what you learned on the prior idea. Right? And so in the case of Brex, it was they had worked on a FinTech company in Brazil when they were younger, and so I'm like, 'You need to work more on the thing all about and not the thing nothing about.'"
Tactical:
  • Look for 'warmer' ideas that build on what you already know rather than chasing unfamiliar trends.
  • Examine your existing internal tools and dashboards to see if they solve a problem for others.
  • Overcome psychological barriers or burnout to reconsider working in fields where you have deep expertise.
View all skills from Dalton Caldwell →
Eoghan McCabe 1 quote
Listen to episode →
"I said, we need to become a wartime company. If we don't fight for this, we are dead. I jumped hard on AI, but I also restarted the culture. I rewrote the values designed to be a sharp knife to cut out the parts of the company that I just knew wouldn't be effective."
Tactical:
  • Adopt a wartime company stance to prioritize survival and speed over legacy processes.
  • Rewrite company values to serve as a filter for cutting out ineffective parts of the organization.
  • Reallocate resources from plateauing legacy products to high-growth AI prototypes immediately.
View all skills from Eoghan McCabe →
Eric Ries 1 quote
Listen to episode →
"People act like having a startup fail is the worst thing that can happen to you. And man, that's not even in the top 10. It's bad, I've done it, it's awful. It's really bad, but far worse is to be in a company that won't die, a zombie, undead company that you hate, but you can't leave."
Tactical:
  • Define a pivot as a change in strategy that maintains absolute fidelity to your original vision.
  • Be willing to accept failure and shut down a project rather than remaining trapped in a company you hate.
  • Regularly evaluate whether your current strategy is becoming a maligned force in the world or something you feel complicit in.
View all skills from Eric Ries →
Ivan Zhao 1 quote
Listen to episode →
"And then we realize because it's so new, it's just so unstable. It don't know where the bug come from. It's from your source code or from the underlying libraries? Then we have to restart the company, rebuild the whole thing."
Tactical:
  • Identify early when a technical bet is creating more instability than value for the user.
  • Willingly throw away code and 'restart' if the current foundation prevents long-term scaling.
  • Pivot the product's primary direction if you discover users do not care about the original implementation.
View all skills from Ivan Zhao →
Scott Belsky 1 quote
Listen to episode →
"I basically say, 'How much conviction do you have in the solution you're building?' I know in the beginning, before you knew all you know now, you had tons of conviction. Now knowing all you know, do you have more or less conviction in the problem and the solution you're building?"
Tactical:
  • Evaluate if you would still start your company today knowing everything you now know about the market.
  • Pivot or quit immediately if your fundamental conviction in the problem has decreased over time.
  • Use conviction as your primary compass to navigate the 'messy middle' of entrepreneurship.
View all skills from Scott Belsky →
Todd Jackson 1 quote
Listen to episode →
"You've got the persona, the problem, the promise, and the product. Lattice kept the first one but changed the others. Vanta changed all four."
Tactical:
  • Use the 'Four Ps' framework to identify exactly which element of the business is failing to gain traction.
  • Determine if you should keep your core persona while completely reimagining the problem and product.
  • Be prepared to transform all four elements simultaneously if the current direction lacks market pull.
View all skills from Todd Jackson →
Uri Levine 1 quote
Listen to episode →
"We started that as a B2C and then we realized that this is way harder than we think it is, and we ended up with converting that into B2B, which turns out to be very successful for us. And so occasionally there are companies that you start your journey with one perception and you change that and that will happen multiple times."
Tactical:
  • Monitor if individual users are unwilling to take the manual actions required for success.
  • Evaluate if a B2B model can automate the solution and provide direct bottom-line value.
  • Be prepared to change your perception of the journey multiple times.
View all skills from Uri Levine →
Varun Mohan 1 quote
Listen to episode →
"Obviously that's a very big moment because that was a bet the company moment in the sense that we basically said, told our investors, 'Hey, we're making money on this.' We had already raised 28 million of capital and we were just like, 'Hey, we're just going to pivot entirely from this.' And we did that overnight."
Tactical:
  • Execute pivots overnight rather than stretching them across multiple quarters to maintain absolute focus.
  • Be prepared to abandon free cash flow positive projects if they no longer align with the largest market opportunity.
View all skills from Varun Mohan →