The Failure Postmortem

In November 2019, Tesla threw a steel ball at a window on stage — and the window shattered. It became the most-replayed product demo fail of the decade. This episode walks through what the Cybertruck team expected, the signals they missed, the exec call that doubled down anyway, and what the hardware world quietly learned from the wreckage.

In 2016, Juicero raised $120 million to build a WiFi-connected cold-press juicer and sell it for $400. Sixteen months later, Bloomberg reporters squeezed the juice packs by hand and got the same result. This is the story of how a product with real ambition became the symbol of Silicon Valley at its most disconnected — and what founders and PMs have quietly learned from it since.

In 2011, Google launched Google+ with genuine conviction — and the full weight of its engineering muscle behind it. By 2019 it was gone. This episode walks through what Google expected, what the data kept showing them, why the org chart overrode the users, and which lessons actually stuck.

In April 2020, Quibi launched with $1.75 billion, Hollywood's biggest names, and a bold bet that people would watch premium short-form video on their phones during commutes. Six months later, it was gone. This episode walks through what the team expected, the failure signals that were hiding in plain sight, the exec calls that kept doubling down anyway, and what later products actually learned from the wreckage.

In March 1995, Microsoft shipped Bob — a cartoon-room shell designed to make the home PC approachable for first-time users. It was gone within a year. This episode works through four beats: what the team expected and why, what failure signals were already visible before launch, where executive calls diverged from the data, and which lessons from Bob's failure actually stuck — in Clippy, Windows 95, and the iPhone home screen.

In April 1985, Coca-Cola voluntarily retired the best-selling soft drink in America. The research was solid. The sample size was enormous. The decision was catastrophic. This episode traces all four beats: what the team expected and why, what signals were already visible in the research files, where the exec call diverged from the available evidence, and which lessons from those 79 days became foundational in product strategy.