Builders Camp

Glossary

What Is the Five Risks Assessment Framework

The Five Risks Assessment evaluates a product idea across desirability, viability, feasibility, usability, and ethical risk before committing real engineering time. It extends Marty Cagan's widely used four product risks by adding an explicit ethical risk axis.

What does the Five Risks Assessment mean?

The Five Risks Assessment is a discovery tool that checks a product idea against five categories of risk before it gets built: desirability, whether customers actually want it; viability, whether the business can sustain it; feasibility, whether it can actually be built with available time and skill; usability, whether users can figure out how to use it; and ethical risk, whether it could cause harm even if the first four risks check out. The framework extends the four big risks Marty Cagan describes through the Silicon Valley Product Group, which name value, usability, feasibility, and business viability as the risks every product idea has to survive, attacked cheaply during discovery, before anyone writes production code. Skipping the ethical check does not remove the risk; it just defers discovering it until the cost of fixing it is much higher.

Why the Five Risks Assessment matters for product managers

Builders Camp's own template library curates the Five Risks Assessment as a quick tool to evaluate desirability, viability, feasibility, usability, and ethical risks, explicitly building the ethical dimension into a discovery practice that many teams otherwise treat as an afterthought handled only after launch. That addition matters specifically for AI-adjacent and data-driven products, where a feature can be desirable, viable, feasible, and usable, and still cause real harm to a specific group of users, the exact failure mode Builders Camp's AI Product Management practical challenge builds its bias-incident scenario around. Checking for that risk during discovery, before a single model is trained on production data, is far cheaper than discovering it after a real customer is affected.

Five Risks Assessment example

A team prototyping an AI feature that auto-flags risky loan applications checks all five risks before building it out: customers want faster decisions, the business saves real underwriting time, engineering can build it with existing models, early usability tests go well, but the ethical risk check surfaces that the training data underrepresents certain applicant groups. Builders Camp's approach treats that finding the same way it treats a failed usability test, as a real blocker to resolve before shipping, not a compliance footnote. Feeding that same finding into an assumption matrix helps the team decide which fix to test first, rather than pausing the whole feature indefinitely or shipping it with a known gap unaddressed.

How Builders Camp teaches the Five Risks Assessment

Product Strategy, a 2 week bootcamp with 4 live sessions and 8 microlessons taught by Andre Albuquerque, curates the Five Risks Assessment template in its resource library as a companion to its opportunity discovery material. Prototyping for Product Managers covers the cheap, fast testing methods used to check each risk before a full build. See the Product Strategy bootcamp for the full curriculum.

Bootcamps referred in this Guide

Frequently asked questions

What are Marty Cagan's original four risks?

Cagan's four risks, described through the Silicon Valley Product Group, are value risk, whether customers will choose it; usability risk, whether users can figure out how to use it; feasibility risk, whether it can be built; and business viability risk, whether the rest of the business can support it.

What does the fifth, ethical risk add to the framework?

Ethical risk checks whether a product could cause harm, through bias, privacy exposure, or manipulation, even when it clearly passes the other four risks, which matters increasingly for AI-driven and data-heavy features.

When should the Five Risks Assessment happen?

It should happen during discovery, before significant engineering investment, since the whole point of the framework is testing risks cheaply with prototypes rather than discovering them after a feature has already shipped.

Who should be involved in a Five Risks Assessment?

A cross-functional group works best, since desirability and ethical risk often need input from research and legal or trust and safety perspectives that a product or engineering lead alone might not catch.

Can a product pass four risks but fail on the fifth?

Yes, and that is exactly the scenario the fifth risk exists to catch: a feature can be wanted, profitable, buildable, and usable, and still cause real harm to a specific group, which the first four risks alone would never flag.

How is this different from a simple pros and cons list?

The five categories force a structured check across distinct failure modes, desirability, viability, feasibility, usability, and ethics, rather than an open-ended list that can easily skip an entire category of risk without anyone noticing.

Sources

Written by

Andre Albuquerque

Andre Albuquerque

CEO of Builders Camp, SuperOperator, and other companies. Building products.

CEO of Builders Camp, SuperOperator, and other companies. Building products.

LinkedInMore guides by Andre Albuquerque

Last updated 2026-09-16

Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.

See the Product Strategy bootcamp