kano-model
Skill6 starsChanged 4 months agoApache-2.0View on GitHub
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.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- tupe12334/instincttheir own version, first seen Aug 17, 2026
- flpbalada/fb-skillstheir own version, first seen Aug 3, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- flpbalada/fb-skills★ 8same name
- tupe12334/instinct★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- 5w1h-analysisSkill
- abductive-reasoningSkill
- account-planSkill
- affinity-diagramSkill
- assumption-inventorySkill
- balanced-scorecardSkill
- break-even-analysisSkill
- business-model-canvasSkill
- change-event-timelineSkill
- change-impact-analysisSkill
- communications-planSkill
- competitive-positioningSkill
- constraint-analysisSkill
- cost-benefit-analysisSkill
- critical-uncertaintiesSkill
- customer-segmentationSkill
- customer-success-health-scoreSkill
- deal-strategy-mapSkill
- decision-matrixSkill
- deductive-reasoningSkill
- effort-impact-matrixSkill
- empathy-mapSkill
- evidence-mapSkill
- fifteen-percent-solutionsSkill
- first-principles-thinkingSkill
- fishbone-diagramSkill
- five-whys-root-causeSkill
- force-field-analysisSkill
- go-to-market-diagnosisSkill
- hypothesis-treeSkill
- inductive-reasoningSkill
- issue-treeSkill
- jobs-to-be-doneSkill
- mece-frameworkSkill
- metrics-treeSkill
- mind-map-analysisSkill
- min-specsSkill
- north-star-metricSkill
- pestel-analysisSkill
- porter-five-forcesSkill
- power-interest-gridSkill
- pre-mortemSkill
- pricing-strategy-checkSkill
- raci-matrixSkill
- rice-scoringSkill
- risk-matrixSkill
- scenario-planningSkill
- service-blueprintSkill
- signal-vs-noise-filterSkill
- stakeholder-power-mapSkill
- swot-analysisSkill
- systems-thinkingSkill
- user-journey-mappingSkill
- validation-planSkill
- weighted-scorecardSkill
- win-loss-reviewSkill
- wsjf-prioritizationSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use this skill to run Kano Model as a practical consulting method, not as a generic framework explanation.
- Very specific: line 28
If an input is missing, do not block automatically.
- Distinctive: line 32
Do not use without a defined customer context and evidence of how feature presence and absence affect satisfaction.
- Distinctive: line 90
Keep wording professional and plain enough that a smart non-specialist can use the output directly.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 and Society of Sensory Professionals classification and paired questionnaire.
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
### 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

