Strategy question

What is the role of a Product Manager in decommissioning a product? What are the steps involved?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

Start a mock interview on this question · Mock interview from a job description

What this question tests

Understanding of the full product lifecycle, checking whether you know decommissioning is a deliberate, planned process, not just flipping a product off.

How to approach it

  1. Clarify scope: are we decommissioning a standalone product, or a feature within a larger product, since stakeholder impact differs.
  2. Identify the PM's core responsibilities: building the business case for sunset, communicating with stakeholders, and planning a migration path for affected users.
  3. Start with data: confirm the decision with usage, revenue, and cost-to-maintain data, since decommissioning should be evidence-based, not a guess.
  4. Plan the migration: identify what alternative product or feature existing users should move to, and build a transition plan, not just a shutdown date.
  5. Communicate on a timeline: give users advance notice, typically 60 to 90 days depending on complexity, with clear reasons and migration instructions.
  6. Execute in phases: stop new signups first, then support existing users through transition, then fully shut down, monitoring for unexpected dependencies throughout.

What a strong answer includes

Common mistakes

Likely follow-up questions

More strategy questions

Learn the skill behind it

Chapters of the AI PM course that teach what this question tests.

Preparing for a specific role?

Book summaries for this kind of question

Browse all 4,000+ questions in the bank