Roadmap Prioritization
Using Weighted Scoring to Prioritize Roadmap Features
This prompt helps teams prioritize features for a product roadmap by applying a weighted scoring system. It ensures features are ranked based on their contribution to key business and user goals, providing a structured and transparent decision-making process.
Responsible:
Product Management
Accountable, Informed or Consulted:
Product, Strategy, Customer Success
THE PREP
Creating effective prompts involves tailoring them with detailed, relevant information and uploading documents that provide the best context. Prompts act as a framework to guide the response, but specificity and customization ensure the most accurate and helpful results. Use these prep tips to get the most out of this prompt:
Define scoring criteria and assign weights based on their relative importance.
Gather data on user needs, business goals, and technical feasibility for each feature.
Review historical outcomes of similar prioritization exercises for context.
THE PROMPT
Help prioritize features for the product roadmap of [product/service name] using a weighted scoring system. Assign weights to key factors such as:
User Value: The extent to which the feature addresses user needs or pain points.
Business Impact: The potential of the feature to drive revenue, retention, or market differentiation.
Development Effort: The estimated time, resources, and complexity required to implement the feature.
Strategic Alignment: How well the feature supports long-term product or business goals.
Calculate a total score for each feature based on the weighted criteria and recommend a prioritized list. If additional information about features, goals, or weights is needed, ask clarifying questions to refine the prioritization.
Bonus Add-On Prompts
Propose weights for each scoring factor based on the product’s strategic priorities.
Identify features with the highest scores and recommend immediate action plans.
Suggest ways to adjust weights dynamically as priorities evolve during development.
Use AI responsibly by verifying its outputs, as it may occasionally generate inaccurate or incomplete information. Treat AI as a tool to support your decision-making, ensuring human oversight and professional judgment for critical or sensitive use cases.
SUGGESTIONS TO IMPROVE
Adjust weights for specific product phases (e.g., MVP vs. post-launch growth).
Include team input to validate scoring criteria and factor importance.
Incorporate a cost-benefit analysis to refine the Development Effort scoring.
Tailor scoring to specific user segments or target markets.
Visualize scores in a roadmap tool or matrix for stakeholder alignment.
WHEN TO USE
To ensure a transparent, data-driven approach to feature prioritization.
When balancing user needs, business goals, and resource constraints.
During collaborative planning sessions where multiple factors must be weighed.
WHEN NOT TO USE
If reliable data for scoring criteria is unavailable.
When a simpler or more qualitative prioritization method is preferred.