identify-assumptions-existing

identify-assumptions-existing - Product Assumption Identification and Risk Assessment Tool

Skill Overview

Systematically identify risky assumptions in existing product feature ideas through multi-perspective devil’s advocate thinking, helping product teams uncover potential issues before feature development begins.

Use Cases

1. Feature Idea Stress Testing

Before committing development resources, examine feature ideas comprehensively from the perspectives of product managers, designers, and engineers to uncover potentially overlooked risks and assumptions and avoid blind investment.

2. Product Risk Assessment

When a team is preparing to launch a new feature or enter a new market, use a structured assumption-identification process to assess potential issues across four key risk areas: value, usability, feasibility, and viability.

3. Assumption Mapping Preparation

Provide input for assumption-mapping workshops or prioritization meetings, helping teams identify which assumptions most urgently require validation and improving the quality of product decisions.

Core Features

1. Multi-Perspective Risk Analysis

Examine potential reasons a feature idea might fail from three professional perspectives: the product manager (business viability and product–market fit), the designer (usability and user experience), and the engineer (technical feasibility and performance challenges). This helps avoid blind spots caused by relying on a single perspective.

2. Four-Dimensional Risk Identification

Systematically cover four key dimensions: value (whether the feature solves a real problem), usability (whether users can get started), feasibility (whether it can be commercialized), and viability (whether it can be technically implemented), ensuring a comprehensive and structured risk assessment.

3. Testable Assumption Outputs

For each identified risk assumption, specify a concrete failure scenario, a confidence level (high/medium/low), and a recommended validation method, turning abstract concerns into actionable testing plans.

Frequently Asked Questions

How do you identify risk assumptions in a product feature?

Start from three professional perspectives and systematically examine the potential issues a feature idea may face across four risk areas: value, usability, feasibility, and viability. For each assumption, define a specific failure scenario, the current confidence level, and a recommended testing method. This process helps teams uncover potential risks before development and avoid wasting resources.

What is assumption mapping, and why should we do it?

Assumption mapping is a product discovery technique that helps teams identify and prioritize the core assumptions that need to be validated. When developing new features for an existing product, teams often make decisions based on unvalidated assumptions. Assumption mapping makes these implicit assumptions explicit and guides teams to test the most critical ones first, thereby reducing the risk of product failure.

What are the four risk areas of a product?

The four key risk areas are: value (whether the feature creates value for customers and solves a real problem), usability (whether users can understand and use it and whether the learning curve is acceptable), feasibility (whether the market, sales, legal, and other functions can support it), and viability (whether it can be technically implemented and whether integration risks exist). These four dimensions cover the key elements of product success and help teams comprehensively evaluate feature ideas.