<< All versions

Skill v1.0.0

currentLLM-judged scan90/100
8421bit/niopd-skills/niopd-ur-kano
──Details
PublishedOctober 22, 2026 at 05:36 PM
Content Hashsha256:e5b024ba76811310...
Git SHA1c2c090da96f
──Files
Files (1 file, 3.3 KB)
SKILL.md3.3 KBactive
SKILL.md · 105 lines · 3.3 KB

version: "1.0.0" name: niopd-ur-kano description: Applies Kano Model to categorize features based on customer satisfaction impact. Use for feature prioritization, customer satisfaction optimization, or product differentiation strategy.


Kano Model Analysis Skill

This skill applies the Kano Model to categorize features based on their relationship to customer satisfaction.

Theoretical Foundation

Origin

The Kano Model was developed by Professor Noriaki Kano (Tokyo University of Science) in 1984, providing a theory of customer satisfaction.

Feature Categories

mermaid
quadrantChart
title Kano Model
x-axis Feature Absent --> Feature Present
y-axis Dissatisfied --> Satisfied
quadrant-1 Attractive
quadrant-2 One-Dimensional
quadrant-3 Must-Be
quadrant-4 Indifferent
CategoryDescriptionEffect
Must-BeExpected, basic needsAbsence = Dissatisfaction, Presence = Neutral
One-DimensionalPerformance featuresMore = More Satisfaction
AttractiveDelighters, unexpectedPresence = Satisfaction, Absence = Neutral
IndifferentDoesn't affect satisfactionNo impact either way
ReverseCreates dissatisfactionPresence = Dissatisfaction

Strategic Implications

  • Must-Be: Must deliver, but don't over-invest
  • One-Dimensional: Compete here, proportional returns
  • Attractive: Differentiate here, high ROI

When to Use

  • Feature prioritization
  • Customer satisfaction strategy
  • Product differentiation
  • Competitive positioning
  • Investment allocation

Instructions

Step 1: List Features to Evaluate

Gather features from:

  • Backlog
  • Competitor analysis
  • Customer requests
  • Team ideas

Step 2: Kano Questionnaire

For each feature, ask two questions:

Functional (presence): "If the product HAD this feature, how would you feel?" Dysfunctional (absence): "If the product DID NOT have this feature, how would you feel?"

Response Options:

  1. I like it
  2. I expect it
  3. I'm neutral
  4. I can tolerate it
  5. I dislike it

Step 3: Classify Using Evaluation Table

Dysfunctional →LikeExpectNeutralTolerateDislike
LikeQAAAO
ExpectRIIIM
NeutralRIIIM
TolerateRIIIM
DislikeRRRRQ

Legend: A=Attractive, O=One-Dimensional, M=Must-Be, I=Indifferent, R=Reverse, Q=Questionable

Step 4: Prioritize Based on Classification

Investment Strategy:

  • Must-Be: Ensure complete coverage (baseline)
  • One-Dimensional: Invest for competitive parity
  • Attractive: Invest for differentiation

Step 5: Generate Report

File path: 02-reports/[YYYYMMDD]-kano-analysis-v0.md

FeatureCategoryPriorityRationale
[Feature]Must-Be/One-Dim/Attractive/IndiffHigh/Med/Low[Reason]

Output Specifications

  • File Naming: [YYYYMMDD]-kano-analysis-v0.md
  • Location: 02-reports/
  • Template: references/kano-template.md

Related Skills

  • niopd-st-rice: Quantitative prioritization
  • niopd-st-moscow: Scope prioritization
  • niopd-ur-jtbd: Underlying jobs
  • niopd-ur-satisfaction: Satisfaction measurement
All versions