> ## Documentation Index
> Fetch the complete documentation index at: https://meta.niceshare.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Kano Model

> Kano Model classifies features by how they affect customer satisfaction. Learn must-be, performance, and delighter priorities with practical product strategy.

<Info>
  **Category**: Models<br />
  **Type**: Customer Satisfaction Prioritization Model<br />
  **Origin**: Noriaki Kano and colleagues, 1984<br />
  **Also known as**: Kano Analysis, Attractive Quality Model
</Info>

<Note>
  **Quick Answer** — The Kano Model is a product decision framework that sorts features into categories based on how their presence or absence affects satisfaction. Proposed by Noriaki Kano in 1984, it distinguishes must-be basics, performance drivers, and delighting attributes. The key insight is strategic sequencing: fix basics first, optimize performance next, then selectively invest in delighters.
</Note>

## What is Kano Model?

The Kano Model is a way to prioritize product and service attributes by satisfaction impact rather than by effort, politics, or loudest stakeholder opinion.

> "Not all quality attributes create satisfaction in the same way." — Noriaki Kano (attractive quality framework)

Its core categories are straightforward: **Must-be** attributes prevent dissatisfaction but rarely create praise; **Performance** attributes improve satisfaction linearly; **Attractive** attributes create delight when present but are not expected when absent. The model also includes indifferent and reverse attributes, helping teams avoid waste.

### Kano Model in 3 Depths

* **Beginner**: Fast login is often a must-be. Better battery life is performance. A surprising, useful automation feature can be an attractive delighter.
* **Practitioner**: Use paired functional/dysfunctional survey questions to classify each feature before roadmap planning.
* **Advanced**: Re-run Kano segments quarterly because attractive features often decay into must-be expectations as markets mature.

## Origin

The Kano Model was introduced in 1984 in the paper *Attractive Quality and Must-Be Quality* by Noriaki Kano, Nobuhiko Seraku, Fumio Takahashi, and Shin-ichi Tsuji in the *Journal of the Japanese Society for Quality Control*. Their work challenged one-dimensional quality assumptions by showing that satisfaction and dissatisfaction are not mirror images.

The original framework used structured questionnaires to classify attributes in products such as televisions and table clocks, then map them into quality categories. This shift influenced modern product operations, especially when used with `/models/swot-analysis`, `/models/diffusion-of-innovation`, and evidence loops from `/models/feedback-loops`.

## Key Points

Kano becomes practical when teams treat it as a sequencing system for product investment.

<Steps>
  <Step title="Must-be failures erase trust quickly">
    Missing basics do not just reduce ratings; they trigger sharp dissatisfaction and churn risk. Reliability, safety, and clarity usually belong here.
  </Step>

  <Step title="Performance attributes are your negotiation surface">
    Customers compare alternatives on these dimensions. Faster, cheaper, and more accurate execution in this layer directly influences willingness to pay.
  </Step>

  <Step title="Attractive features create strategic differentiation">
    Delighters are most valuable when they solve a hidden pain elegantly. They are not gimmicks; they should feel meaningful, not decorative.
  </Step>

  <Step title="Category drift is inevitable">
    Today's delighter becomes tomorrow's baseline. Teams should schedule recurring reclassification instead of freezing assumptions.
  </Step>
</Steps>

## Applications

Use Kano to turn feature debates into testable portfolio decisions.

<CardGroup cols={2}>
  <Card title="Roadmap Prioritization">
    Split backlog items into must-be, performance, and attractive buckets before scoring. This prevents overfunding flashy features while core reliability is still weak.
  </Card>

  <Card title="Voice-of-Customer Research">
    Add Kano questions to interviews and surveys so teams capture asymmetric reactions, not just average ratings.
  </Card>

  <Card title="Release Planning">
    Gate launches on must-be completion first. Then choose one performance improvement and one delighter per cycle to balance trust and momentum.
  </Card>

  <Card title="Cross-Functional Alignment">
    Product, design, and engineering can use Kano categories as shared language when negotiating scope, quality, and delivery dates.
  </Card>
</CardGroup>

## Case Study

A 2024 Gen Z smartphone preference study applying the Kano framework analyzed 16 attributes and classified them into five quality types, including 5 must-be attributes, 2 performance attributes, and 6 attractive attributes. The result was practical rather than theoretical: teams could immediately see which features were baseline expectations and which could create differentiation.

The study's recommended configuration (for that segment) included a 5000mAh battery, 8GB RAM, 128GB storage, and a 6.7-inch display, illustrating how Kano converts vague "user needs" into concrete design trade-offs. The measurable indicator here is the attribute distribution itself: category counts revealed that most candidate features were not equal in strategic value.

## Boundaries and Failure Modes

Kano classification is not permanent truth. Segment differences can invert categories, and weak survey design can misclassify features. Another failure mode is using Kano without feasibility constraints: teams may over-invest in attractive features that are costly but weakly linked to retention. Kano should be paired with delivery and economics checks, not used in isolation.

## Common Misconceptions

Many Kano failures come from good intentions combined with shallow execution.

<AccordionGroup>
  <Accordion title="Delighters should always come first">
    If basics are unstable, delighters cannot compensate. Start with must-be reliability before adding excitement.
  </Accordion>

  <Accordion title="Kano is a one-time workshop">
    Customer expectations move. Reclassification cadence is part of the method, not optional overhead.
  </Accordion>

  <Accordion title="High survey scores equal high strategy value">
    A feature can be liked but strategically indifferent. Kano focuses on satisfaction asymmetry, not just popularity.
  </Accordion>
</AccordionGroup>

## Related Concepts

Kano is strongest when connected to models for competition, diffusion, and decision execution.

<CardGroup cols={3}>
  <Card title="SWOT Analysis" href="/models/swot-analysis">
    Align satisfaction priorities with strategic strengths and threats.
  </Card>

  <Card title="Diffusion of Innovation" href="/models/diffusion-of-innovation">
    Understand how delighters move from novelty to expectation over time.
  </Card>

  <Card title="Cynefin Framework" href="/models/cynefin-framework">
    Match feature decisions to context complexity before committing.
  </Card>

  <Card title="Decision Tree" href="/models/decision-tree">
    Evaluate roadmap choices under cost, risk, and timing uncertainty.
  </Card>
</CardGroup>

## One-Line Takeaway

<Tip>
  Build trust by fixing must-be basics first, then win preference through selective performance gains and meaningful delighters.
</Tip>