Roadmap Prioritization
Prioritizing Roadmap Features Using the Kano Model
This prompt helps teams prioritize features for a product roadmap using the Kano Model, which categorizes features into Must-Haves, Performance Needs, and Delighters. It ensures that the roadmap balances essential functionality with elements that excite and engage users.
Responsible:
Product Management
Accountable, Informed or Consulted:
Product, Design, 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:
Gather user feedback or survey data to assess feature expectations and preferences.
Categorize features based on their necessity, impact, and ability to surprise users.
Review competitor offerings to understand market standards for Must-Haves and Delighters.
THE PROMPT
Help prioritize features for the product roadmap of [product/service name] using the Kano Model. For each feature, classify it into one of the following categories:
Must-Have Features: Basic functionalities users expect that are critical to product success.
Performance Needs: Features that directly impact user satisfaction when improved.
Delighters: Unexpected features that exceed user expectations and enhance satisfaction.
Recommend a balanced prioritization of features, ensuring that Must-Haves are addressed first, Performance Needs are optimized, and Delighters are strategically included to boost engagement. If additional details about user expectations or feature descriptions are needed, ask clarifying questions to refine the prioritization.
Bonus Add-On Prompts
Suggest ways to identify Delighters that align with user personas and market trends.
Propose a method for assessing whether a feature is a Must-Have or a Performance Need.
Identify potential trade-offs between optimizing Performance Needs and adding Delighters.
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 the impact of Must-Haves vs. Delighters.
Add resource assessments to evaluate the feasibility of including Delighters.
Incorporate customer satisfaction surveys to validate Performance Needs.
Use scenario-based planning to test how features affect overall user experience.
Tailor the model for B2B vs. B2C products, emphasizing different user expectations.
WHEN TO USE
To balance foundational functionality with engaging enhancements.
When prioritizing features that directly influence user satisfaction.
During roadmap planning for competitive differentiation.
WHEN NOT TO USE
If user feedback data for classifying features is unavailable.
When the focus is solely on technical or internal product improvements.