recovering-from-failure

Diagnose product failures and guide pivots using frameworks from Lenny's Podcast and Newsletter.

1.3k|169|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/RefoundAI/lenny-skills --skill recovering-from-failure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recovering-from-failure
Source: https://github.com/RefoundAI/lenny-skills/tree/main/skills/recovering-from-failure
Command: npx skills add https://github.com/RefoundAI/lenny-skills --skill recovering-from-failure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product teams facing stalled growth, failed launches, or unclear product-market fit often lack a structured way to decide whether to persevere, pivot, or shut down. This Skill provides diagnostic frameworks and real-world pivot case studies to turn setbacks into strategic decisions.

Core Features & Use Cases

  • Failure Diagnosis: Apply frameworks like the Four Ps (persona, problem, promise, product) and root cause analysis to identify exactly why a product is not gaining traction.
  • Pivot Decision Frameworks: Use the Conviction Test, Two Types of Pivots, Five Patterns of Successful Pivots, and Seven Options When Your Product Isn't Taking Off to choose a path forward.
  • Turnaround Playbooks: Access templates like the Minus One to One Product Turnaround Strategy, Freemium-to-Paid Recovery Playbook, and Startup Failure Warning Signs Checklist.
  • Use Case: A founder with a plateauing B2B SaaS product asks whether to pivot. The Skill walks them through conviction assessment, retention signal analysis, and the four strategies for finding a better idea based on 40+ analyzed startup pivots.

Quick Start

Ask the AI to help you evaluate whether your struggling product should pivot, persevere, or shut down using the conviction test and pivot frameworks.

Frequently Asked Questions about recovering-from-failure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide whether to pivot or persevere with my startup?

Use Scott Belsky's Conviction Test: compare your current conviction in the problem and solution against your original conviction. If conviction has grown, persevere through the messy middle; if it has diminished, pivot or quit. The Skill also provides the Two Signs It's Time to Pivot framework based on retention data.

What frameworks help diagnose why a product is failing?

The Skill includes Todd Jackson's Four Ps framework (persona, problem, promise, product) to isolate the failing element, plus root cause analysis methods and the Startup Failure Warning Signs Checklist derived from real post-mortems like Cascade.

How do I find a good pivot idea for my startup?

Four strategies derived from 40+ analyzed pivots: go all-in on a feature showing organic pull, productize an internal tool, expand into an adjacent bigger market, or ideate internally via hackathons. Most successful pivots came from narrowing to what already works.

When is the right time to pivot a startup?

Data from 40+ pivots shows ideation pivots typically happen within 3 months of launch, while hard pivots with live products cluster around the one-year mark. The Skill provides timeline checkpoints at 3 months, 6 months, 1 year, and 2 years.

What are the warning signs that a startup is heading toward failure?

Key warning signs include persistent lukewarm interest with low retention, growth plateaus, reliance on founder-driven sales rather than inbound demand, ambiguous customer rejections, and running out of good ideas to drive growth.

How should I communicate a failed project to executives?

Use the five-step framework: get ahead of the news, highlight learnings, share the original context and hypothesis, present a clear recommendation for next steps, and separate your identity from the project's outcome.