Making a New Product Last: Durability Checks Before and After Launch

Quick Overview

A product strategy question asking how a product manager would make sure a product that is about to launch lasts for years instead of fading after its debut. It tests validating demand before launch, reading retention and unit economics, building defensibility and setting checkpoints to scale, change course or stop.

Making a New Product Last: Durability Checks Before and After Launch

Company: Relevel

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are the product manager for a product that is close to launch. How would you make sure it is sustainable, meaning it keeps going for years instead of fading away after its debut? Explain what you would check or put in place before launch and afterward, and how you would know whether the product is on track to last. ```hint Count the ways it could die A launch can go well and the product can still fail within a few years. List the different reasons that happens, on the user side, the business side and the competitive side, and work backward from each to what you would verify and when. ``` ### Clarifying Questions - Is a specific product in mind, or should I choose one to make the answer concrete? - Is this a standalone business or a new feature inside an existing product that already has users and revenue? - What counts as surviving long term here: steady user retention, profitability, staying ahead of rivals, or continued funding from the company? - How far along is the product: an idea, a tested prototype, or ready to ship? ### What a Strong Answer Covers - A definition of long-term survival broken into separate conditions that must all hold. - Evidence gathered before launch that the need is real, recurring and worth paying for. - Launch metrics that show whether users return and whether each customer is profitable, rather than counting sign-ups. - A plan for defensibility and for keeping costs, team and dependencies under control as the product grows. - Checkpoints with pre-agreed criteria to scale, fix, change course or stop. ### Follow-up Questions - Three months after launch, sign-ups are strong but weekly retention keeps falling. What do you do? - How would your answer change if the product were a feature inside a large existing app rather than a standalone business? - What evidence would lead you to recommend shutting the product down, and how would you make that case?

Overview: A product strategy question asking how a product manager would make sure a product that is about to launch lasts for years instead of fading after its debut. It tests validating demand before launch, reading retention and unit economics, building defensibility and setting checkpoints to scale, change course or stop.

Relevel logo
Relevel
Nov 23, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are the product manager for a product that is close to launch. How would you make sure it is sustainable, meaning it keeps going for years instead of fading away after its debut?

Explain what you would check or put in place before launch and afterward, and how you would know whether the product is on track to last.

Clarifying Questions Guidance

  • Is a specific product in mind, or should I choose one to make the answer concrete?
  • Is this a standalone business or a new feature inside an existing product that already has users and revenue?
  • What counts as surviving long term here: steady user retention, profitability, staying ahead of rivals, or continued funding from the company?
  • How far along is the product: an idea, a tested prototype, or ready to ship?

What a Strong Answer Covers Guidance

  • A definition of long-term survival broken into separate conditions that must all hold.
  • Evidence gathered before launch that the need is real, recurring and worth paying for.
  • Launch metrics that show whether users return and whether each customer is profitable, rather than counting sign-ups.
  • A plan for defensibility and for keeping costs, team and dependencies under control as the product grows.
  • Checkpoints with pre-agreed criteria to scale, fix, change course or stop.

Follow-up Questions Guidance

  • Three months after launch, sign-ups are strong but weekly retention keeps falling. What do you do?
  • How would your answer change if the product were a feature inside a large existing app rather than a standalone business?
  • What evidence would lead you to recommend shutting the product down, and how would you make that case?