Naming and Operationalizing SVPG’s Four Product Risk Areas

Status: Supporting comparison, not canonical guidance. See risk-areas-model.md for the selected model. This document preserves alternative names, the four-dimensions-with-optional-Ethics position, the practitioner survey, and the history behind the overlapping terms.

Recommended naming conventions#

Recommended default: Product Risk Dimensions#

The recommended default for most product teams is:

Product Risk Dimensions Value · Usability · Feasibility · Viability

This is more precise than simply naming a section “Four Risks.”

The reason is semantic as well as practical. ISO 31000 defines risk as the effect of uncertainty on objectives. Under that meaning, “Value” by itself is a subject or dimension; even “value risk” is still a category label. A concrete risk would say what might happen and why the product objective would suffer. SVPG itself calls its model a risk taxonomy, meaning a classification system for types of risk, which supports treating the four labels as categories or dimensions rather than four individual risk records. ¹²

For example:

Dimension: Value Risk: Target finance teams may see too little improvement over their spreadsheet workflow to switch, preventing adoption.

The second sentence is a risk that can be investigated. “Value” indicates where to look.

Pros: faithful to SVPG; preserves the useful Value/Usability distinction; works equally well for B2B and B2C; separates taxonomy from concrete risk statements; gives design, engineering and business teams a shared coverage checklist. ²

Cons: the word risk can make discovery sound like defensive risk management; people may still write vague entries such as “high value risk” instead of spelling out what could fail.

Decision rationale: This preserves the label most faithful to SVPG and establishes that the four names are categories rather than individual risk records. It remains an alternative because the canonical document narrows the label to Solution Risk Dimensions.

Good alternative for discovery workshops: Product Uncertainties#

A softer formulation is:

Key Product Uncertainties Value · Usability · Feasibility · Viability

This works particularly well in early discovery, where the goal is to expose what the team does not yet know and gather evidence. SVPG’s own current “build to learn” language and Pichler’s risk-driven strategy discovery both treat uncertainty as something to resolve before larger commitments are made. ³⁴

Its weakness is precision. “Uncertainty” indicates that knowledge is incomplete; it does not state what objective is threatened or what consequence follows. That makes it a good workshop heading and a weaker risk-register item. This distinction follows the ISO definition of risk as the effect that uncertainty has on objectives. ¹

A useful phrasing is:

“What are the biggest uncertainties across Value, Usability, Feasibility and Viability?”

Then convert the important answers into specific risk statements.

Decision rationale: “Uncertainty” is retained as workshop language because it helps elicit unknowns. It is not canonical record structure because it does not state the threatened objective or consequence.

Best for an experiment backlog: Assumption Categories#

For a team running frequent discovery tests, Torres’ terminology is useful:

Assumption Categories Desirability/Value · Usability · Feasibility · Viability · Ethics, where applicable

An assumption is naturally testable because it can be written as a proposition that needs to hold. Torres defines assumptions in essentially those terms and recommends identifying, prioritizing and testing them rather than evaluating a whole idea as one indivisible object. ⁵⁶

For example:

Risk: Buyers may not switch because the existing process is good enough. Assumption: The target buyer experiences the problem frequently enough that eliminating it changes purchase behavior.

The risk and assumption are related but are not the same sentence.

The disadvantage of using Assumptions as the name for the top level is that Value, Usability, Feasibility and Viability are not themselves assumptions. A product can contain dozens of assumptions in every category; Torres’ August 2026 material continues to emphasize generating many underlying assumptions before identifying the risky ones. ⁷

Avoid:

❌ “The four assumptions are Value, Usability, Feasibility and Viability.”

and use:

✓ “Assumptions are evaluated across four product risk dimensions.”

Decision rationale: This section supplies the canonical model’s atomic unit without treating the dimension labels as assumptions. The category says where to look; the assumption states what must be true and can be tested.

When to add Ethics/Safety#

SVPG places ethical, compliance and related concerns largely within business viability. Cagan has acknowledged the argument for separating ethical risk when it otherwise receives insufficient attention. Torres makes Ethical assumptions a fifth category, while Pichler makes Ethicality a first-class product-success factor. ²⁸⁵⁹

For a team where potential harm, privacy, fairness, safety or societal effects are material, the recommended form is:

Product Risk Dimensions: Value · Usability · Feasibility · Viability · Ethics/Safety

The advantage of a fifth category is attention: teams are forced to ask the question explicitly. The cost is another category and some overlap with viability, security, compliance and usability. SVPG’s 2023 discussion correctly identifies this as a tradeoff between completeness and a taxonomy people can remember and use. ²

Decision rationale: This preserves the source’s optional-Ethics position. The canonical document resolves the tradeoff differently by making Ethics explicit, because maintaining attention to harm outweighs the cost of overlap.

How practitioners name and operationalize the areas#

The main difference between the frameworks is not whether customer, user, technical, and business questions matter. It is what object the framework asks the team to manage: SVPG manages risk categories; Torres manages assumptions; Lean Startup manages hypotheses and learning; IDEO and consultancies use evaluation lenses; Google Design Sprints organize around assumptions and questions; Pragmatic Institute organizes around product-management activities. ^2510111213

Decision rationale: This inventory shows that similar concerns are organized around different managed objects. It supports the synthesis, but the full survey belongs here because it would interrupt the canonical path from definitions to workflow.

Two patterns dominate this comparison.

First, SVPG is one of the few prominent frameworks that deliberately keeps Value and Usability separate. IDEO, NN/g, McKinsey and similar design-oriented frameworks usually put both under Desirability. Cagan says this separation became important to him particularly in B2B products, where the person deciding whether to buy a product and the person required to use it can be different people with different criteria. ²

Decision rationale: This pattern supports keeping Value and Usability separate in the canonical taxonomy, especially where buyer and user are different people.

Second, several practitioners have shifted attention from naming broad categories to identifying the specific belief that could be wrong. Torres is the clearest example: an assumption is a belief that must hold for an idea to succeed, and the team should surface many such assumptions, rank them by risk, and test the important ones. Google Design Sprints similarly decomposes assumptions and converts them into sprint questions, while Lean Startup expresses uncertain beliefs as measurable hypotheses. ⁵¹²¹⁰

Decision rationale: This pattern supports making the concrete assumption, rather than the broad risk category, the atomic discovery artifact. Together, the two patterns separate coverage from unit of work.

Alternative taxonomies and why they differ#

Desirability, feasibility, viability#

The closest widespread alternative to SVPG is:

Desirability · Feasibility · Viability

IDEO explicitly frames design thinking around what is desirable for people, feasible with technology, and viable for organizations. NN/g uses essentially the same DVF model, and McKinsey uses customer desirability, technical feasibility, and business viability in innovation work. ¹¹¹⁸²²

The mapping is approximately:

This consolidation is intentional. NN/g, for example, defines desirability in terms of user value and says a desirable product must be useful and usable. SVPG’s explanation of the competing taxonomies likewise says IDEO’s desirability combines customer value and usability. ¹⁸²

The three-lens model has a clear advantage: it is compact and works well as an innovation or concept-evaluation model. The tradeoff is loss of diagnostic precision. A concept can solve a valuable problem while still having an unusable workflow. That distinction becomes especially useful in B2B, internal tools and other settings where buyers, administrators, approvers and end users are different people. This latter argument is also Cagan’s stated rationale for retaining separate Value and Usability categories. ²

Decision rationale: This is the nearest competing coverage model, so it makes the cost of merging Value and Usability explicit. The canonical synthesis chooses diagnostic precision over compactness.

Five assumption categories#

Teresa Torres’ taxonomy is structurally close to SVPG but changes both the labels and the object being classified:

Desirability assumptions · Viability assumptions · Feasibility assumptions · Usability assumptions · Ethical assumptions

Here, an item on the team’s board is not normally “the viability risk.” The team asks what specifically has to be true about economics, behavior, technology, workflow or harm for an idea to work. ⁵

This distinction is operationally important. Torres explicitly argues that describing a solution as having “viability risk” leaves the test ambiguous; enumerating viability assumptions gives the team something concrete to evaluate. Her workflow uses story maps to expose desirability, usability and feasibility assumptions, traces an Opportunity Solution Tree to find viability assumptions, intentionally explores potential harm, and then prioritizes assumptions for testing. ⁵⁶

The distinction can be summarized this way:

SVPG: “Has every important kind of product risk been covered?”

Torres: “What exactly is being assumed, and which assumption should be tested next?”

Those are complementary questions, not competing ones. This is an analytical synthesis of the two methods. ²⁵

Decision rationale: This is the bridge between SVPG and Torres: dimensions provide coverage, while assumptions provide testable propositions. That complementarity, rather than either framework alone, is the basis for the canonical synthesis.

Desirability, feasibility, viability, ethicality#

Roman Pichler’s framework is:

Desirability · Feasibility · Viability · Ethicality

He calls them product success factors, while in strategy-discovery work he talks about strategy risks within the same four areas. His validation loop starts with the most important uncertainty, applies an appropriate research method such as interviews, observation, a throwaway prototype or business-model analysis, uses the resulting evidence to change or retain the strategy, and repeats until the remaining significant risks have been addressed. ⁹⁴

Its conceptual difference from SVPG is revealing:

The choice reflects the level at which the framework is being used. Pichler is often validating product strategy; Cagan’s taxonomy is heavily used during solution discovery. At a strategy level, ethics may deserve a separate gate while detailed interaction usability can sit lower in the decomposition. ⁹⁴²

Decision rationale: Pichler shows that category choice changes with the level of analysis. His strategy model explains why Ethics may rise and Usability may be nested, but it does not replace the canonical solution-level model.

Value and growth hypotheses#

Lean Startup takes a different route. Its core categories are not four product properties. It asks teams to identify risky assumptions, express important ones as hypotheses, build the smallest useful experiment or MVP, measure real behavior, and generate validated learning. Its named high-level hypotheses are particularly value hypotheses and growth hypotheses. ¹⁰

That means there is no clean one-to-one mapping:

• Value is directly represented by the value hypothesis.
• Viability is partly covered through value, growth, adoption and business-model economics.
• Usability can be a hypothesis that affects customer behavior, but it is not a canonical top-level Lean Startup category.
• Feasibility can likewise be tested through experiments or prototypes, but core Lean Startup terminology does not elevate it to a named sibling of value and growth. ¹⁶¹⁰

Lean Startup is therefore better understood as a learning architecture than as a completeness checklist.

Decision rationale: Lean Startup is retained to prevent a false one-to-one taxonomy mapping. It contributes an evidence-and-learning loop, not a complete checklist of solution failure modes.

Corporate innovation variants#

BCG X shows why taxonomies change with context. Its “Four Lenses for Validation” are Desirability, Viability, Feasibility, and Strategic Fit. The extra question is whether a venture has synergies or advantages within the sponsoring company. ²⁴

That suggests a useful general principle: the fourth or fifth category often exposes the failure mode that a particular organization is most prone to overlook. SVPG separated business viability because customer value could crowd it out. Torres and Pichler expose ethics because harm can disappear inside an overly broad business category. BCG exposes strategic fit because corporate venture ideas can look attractive in isolation while making little sense for the parent company. This is an inference from how the respective authors explain their taxonomies. ²⁵⁹²⁴

Decision rationale: These variants support a general rule: an extra category is an attention mechanism for a failure mode the host organization tends to hide. That rule helps justify explicit Ethics without claiming that five categories are universal.

A compact comparison makes the pattern clearer:

The practical lesson is that there are two independent design choices in any taxonomy:

1. Coverage: Which classes of failure deserve an explicit category?
2. Unit of work: Are the managed objects lenses, risks, assumptions, hypotheses, questions, or experiments?

Much of the apparent disagreement between practitioners disappears once those two choices are separated. ²⁵¹⁰²⁴

Decision rationale: This is the comparison’s main analytical result. The canonical model makes the two choices separately: five dimensions for coverage and concrete assumptions for the unit of work.

Source context and evolution#

The terminology evolved over time, which explains some apparent contradictions between articles.

This history matters because neither framework is a static four-box or five-box checklist. SVPG increasingly describes the four risks as a conceptual model for evaluating potential solutions, while Torres embeds nearly equivalent concerns inside a broader continuous decision system. ³³³⁵³⁹

Decision rationale: The chronology is retained to reconcile changing source language and apparent contradictions. It comes after the conceptual comparison because history explains the terminology but does not determine the operating model.

Citation references#

Source limitation: The numbered turn... references preserve provenance from the original research session but are not portable citations. The linked references below are the independently usable bibliography.

References#

Decision rationale: This bibliography remains separate from the internal reference list because these links are reader-usable evidence rather than session-local provenance markers.