learning from product failure

Market timing can outweigh perfect execution.

pets.com executed well but failed because 80 % of the US was still on dial-up; Chewy later succeeded with the same idea in a broadband world.

Why: Even flawless product execution can’t overcome structural market constraints; recognize when the environment, not the product, is the bottleneck.

"probably can't make it work when 80% of the country... is still on dial-up"

Earn trust before imposing change.

Katie Dill arrived at Airbnb ready to overhaul the design org but was confronted by half the team reading grievances aloud; the core issue was she had not earned their trust first.

Why: People resist change when they don’t believe the leader cares about their interests; trust is the prerequisite for any meaningful transformation.

"the missing piece... is that I hadn't earned their trust"

Design experiments to fail conclusively.

Sri Batchu advocates maximizing the treatment effect—throw every possible lever at the hypothesis—so that if it still fails you can confidently move on.

Why: Inconclusive failures get retried endlessly by new executives; conclusive failures become institutional memory that prevents wasted cycles.

"failure is not that you didn't drive revenue. Failure is not learning"

Start with the user problem, not the competitive threat.

Airbnb Plus was conceived as a reaction to managed-marketplace competitors instead of focusing on the real user problem: uncertainty about listing quality.

Why: Solution-first thinking anchored to competitors leads to building capabilities outside the company’s strengths and poor unit economics.

"we were very solution first... and competitor afraid"

Celebrate and share failures to normalize risk-taking.

Intercom’s principle “ship fast, ship early, ship often” embeds the expectation that most bets will fail and that rapid learning is the goal.

Why: A culture that punishes failure incentivizes incrementalism; a culture that rewards learning enables bigger, higher-impact bets.

"we celebrate failure as long as you're learning"

Never green-light a full rewrite without exhaustive discovery.

Maggie Crowley’s team embarked on a six-month rewrite that ballooned to 2.5 years, never reached feature parity, and drained morale.

Why: Rewrites are seductive but hide unknown complexity; skipping rigorous discovery leads to sunk-cost traps and wasted years.

"don't do a rewrite... we skipped discovery... it took us forever to get to feature parity"

Fear-driven products rarely delight users.

Google Buzz and Google+ were motivated by competitive fear rather than genuine user needs, leading to privacy disasters and eventual shutdown.

Why: Products built to defend against competitors focus on parity instead of user delight, creating offerings no one asked for.

"a lot of the motivation... came from a place of fear, you know, it didn't come from a place of, let's make a great product for people"

Public failure is survivable and often career-accelerating.

Paul Adams froze on stage at Cannes, walked off, cursed on live mic, yet leveraged the infamy to build deeper connections and continued career growth.

Why: Most people over-weight the downside of public failure; the recovery story often increases credibility and human relatability.

"I was famous that night... you can turn it around"