analyze-feature-requests

Group related requests into themes, then score each theme on impact, effort, risk, and strategic alignment with your stated product goal. The analysis produces a ranked top-three list with rationale and validation steps for each.

Opportunity Score, from Dan Olsen, equals importance multiplied by one minus satisfaction, normalized to 0-1. It prioritizes customer problems that matter most and are currently underserved, rather than letting customers design the solution.

Yes. Provide the file containing your feature requests directly, and it will be read and analyzed. Structured data can also be summarized into a table before thematic grouping and scoring.

Avoid relying on raw request counts when requests come from a biased sample, such as only vocal enterprise clients. Requests reflect proposed solutions, so reframe them as underlying problems before scoring to avoid building a feature factory.

For each shortlisted feature, identify the highest-risk assumptions about customer need and market fit, then design the lowest-effort test, such as interviews, prototypes, or fake-door tests, before committing development resources.