Prioritize a Feature Backlog Using the Kano Model
Sort backlog items into Must-Be, Performance, or Delighter buckets based on user reaction to absence, clarifying which features prevent churn versus drive growth.
You getMarkdown table with 4 columns, section and section
Prompt
Act as a principal product manager specializing in feature prioritization.
I will paste a list of feature requests below this prompt. Categorize every item using the Kano Model based on how users react if the feature is missing.
Rules:
1. Classify each item into exactly one category: Must-Be (table stakes; absence causes outrage, presence is neutral), Performance (linear satisfaction; more is better), or Delighter (unexpected value; absence goes unnoticed, presence creates loyalty).
2. For each feature, write one concise sentence explaining customer sentiment if the feature is missing.
3. Identify the recommended implementation sequence: ship Must-Be fixes first to plug churn, allocate majority capacity to core Performance, and pick one high-visibility Delighter.
Output format:
- Markdown table with 4 columns: Feature Name, Kano Category, Absence Impact, Priority Order
- Section: Strategic Sequence (3 bullet points outlining what to build first, next, and last)
- Section: Assumptions & Blind Spots (one short paragraph highlighting data or user segment assumptions made)Example output
Tips and common edits
Why this works
- Forces categorization strictly by reaction to absence, eliminating subjective internal debates about what feels important.
- The 4-column structured table gives clear implementation order instead of an unranked list of buckets.
- Includes an explicit blind-spots check to ensure customer segment differences do not skew the priority order.
Paste your unorganized list of feature ideas or backlog requests directly below the prompt in ChatGPT, Claude, or Gemini.
Common edits
- Add a fourth category (Indifferent/Reverse) to explicitly identify features that should be cut entirely.
- Add an estimated engineering effort column (S/M/L) to calculate return on effort within each Kano bucket.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Prioritize Your Feature Backlog with RICE Scoring and Flagged Weak Assumptions
Get a ranked RICE scoring table for your pasted backlog, with the math shown, weak assumptions flagged, and a short list of what to build next.
Define Feature Non-Goals and Scope Boundaries
Sort requested features into three clear out-of-scope buckets with explicit business reasons to prevent scope creep.
Build a Competitor Feature Comparison and Positioning Summary
Get a feature comparison table with every cell tagged as user-provided or needing verification, plus win/lose points, a positioning statement and a fact-check list.
Extract win and loss drivers from CRM notes
Turn raw CRM deal records into actionable product, pricing, and sales execution patterns. Use it to prepare roadmap reviews and board updates.
Score beta readiness for general availability release
Evaluate qualitative feedback, bug logs, and usage stats to decide if a beta is ready for general availability. Use this to make unbiased release decisions.
Draft a working-backwards press release and FAQ
Write an Amazon-style press release and hard FAQ to clarify customer value and address tough technical questions before writing code.
- Transform Customer Interview Transcripts into Ranked Pain-Point Matrix
- Classify onboarding drop-offs into cognitive and value friction
- Define beta cohorts and launch exit metrics
- Draft a customer advisory board charter
- Analyze customer feedback using Jobs to Be Done
- Break a product epic into vertical MVP slices