Roadmap Prioritization
Prioritizing Roadmap Features with MoSCoW Method
This prompt helps teams prioritize features for a product roadmap using the MoSCoW Method, which categorizes features into Must-Haves, Should-Haves, Could-Haves, and Won’t-Haves. It ensures that essential features are addressed first while leaving room for flexibility in lower-priority items.
Responsible:
Product Management
Accountable, Informed or Consulted:
Product, Customer Success, Strategy
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:
Gather a list of potential features to prioritize.
Define success criteria for the product (e.g., meeting launch requirements or customer expectations).
Collect input from stakeholders to align on what constitutes Must-Have functionality.
THE PROMPT
Help prioritize features for the product roadmap of [product/service name] using the MoSCoW method. For each feature, classify it into one of the following categories:
Must-Have: Features critical to the product’s success and viability.
Should-Have: Important features that significantly enhance user experience but are not critical.
Could-Have: Features that are desirable but optional, providing additional value if resources allow.
Won’t-Have: Features that are not feasible or aligned with current goals and can be revisited later.
Provide recommendations for how to allocate resources to Must-Have and Should-Have features while considering opportunities for Could-Haves. If additional context about user needs, business goals, or development constraints is required, ask clarifying questions to refine the prioritization.
Bonus Add-On Prompts
Suggest ways to identify Must-Have features that directly address user pain points.
Propose criteria for moving features between Should-Have and Could-Have categories.
Recommend strategies to revisit and evaluate Won’t-Have features in future roadmaps.
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
Focus on user personas to determine how features should be categorized.
Tailor prioritization for specific project phases (e.g., MVP vs. mature product).
Incorporate feedback from technical teams to validate development feasibility.
Highlight interdependencies between features to inform category placement.
Include competitive analysis to decide which Could-Have features could become differentiators.
WHEN TO USE
When organizing and categorizing features for a clear and structured roadmap.
To balance essential requirements with additional features based on resource availability.
During collaborative roadmap discussions with multiple stakeholders.
WHEN NOT TO USE
If no clear success criteria or feature list exists.
When focusing solely on innovative or high-impact features without considering foundational needs.