kano-model
/kano-model
Use when deciding which customer needs or service features drive satisfaction, dissatisfaction, or differentiation. Use when applying the Kano Model consulting method and when a user asks for Kano Model, method execution, structured diagnosis, or action planning.
- Author
- fzfclee ↗
- Repository
- consulting-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 10.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 10.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when deciding which customer needs or service features drive satisfaction, dissatisfaction, or differentiation. Use when applying the Kano Model consulting method and when a user asks for Kano Model, method execution, structured diagnosis, or action planning.
Original author description
Use when deciding which customer needs or service features drive satisfaction, dissatisfaction, or differentiation. Use when applying the Kano Model consulting method and when a user asks for Kano Model, method execution, structured diagnosis, or action planning.
How it works
- Method Notes
- Required Inputs
- When Not To Use
- Adjacent Methods
- Step-by-Step Execution
- Output Template
- Quality Gate
SKILL.md preview
--- name: kano-model description: Use when deciding which customer needs or service features drive satisfaction, dissatisfaction, or differentiation. Use when applying the Kano Model consulting method and when a user asks for Kano Model, method execution, structured diagnosis, or action planning. license: Apache-2.0 --- # Kano Model Use this skill to run `Kano Model` as a practical consulting method, not as a generic framework explanation. ## Method Notes - Classify features as must-be, performance, delighter, indifferent, or reverse. - Kano categories shift over time; mark evidence age. - Pair functional (present) and dysfunctional (absent) reactions. Qualitative logic: expected presence with disliked absence suggests must-be; satisfaction with presence and dissatisfaction with absence suggests performance; liked presence with acceptable/neutral absence suggests delighter; little reaction either way suggests indifferent; disliked presence with preferred absence suggests reverse. - State mode: qualitative evidence gives tentative categories; a standardized survey uses paired response options and a documented evaluation mapping. These qualitative cues are not a substitute for that mapping. Retain contradictory pairs, subgroup differences and ties as mixed / unclear unless a stated grouping/aggregation rule resolves them; do not force one class or a universal tie-break. - Basis: [ASQ Kano model](https://asq.org/quality-resources/kano-model) and [Society of Sensory Professionals classification and paired questionnaire](https://www.sensorysociety.org/knowledge/sspwiki/Pages/Kano%20Modeling%20in%20Product%20Development.aspx). ## Required Inputs Collect or infer these inputs before execution: - features or service attributes - customer segment - satisfaction evidence - dissatisfaction evidence If an input is missing, do not block automatically. Mark it as `missing`, state the assumption used, and add a validation action. ## When Not To Use Do not use without a defined customer context and evidence of how feature presence and absence affect satisfaction. Kano classification alone does not set roadmap priority, cost, or sequence. ## Adjacent Methods - `jobs-to-be-done`: understand the progress the customer is trying to make. - `user-journey-mapping`: locate attributes and pain points across a chronological experience. ## Step-by-Step Execution | Step | Required input | How to execute | Output | |---|---|---|---| | Define feature set | Features/service attributes and target segment. | List attributes in customer language. | Kano item list. | | Collect satisfaction evidence | Survey/interview/VOC data for presence and absence of each item. | Capture how customers react if the attribute exists or is missing. | Functional/dysfunctional response data. | | Classify categories | Response data. | Classify must-be, performance, delighter, indifferent, or reverse. | Kano classification. | | Interpret investment | Categories, segment, maturity, cost. | Decide baseline requirements, performance investments, and differentiating delighters. | Feature priority implications. | | Refresh assumptions | Evidence age and market expectations. | Mark which classifications need revalidation over time. | Kano review plan. | ## Output Template ```markdown ### 1. Scope And Evidence Customer segment: Decision: Attributes tested: Research basis: Mode, response mapping, and grouping / aggregation rule: ### 2. Classification | Attribute | Functional response | Dysfunctional response | Kano class | Confidence | |---|---|---|---|---| | | | | | | ### 3. Investment Logic | Attribute | Current performance | Priority | Reason | |---|---|---|---| | | | | | ### 4. Refresh Plan | Assumption | Validation | Owner | Timing | Reclassification trigger | |---|---|---|---|---| | | | | | | ### Evidence And Next Decision - Confirmed facts: - Assumptions: - Missing evidence: - Next action, owner, and timing: - Expected signal and decision threshold: ``` ## Quality Gate - Produce the method-specific outputs for Scope And Evidence, Classification, Investment Logic; do not substitute a generic framework summary. - Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption. - Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method. - Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal. - State missing inputs and the smallest validation action instead of inventing precision. - Preserve tentative, mixed / unclear and reverse reactions; for standardized survey claims, name the evaluation mapping used and handle inconsistent/questionable responses explicitly. - Keep wording professional and plain enough that a smart non-specialist can use the output directly.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · fzfclee/consulting-skills | 100 | Apache-2.0 |
| jacob-balslev/skill-graph | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version eba65cafc29b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100competitive-positioning
Use when a strategy, offer, pitch, or account plan needs sharper differentiation. Use when applying the Competitive Positioning consulting method and when a user asks for Competitive Positioning, method execution, structured diagnosis, or action planning. - 100go-to-market-diagnosis
Use when a product, service, or consulting offer needs market entry, growth, or conversion improvement. Use when applying the Go To Market Diagnosis consulting method and when a user asks for Go To Market Diagnosis, method execution, structured diagnosis, or action planning. - 100s4-16-kano-model
Classifies product features as must-be, one-dimensional, attractive, indifferent or reverse from paired survey questions. Use when deciding which features to build, keep or drop. - 100kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this… - 100product-discovery
Product discovery and market research expert. Use when validating product ideas, conducting market research, user interviews, competitive analysis, or opportunity assessment. Covers JTBD, Kano model, and Value Proposition Canvas. - 100value-proposition-design
Design a product value proposition using the Value Proposition Canvas (jobs, pains, gains, pain relievers, gain creators) and the Kano model. Use when the user asks to write a value proposition, map pains and gains to product features, apply VPC, distinguish…