How the Value/Usability/Feasibility/Viability Framework Works in pm‑product‑discovery

The Value/Usability/Feasibility/Viability (VU/F) framework is a four‑dimensional risk‑categorization model that forces product teams to validate assumptions about customer demand, user experience, business sustainability, and technical constraints before building solutions.

The pm‑product‑discovery skill set in the phuryn/pm‑skills repository operationalizes Teresa Torres’ Continuous Discovery Habits through modular markdown files that encode the VU/F framework into repeatable discovery workflows. By explicitly defining these four risk categories in skill files such as identify‑assumptions‑existing/SKILL.md, the repository enables LLM‑driven product discovery that consistently surfaces and tests “leap‑of‑faith” assumptions.

The Four Risk Categories in the VU/F Framework

Each dimension of the framework targets a specific failure mode that can kill a product initiative. The categories are defined in pm‑product‑discovery/skills/identify‑assumptions‑existing/SKILL.md and identify‑assumptions‑new/SKILL.md, ensuring consistent application across new and existing products.

Value

Value asks whether the solution creates real customer value. This covers demand validation, willingness to pay, and the problem‑solving impact of the proposed feature. In the identify‑assumptions‑existing skill, Value appears as the first risk category under step 2, prompting teams to articulate assumptions like “users will pay $10/month for this analytics add‑on.”

Usability

Usability examines whether users can figure out how to use the solution. It captures onboarding speed, learning curve, and cognitive load. The framework forces explicit consideration of user experience risks before development begins, ensuring that elegant solutions are also accessible.

Viability

Viability determines if the business model can support the solution. This includes monetization strategy, financing, compliance requirements, and scalability from a business perspective. The category is defined in the existing‑product skill and expanded with additional business‑risk prompts in the new‑product variant.

Feasibility

Feasibility assesses whether the team can build the solution with current technology. It covers technical constraints, integration risks, and infrastructure scalability. Both assumption‑identification skills list Feasibility as a required category under step 2, ensuring engineering constraints are surfaced early.

How the Framework Orchestrates Product Discovery

The VU/F framework is not merely a checklist; it drives a structured workflow orchestrated by the /discover command. The process unfolds across four distinct stages defined in pm‑product‑discovery/commands/discover.md.

Step 1: Contextualization

The discovery command first determines whether the work concerns a new or existing product (lines 22‑25 of discover.md). This contextual branching ensures the appropriate assumption‑identification skill is invoked.

Step 2: Assumption Extraction

Based on the context, the command calls either identify‑assumptions‑existing or identify‑assumptions‑new. Each skill iterates over the four VU/F categories, prompting the generation of concrete, testable assumptions. For example, the new‑product skill extends the core framework with additional risk dimensions while preserving the four primary categories.

Step 3: Confidence Rating and Testing

For every assumption extracted, the user rates confidence and proposes a specific test (lines 42‑44 of identify‑assumptions‑existing.md). This creates a structured risk canvas:

Category	Assumption	Confidence	Test
Value	Users will pay premium pricing for AI features.	Low	Launch fake‑door landing page.
Usability	First‑time users complete setup in < 5 min.	Medium	5‑minute usability test.
Viability	Sales team can close 20 % of qualified leads.	Low	Pilot sales outreach.
Feasibility	Backend handles 1 M events/day without scaling issues.	High	Benchmark existing pipeline.

Step 4: Decision‑Making with Impact × Risk

The resulting VU/F assumption list feeds into the Impact × Risk matrix (step 5 of discover.md). High‑impact, low‑confidence items are flagged as “leap‑of‑faith” assumptions that must be validated before committing engineering resources.

Implementation in the pm‑skills Repository

The framework is explicitly encoded in modular skill files, enabling deterministic execution by LLM orchestrators.

Key Source Files

• pm‑product‑discovery/skills/identify‑assumptions‑existing/SKILL.md – Defines the core VU/F categories for established products.
• pm‑product‑discovery/skills/identify‑assumptions‑new/SKILL.md – Extends the framework with additional risk categories for zero‑to‑one initiatives.
• pm‑product‑discovery/skills/opportunity‑solution‑tree/SKILL.md – References VU/F categories when validating solutions via experiments.
• pm‑product‑discovery/commands/discover.md – Orchestrates the full workflow, invoking the appropriate assumption‑identification skill based on product maturity.

Running a Discovery Cycle

Trigger the framework using the discovery command:

/discover

The command executes the VU/F workflow:

1. Branch – Asks whether the product is new or existing.
2. Extract – Loads the relevant skill file and iterates through Value, Usability, Viability, and Feasibility.
3. Validate – Returns a structured table of assumptions with confidence ratings and proposed experiments.

Because the risk categories are defined once and referenced across multiple skills (including the Opportunity Solution Tree), the framework maintains consistency while allowing extensibility. New risk dimensions (e.g., Ethics, Go‑to‑Market) can be added in the new‑product skill without breaking backward compatibility for existing‑product scenarios.

Summary

• The Value/Usability/Feasibility/Viability framework provides a four‑dimensional lens for identifying product risks before development begins.
• The phuryn/pm‑skills repository implements this framework through modular skill files: identify‑assumptions‑existing/SKILL.md and identify‑assumptions‑new/SKILL.md.
• The /discover command orchestrates a workflow that contextualizes the product stage, extracts VU/F assumptions, rates confidence, and maps risks to an Impact × Risk matrix.
• Each category targets a distinct failure mode: Value (demand), Usability (adoption), Viability (business model), and Feasibility (technical constraints).

Frequently Asked Questions

What is the origin of the VU/F framework?

The framework originates from Teresa Torres’ Continuous Discovery Habits, a product management methodology emphasizing continuous customer touchpoints and assumption testing. The pm‑product‑discovery skill set codifies these principles into executable markdown files that LLMs can process systematically.

How does the framework differ for new versus existing products?

The core four categories remain identical, but identify‑assumptions‑new/SKILL.md extends the framework with additional risk dimensions tailored to zero‑to‑one products. Conversely, identify‑assumptions‑existing/SKILL.md focuses on optimizing or expanding features within validated market contexts, preserving backward compatibility through the same VU/F structure.

How does the VU/F framework integrate with the Opportunity Solution Tree?

The Opportunity Solution Tree (OST) skill references the VU/F categories when validating proposed solutions. After mapping opportunities to solutions in the tree, teams use the four risk dimensions to surface assumptions about each solution, ensuring that the OST is grounded in testable risks rather than untested hypotheses.

Can teams add custom risk categories beyond the four core dimensions?

Yes. The modular architecture of the skill files allows teams to append additional risk categories (such as Ethics or Go‑to‑Market) in the new‑product skill definition without modifying the existing‑product workflow. This extensibility ensures the framework adapts to specialized domains while maintaining the core VU/F safety net.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}