You didn't fail, your product did.
summary
Early-career work ships a timing-out feature that users hate, and a built-from-scratch Android app that only one customer uses; later products hit 10x year-on-year growth after switching to small MVE builds, heavy analytics, and rapid user testing. Validation tactic: query DB for Android web users and send a clickbait “can you help” email to recruit interviews. Core claim: separate personal success metrics from product KPIs so you didn't fail your product and avoid valuing shipping on time over genuine user impact.
AI-written summary · about
chapters (7)
- 0:00The shadow career
- 1:50Roots of success obsession
- 4:25Shipping on time
- 8:13Failing fast and early
- 12:37Emotional impact of failure
- 15:23Separating self from work
- 18:56Final advice on failing
related talks
59mSuccess On Your Own Terms
18mWhat I've learned from my career mistakes
31mProduct excellence and developer productivity fireside chat
23mFrom coding to building a company: My journey in starting a successful product...
01h 00m3 Key Questions For Products Teams To Answer
43mGrasping success from failure
26mA Software Developer's Guide to Launching Your Own Product
22mMaximising Your Odds of Success: Tips for Building Confidence in Your Game