analyze-feature-requests

Feature Request Analysis and Prioritization

Skill Overview

Helps product managers intelligently analyze customer feature requests, categorize them by theme, and scientifically prioritize them based on strategic alignment, impact, effort, and risk.

Applicable Scenarios

Reviewing customer requests: When receiving a large number of customer feature requests and needing to analyze and filter them systematically, this skill automatically groups requests by theme and evaluates how well each request aligns with the product strategy, helping prevent customer-driven development.

Organizing the backlog: When faced with a complex list of backlog items and needing to quickly identify high-value opportunities, this skill uses a multidimensional assessment—Impact, Effort, and Risk—to support data-driven prioritization decisions.

Making prioritization decisions: When planning a product roadmap or preparing for the next iteration, this skill provides a scientific evaluation method based on the Opportunity Score, ensuring that resources are invested in solving the most valuable problems rather than simply accumulating features.

Core Features

Intelligent request classification: Automatically groups feature requests by theme, identifies related requests, and names thematic categories, helping users quickly build a clear, structured view from a disorganized list of requests.

Strategic alignment assessment: Evaluates how well each theme aligns with the product’s goals and vision. It uses the Opportunity Score method—Importance × (1 − Satisfaction)—to quantify the value of problems as perceived by customers and prioritize genuine pain points.

Multidimensional prioritization: Based on four dimensions—Impact (customer value and number of users), Effort (development and design resources), Risk (technical and market uncertainty), and Strategic Alignment—this skill provides ranking recommendations for the top three features, including alternatives, high-risk assumptions, and minimal testing methods.

Frequently Asked Questions

How should the priority of customer feature requests be assessed?

This skill uses a four-dimensional evaluation framework: Impact (impact and number of users), Effort (required resources), Risk (uncertainty), and Strategic Alignment. For customer-reported problems, it applies Dan Olsen’s Opportunity Score method:

Opportunity Score = Importance × (1 − Satisfaction)

The score is normalized to the 0–1 range. This formula prioritizes problems that customers consider important but that are poorly addressed by current solutions, rather than simply adding more features.

How can a large number of requests be categorized and organized?

This skill automatically identifies related requests and groups them by theme. You only need to provide the product goals and request list. The skill analyzes semantic similarities among the requests, creates meaningful thematic categories, and evaluates the strategic alignment of each theme. The final output includes thematic groupings, prioritization, and specific implementation recommendations, helping you quickly establish a clear structure from a chaotic set of requests.

How can overengineering based on customer requests be avoided?

The core principle of this skill is: “Never allow customers to design solutions.” It prioritizes analyzing opportunities—the underlying problems—rather than features. When customers propose specific feature requests, the skill guides you to focus on the underlying needs and uses the Opportunity Score to assess the importance of the problem itself, rather than directly implementing the customer-suggested solution. For prioritized features, it also provides alternative solutions and high-risk assumption analyses, helping you validate assumptions with a minimum viable product and avoid overinvestment.