Individual skill
recovering-from-failure
Help users navigate product failure by diagnosing root causes, evaluating conviction, and executing successful pivots or turnarounds based on proven industry frameworks.
skills/recovering-from-failure/SKILL.md
Source commit 13598cc54e09399bc1bc1398b0fca284110efb2f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,477
- Repository last updated
- Jul 16, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-assistant Repository topic
- claude Repository topic
- claude-code Repository topic
- lenny-rachitsky Repository topic
- llm Repository topic
- pm-tools Repository topic
- product-management Repository topic
- skills Repository topic
- product-skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,485 bytesreferences/artifacts.mddoc · 51,963 bytesreferences/guest-insights.mddoc · 29,036 bytes
Read excerpt
# Recovering From Failure
Turn product setbacks and stalled growth into strategic breakthroughs and pivots.
Help the user with recovering from failure using insights from 20 guests and posts across Lenny's Podcast and Newsletter.
## How to Help
1. **Diagnose the failure** - Use frameworks like the Four Ps or root cause analysis to identify exactly why the product or feature isn't gaining traction.
2. **Assess conviction** - Determine if the team still believes in the problem and solution after facing real world challenges or if it is time to move on.
3. **Identify the pivot path** - Look for organic pull within existing features or technical foundations to find a more viable direction.
4. **Execute with speed** - Move decisively to abandon failing initiatives and reallocate resources toward high conviction opportunities.
## Core Principles