User Needs Research Report

Problem

Product teams often face three issues: user feedback is abundant but hard to classify, priority debates rely on opinion, and reports list features without an evidence chain. This skill turns scattered interviews, reviews, survey data, behavior data, and competitor observations into a reusable analysis framework, helping engineers and product managers convert “users say they want” into evaluated priorities and strategy suggestions.

How It Works

It analyzes six dimensions:

• Need layers: Use a L1-L5 pyramid to separate functional, safety, social, respect, and growth needs, identifying current coverage and gaps.
• Pain points: Combine 5Why, scenario reconstruction, and current-vs-ideal comparisons, scoring intensity, frequency, urgency, and willingness to pay to produce P0-P3 priorities.
• User segmentation: Split users by demographics, usage frequency, payment ability, and lifecycle to form personas and segment strategies.
• Decision path: Check awareness, interest, evaluation, decision, purchase, usage, and repurchase to locate drop-off points and weighted competitive factors.
• Purchase motives: Separate functional, emotional, and social motives so trust, identity, and status are not ignored.
• Behavior logic: Use motivation, ability, and prompts to check friction, and evaluate retention, conversion, and referral metrics.

The output is a structured report suitable for team alignment, project approval, or executive review.

Boundaries

It is best used when evidence is limited or requirements are noisy, such as new product validation, feature optimization, growth bottlenecks, and market entry strategy. It is less suitable when insights are already clear and only execution is needed, when the issue is purely technical feasibility, or during urgent incident response.