Product Post-Mortem: Diagnose Why a High-Potential Product Flopped

Name a product that seemed to have everything it needed to succeed and still failed, and explain why it failed. The choice of product is yours. Walk the interviewer through what made its prospects look strong, what went wrong, and which causes mattered most. ```hint Causes, not symptoms Low sign-ups or a shutdown are what happened, not why. Identify the assumption about users, the market, the timing or the business model that proved false, and separate that main cause from the factors that only made things worse. ``` ### Clarifying Questions - Does the product have to be one I worked on, or can it be any well-known product, including one from Google? - What counts as failure here: a shutdown, missing its own goals, or never reaching the scale its potential suggested? - Should the answer stop at diagnosing the failure, or also cover what the team could have done differently? ### What a Strong Answer Covers - A recognizable example with a convincing case that its potential was real, and a clear statement of how it failed - Root causes traced across user value, product decisions, go-to-market, timing and economics, with the primary cause separated from contributing ones - Claims grounded in what is publicly known rather than hindsight guesses presented as fact - A concrete decision or alternative path that might have changed the outcome - A transferable lesson for how the candidate would build or launch products ### Follow-up Questions - If you had been the PM a year before launch, which single decision would you change, and how would you have tested it first? - Which of these causes could the team have fixed after launch, and which doomed the product from the start? - Name a product that succeeded in the same space. What did it do differently?