value-realization

What this skill does

# Value Realization Philosophy

**Status**: Production Ready ✅
**Version**: 1.2.5
**Last Updated**: 2026-05-12
**Type**: Analytical Framework

## Overview

This skill provides a philosophical framework and analytical methods for evaluating whether end users can "know" what value they can achieve through a product. It guides analysis from a value discovery perspective, rather than providing checklists.

**What this skill provides**:
- Framework to evaluate product ideas when certainty is lacking
- Analysis methods for assessing end user value discovery
- Patterns from real product successes and failures
- Analysis methods for product design, positioning, and value communication

**Core question**: Can end users clearly understand what value they'll achieve through the product - even if that value takes time to achieve?

**Key terminology**:
- **User**: The person using this skill (product creator, PM, designer, entrepreneur, etc.)
- **End user**: The person who will use the product being discussed
- **Value**: A beneficial relational property between subject and object. In product analysis, judgments about whether value holds must be specified in terms of outcomes that end users can understand, verify, and perceive in a concrete value scenario (such as identity, financial gain, capability enhancement, time savings, etc.)
- **Value Relation Position**: An analytical element within a value scenario that indicates where value confirmation or outcome realization occurs in the value relation. Analysis must distinguish between: end users confirming that an external object, content, feature, or product is valuable to them; end users achieving their own outcome through the product; and end users themselves, their actions, or their outputs being confirmed as valuable through feedback from other people, groups, organizations, or systems. The three can coexist, but they cannot substitute for one another
- **Features**: The product's technical capabilities
- **Value Scenario**: A concrete context in which end users use the product with a specific task or goal and obtain an outcome that can be understood, verified, and perceived. A value scenario should specify the end-user task, product role, value relation position, and outcome end users achieve
- **Usage Scenario**: A concrete context in which the product may be used
- **Use Case**: A specific task or workflow end users complete with the product in a given context

**Core distinction**:
- Features are not value
- Features are what the product can do, value is the outcomes end users gain
- Analysis must translate features into specific end user outcomes
- Value analysis should place value in a concrete scenario
- Value scenario analysis should specify the value relation position to avoid conflating external objects being considered valuable, end users achieving their own outcomes, and end users themselves, their actions, or their outputs being confirmed as valuable
- Usage scenarios explain where the product may be used, use cases explain how end users use it to complete tasks, and value scenarios explain what outcome end users get in that context

## Core Insight

End users adopt products when they **know** what value they'll get. This "knowing" is critical:

- If end users know they'll achieve something valuable (even long-term), they'll use it
- If end users don't know what they'll achieve, they won't use it - no matter how good the product is

**What "knowing" means**:
- End users can explain to themselves or others why they're using the product
- End users can describe what they'll achieve (not just what features exist)
- End users understand the outcome, even if it takes time to achieve

**Observed patterns**:
- When end users can articulate clear value → higher adoption rates
- When end users cannot articulate value → adoption challenges, even with innovative features
- Some end users adopt without full clarity, then discover value through use (progressive discovery)

**Value types end users seek** (but aren't limited to):
- Identity and belonging
- Financial gain
- Short-term benefits
- Long-term benefits
- Status and recognition
- Capability enhancement
- Time savings
- Problem resolution

**Role of value scenarios**:
Product attributes themselves are not end-user value. Analysis should use scenarios to connect product attributes to end-user outcomes, define the context where value occurs, and provide a basis for judging whether the value holds.

Attributes still matter. Attributes provide evidence; scenarios help establish the relationship between attributes and end-user outcomes.

Value scenarios should also specify the value relation position: what external object end users confirm as valuable to them, what outcome they achieve for themselves through the product, and whether they themselves, their actions, or their outputs are confirmed as valuable through feedback.

## The Challenge

Most product creators face a hidden problem: **end users often don't know what they actually want, and how they articulate it may be wrong**.

The job isn't just to build what end users ask for - it's to help end users discover what value they're actually seeking.

## How to Engage with This Skill

This skill operates through conversational analysis. When the user presents a product idea, feature, copy, usage scenario, or use case:

1. **Identify the end users** - Determine who will use the product
2. **Identify the value scenario** - Determine the concrete context where value occurs and specify the value relation position
3. **Evaluate through four dimensions** - Value clarity, timeline, perception, discovery
4. **Adjust output to the request** - Full analysis, copy, usage scenarios, use cases, or diagnostic assessment
5. **Consider context** - Each product, market, and end user group differs

**This framework guides thinking. It does not prescribe solutions.**

**Analysis approach:**
- Evaluate through four dimensions around the current value scenario
- Adjust output format to the current request:
  - When evaluating a product idea, fully analyze all four dimensions
  - When writing copy, usage scenarios, or use cases, first judge whether value is clear, when value occurs, whether the outcome is perceivable, and whether end users need to discover value through use
  - When diagnosing existing copy or a value proposition, use the four dimensions to assess effectiveness
  - When the user asks to optimize a product or provide improvement directions, first use the value scenario and four dimensions to explain how the current object of analysis affects how end users obtain, understand, verify, or perceive outcomes in a concrete value scenario, then propose adjustments related to value realization or value communication; adjustments should be derived from the value scenario and analysis conclusions, and should distinguish judgments supported by current evidence from hypotheses requiring verification
- Before outputting status indicators in the four-dimension analysis, read `references/scoring-rubric.md`
- Analysis process for each dimension:
  1. Explain the analytical reasoning for this dimension (why this dimension matters for this product)
  2. Systematically apply the dimension's analytical methods to the current product idea, feature, copy, usage scenario, or use case, stating the preconditions and applicability boundaries the judgment depends on (cannot skip the analysis and jump directly to questions)
  3. After completing the dimension analysis, provide status assessment using status indicators (🔴🟡🟢) with specific description of current state (not vague generalizations). Check the status against `references/scoring-rubric.md`
  4. When citing product cases, base on verifiable information and explain relevance to current product (case applicability assessment in "Research Methodology" section)
  5. Pose sharp questions that directly challenge product necessity or require comparison with existing solutions
- Aft