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

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

Example for: an early-stage B2B team collaboration tool with a messy backlog.

Feature NameKano CategoryAbsence ImpactPriority Order
SAML SSO IntegrationMust-BeEnterprise prospects drop out of the sales funnel immediately without IT compliance sign-off.1
Password Reset Flow FixMust-BeGenerates high-volume support tickets and immediate user abandonment.2
Fast In-App SearchPerformanceUsers tolerate slow search briefly, but latency directly reduces daily active usage and satisfaction.3
Bulk CSV Member ExportPerformanceAdmin workflows slow down without it, but manual workarounds exist in the short term.4
AI Meeting SummariesDelighterUsers do not expect native meeting transcripts, so absence causes zero complaints or churn.5
Strategic Sequence
  • Immediate Fixes (Must-Be): Implement SAML SSO and resolve the broken password reset flow right away to stop active churn and unblock pipeline deals.
  • Sustained Investment (Performance): Dedicate 60% of engineering bandwidth to fast in-app search indexing, as search speed directly correlates with daily retention.
  • Competitive Differentiator (Delighter): Schedule AI meeting summaries as a single targeted bet next quarter to test viral adoption without derailing foundation work.
Assumptions & Blind Spots

This categorization assumes mid-market B2B buyers who demand strict enterprise security standards. If the target audience shifts primarily toward bottom-up freemium developers, SSO drops down the priority rank while search speed and keyboard shortcuts become table stakes.

Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Product Management