product-prioritization

Prioritize your product backlog by combining evidence gathering with weighted scoring and opportunity-cost reasoning. You score features on Demand, Impact, Effort, and Alignment—weighting Demand highest—to produce objective rankings instead of opinion-driven roadmaps.

The best way to rank a backlog from user feedback is to analyze the feedback to identify specific user demand evidence, then score each proposed feature against Impact, Effort, and Alignment. Demand is weighted highest to prevent easy-to-fake claims from skewing the roadmap.

Plan an MVP scope by answering forcing questions that identify the specific user, the consequences of not building, and the smallest valuable deliverable. This framework isolates the core valuable MVP before committing to full implementation effort.

Yes, you can assess a single feature by running it through the same forcing questions and weighted scoring framework. The Skill evaluates the individual feature's Demand, Impact, Effort, and Alignment to output a build, kill, or investigate recommendation with falsifiable criteria.

Yes, roadmap planning effort estimates should use dual scoring for both human and AI-assisted implementation speed. Comparing these dual effort estimates against weighted user demand and impact scores directly influences the final opportunity-cost reasoning and prioritization outcome.