Reducing Product Risk from Discovery Through Launch: A Product Manager's Approach

In a product manager interview you are asked how you would keep risk low while building a product. Describe the approach you would take from the first idea through launch: which kinds of risk you look for, how you would reduce each one, and how you would decide the product is ready for full investment and release. ```hint Not all risk is technical List the different ways a product can fail, from nobody wanting it to the business being unable to support it. Then ask which of those you could test cheaply before writing production code. ``` ### Clarifying Questions - Is this a new product with no customers yet, or a major feature added to a product that existing customers rely on? - Is the product sold to businesses with contracts and administrators, or used by consumers? - Which failure worries the company most: building something nobody adopts, missing a committed date, or breaking something customers depend on? - May I pick a concrete product to illustrate the approach? ### What a Strong Answer Covers - Distinct risk types (value, usability, feasibility, business viability, delivery and launch) rather than one generic notion of risk. - Identifying the riskiest assumptions and testing them with the cheapest convincing evidence first, with success and stop criteria agreed in advance. - Incremental delivery and controlled release: a thin first version, feature flags, staged rollout, monitoring and rollback. - Ownership and communication of risks across engineering, design, legal, sales and support. - Judgment about how much de-risking is worth it, given how reversible each decision is and the cost of moving slowly. ### Follow-up Questions - For a product with no users yet, which risk would you test first, and with what experiment? - Leadership has announced a fixed launch date tied to a big event. How do you keep risk under control without moving it? - How do you avoid de-risking so thoroughly that a competitor ships first?