Product Risks

The four questions every product idea must answer before it is worth building: value (will people choose to use or buy it?), usability (can they figure out how to use it?), feasibility (can it actually be built with what we have?), and business viability (does it work for the business, across legal, finance, sales, and the rest?). Discovery exists to retire these risks cheaply.

Why it Matters

Teams default to worrying about feasibility, "can we build it?", because that is the engineer's question, and discover too late that the bigger risks were value and viability. Naming all four makes the dangerous, easy-to-skip ones explicit, and orders the work so the riskiest assumption is tested first rather than last.

Signals

• A plan that addresses only whether something can be built, not whether anyone wants it.
• Launches that work technically but no one adopts (value) or can use (usability).
• Features blocked at the end by legal, finance, or sales concerns no one raised (viability).

Benefits

A checklist that surfaces the risks people skip, a way to sequence experiments by which assumption would sink the idea, and a shared language across product, design, engineering, and the business.

Risks

Treating the four as a gate to pass once rather than risks to weigh continuously; over-testing low-risk ideas; assuming all four matter equally when one usually dominates.

Tensions

Thorough risk assessment slows the start, and the four pull on different specialists whose instincts conflict; the point is to test the one that would actually kill the idea, not to study all four exhaustively.

Examples

A feature that is easy to build but no one values; a technically sound product blocked late by a compliance constraint that a viability check would have caught early.