Features create different kinds of value

01Feature requests are being built without a clear view of customer value.

02Treating every feature as equally important obscures real priorities.

03Adding more features does not always increase satisfaction.

04Essential features and delight features require different strategies.

Kano classifies features by their effect on satisfaction and clarifies investment priorities.

FROM SETUP TO FIELDWORK

List the features. Each one becomes a functional/dysfunctional pair.

No separate preview step — every feature you add updates the exact pair respondents see on the right.

createsurvey · kano-model

Kano Model

PriorityCustom tasks · min. 50 respondents

Features to evaluate

1Fast loading speed×

2Dark mode×

3Mobile app×

+ Add feature

Shared response options (not a score)

Kano scoring classifies the combination of "with the feature" and "without it" answers, not a score — the same options apply to every feature.

·I like it

·I expect it

·I'm neutral

·I can tolerate it

·I dislike it

Apply to survey

Live

Live preview

Question 3 of 11

If Fast loading speed was NOT there, how would you feel? *

I like it

I expect it

I'm neutral

I can tolerate it

I dislike it

‹ Previous

* Required

Next ›

Left: the feature list every Kano study starts from. Right: exactly what respondents see — the functional/dysfunctional pair for each feature.

FROM RESPONSES TO RESULTS

Feature roles in customer satisfaction

Every figure below comes from one real example study — 180 respondents classifying six features, computed by the same engine your own survey runs on.

Classification process

The scale, the classification table, the resulting category split and how clean the answers were.

Design & data qualityA·O·M·I·R·Q

Respondents180

Features rated6

Scale5-point functional pair

ClassificationKano table (A·O·M·I·R·Q)

Questionable answers1.8%

Mean classification strength46%

Lifecycle-risk features1

M 1O 1A 2I 1R 1

Feature categories

Satisfaction if present crossed with dissatisfaction if absent sorts every feature into a quality type.

Better-Worse matrix4 quadrants

Better →← |Worse|

M Must-be — keep the standardO Performance — invest in proportionA Attractive — a chance to stand outI Indifferent — neither helps nor hurtsR Reverse — some would rather not have it

Satisfaction and dissatisfaction effects

Plot satisfaction and dissatisfaction effects on one scale to distinguish basic expectations from features that increase satisfaction.

Feature classificationWorse ← → Better

Fast loading speed

Mobile app

Offline access

Real-time notifications

In-app AI assistant

Dark mode

Left is the dissatisfaction if the feature is missing; right is the satisfaction if it is there. The badge is the final class.

Development priorities

The upside of shipping it and the risk of skipping it combine into one ranked list.

Improvement priorityBetter × |Worse|

Mobile app

0.374

Fast loading speed

0.179

Offline access

0.152

Real-time notifications

0.148

In-app AI assistant

0.096

Dark mode

0.040

Score = Better × |Worse| — the upside of having it and the risk of not, in one number.

Investment strategy by category

Use each Kano category to guide maintenance, investment, differentiation, and communication priorities.

Strategy by category4 types in use

MMust-be — keep the standard

Absence turns straight into complaints; presence adds nothing. Hold it steady rather than over-invest.

Fast loading speed

OPerformance — invest in proportion

Satisfaction rises with what you put in. The wider the gap over rivals, the bigger the edge.

Mobile app

AAttractive — a chance to stand out

Nobody complains without it, but having it lifts satisfaction sharply. Good headline material.

Offline access · Real-time notifications

RReverse — shipping it costs you

More respondents dislike having it than want it. Make it optional, or leave it out.

In-app AI assistant

Feature roadmap

The report summarizes practical implications and identifies features that are becoming expected over time.

ConclusionsN = 180

1"Mobile app" is the top investment candidate (score 0.374), classed as performance quality.

2"Offline access" carries lifecycle risk (attractive with CS ≥ 0.6) — it will likely drift into an expectation.

3"Real-time notifications" splits attractive 35% / indifferent 34% — resampling keeps the class only 57% of the time, so treat it as unsettled rather than decided.

4"In-app AI assistant" lands as reverse quality — 80 of 180 would rather not have it, so shipping it by default costs more than it adds.

A COMPLETE REPORT

See the full report from summary to conclusion.

The six cards above are fragments of this. Scroll the real output end to end, right here on the page.

Kano model — 6 features · 180 simulated respondents

Kano Model · Feature Requirement Analysis

6 features classified from 180 valid responses.

Executive Summary

180 respondents · 6 features

This Kano study classified 180 respondents' ratings across 6 candidate features. The most common classification is Attractive (2 of 6 features), and 2 features offer differentiation potential as Attractive quality. "Mobile app" ranks highest for improvement priority (Better × |Worse| = 0.374), classified One-dimensional. Notably, "Fast loading speed" is a Must-be feature but shows a low satisfaction coefficient of 0.2267 — its baseline execution needs attention.

Study Design & Data Quality

Metric	Value
Respondents	180
Features evaluated	6
Question scale	5-point (like–expect–neutral–tolerate–dislike)
Classification method	Kano evaluation table (A·O·M·I·R·Q)
Category distribution	M 1 · O 1 · A 2 · I 1 · R 1 · Q 0
Questionable rate	1.8%
Avg. classification strength	45.7%
Lifecycle-risk features	1

Improvement priority

Priority was set by looking together at the reaction that satisfaction rises when the feature is present and the reaction that its absence is felt as an inconvenience. The longer the bar, the more both reactions appeared.

Must-be (M)One-dimensional (O)Attractive (A)Indifferent (I)Reverse (R)

Interpretation

"Mobile app" is the top investment priority (score 0.374), classified as One-dimensional.

Feature map

The horizontal axis is how much the inconvenience grows when the feature is absent; the vertical axis is how much satisfaction rises when it is present. Where a point sits shows what role the feature plays for the customer.

Must-be (M)

Fast loading speed

One-dimensional (O)

Mobile app

Indifferent (I)

Dark mode

Attractive (A)

Offline access, Real-time notifications

Answers by feature

Shows the answers for each feature split into Kano’s six types. The figure in brackets is the share of respondents who chose that type; the last two columns give the most frequent type and a reference range for its share.

Feature	Must-be	One-dimensional	Attractive	Indifferent	Reverse	Questionable	Most frequent type	Reference range
Fast loading speed	103(57.2%)	33(18.3%)	6(3.3%)	30(16.7%)	5(2.8%)	3(1.7%)	Must-be57.2%	50~64.4%
Dark mode	9(5%)	10(5.6%)	52(28.9%)	101(56.1%)	7(3.9%)	1(0.6%)	Indifferent56.1%	48.9~63.3%
Mobile app	42(23.3%)	65(36.1%)	36(20%)	27(15%)	3(1.7%)	7(3.9%)	One-dimensional36.1%	29.4~43.3%
Offline access	17(9.4%)	25(13.9%)	82(45.6%)	48(26.7%)	4(2.2%)	4(2.2%)	Attractive45.6%	38.3~53.3%
Real-time notifications	18(10%)	29(16.1%)	63(35%)	61(33.9%)	8(4.4%)	1(0.6%)	Attractive35%	28.3~42.8%
In-app AI assistant	20(11.1%)	5(2.8%)	31(17.2%)	41(22.8%)	80(44.4%)	3(1.7%)	Reverse44.4%	37.2~51.7%

How firm each classification is

Each feature is classified by whichever category got the most answers. This is how often the same category came out on top when the respondents were resampled.

Feature	Classification	Same category	Otherwise
Real-time notifications	Attractive	56.6%	Indifferent (43.4%)
Mobile app	One-dimensional	98.1%	Must-be (1.7%)
Fast loading speed	Must-be	100%	—
Dark mode	Indifferent	100%	—
Offline access	Attractive	100%	—
In-app AI assistant	Reverse	100%	—

1 feature(s) kept the same category in fewer than 80% of 1000 resamples — Real-time notifications 56.6%, otherwise Indifferent. For these the category is a close call rather than a property of the feature: read the answer counts behind it before planning off the label, and ask again with more respondents if the plan depends on it.

Improvement direction by feature type

Points to look at when improving, organised by feature type.

Must-be — Keep to Standard

Absence causes sharp dissatisfaction, but presence adds little delight. Maintain reliably rather than over-invest.

Features: Fast loading speed

One-dimensional — Invest Proportionally

Satisfaction rises in proportion to investment. A real competitive lever — the more you improve it relative to competitors, the more it pays off.

Features: Mobile app

Attractive — Differentiation Opportunity

Absence causes little complaint, but presence delights disproportionately. Ideal as a headline feature in marketing.

Features: Offline access · Real-time notifications

Indifferent — Reallocate Resources

Little effect on satisfaction either way. Redirect development resources toward Performance or Attractive features.

Features: Dark mode

Conclusions & next steps

The features to look at first in these answers, and what to do next.

"Mobile app" is the top investment priority (score 0.374), classified as One-dimensional.

2 features are classified Attractive (Offline access, Real-time notifications) — a relatively rich set of differentiation candidates for the next release.

"Fast loading speed" is already classified Must-be but shows a low satisfaction coefficient — its execution quality (not new investment) needs attention first.

1 feature (Dark mode) show low impact on satisfaction either way — reallocating their development budget toward Attractive or One-dimensional features is worth considering.

1 feature classified Reverse (In-app AI assistant) — respondents preferred its absence; re-validate the question wording and the feature's rationale before building it.

Offline access show lifecycle risk (Attractive with CS ≥ 0.6) — as adoption spreads, expect these to drift toward One-dimensional baseline expectations, so keep improving them rather than treating them as a one-time win.

Methodology — Classification is based on the Kano evaluation table applied to each response's functional/dysfunctional answer pair (max-frequency rule, tie-break M > O > A > I). CS (Better) = (A+O) ÷ (A+O+M+I); DS (Worse) = −(M+O) ÷ (A+O+M+I); Priority score = CS × |DS|. Minimum 5 valid responses required per feature.

Scroll to explore the full report

IN THE REPORT

What customers expect and value

Separate basic expectations from true delight, then invest in the features that move satisfaction.

Classification results

Must-be, Performance, Attractive, Indifferent, Reverse.

Better-Worse map

CS / DS coefficients plotted for every feature.

Opportunity score

Investment priority by satisfaction potential.

Portfolio matrix

Position features on a priority quadrant.

Feature roadmap

Set the development order and timing for each feature.

Migration analysis

How categories may shift over the lifecycle.

Segment view

Compare classifications across respondent groups.

Auto interpretation

Plain-language reading of the priorities.

ALSO IN SURVEY ANALYSIS

More survey methods

Each method answers a different question — same interface, different lens.

OPP · IDP · PSM

Van Westendorp PSM

Turn four price questions into OPP, IDP, elasticity, revenue simulation, and competitor benchmark.

AHP · CR · 5 levels

AHP Priority

Turn pairwise comparisons into eigenvalue weights with up to 5 hierarchy levels and segment analysis.

WTP · Part-worth

CBC Conjoint

Measure attribute importance and willingness to pay with choice-based conjoint analysis.

IPA · Regression

Driver Analysis

Find which attributes drive overall satisfaction or NPS using importance-performance analysis.

Recall · Image

Brand Awareness

Track unaided and aided brand recall, brand image dimensions, and competitive positioning.

eNPS · Pulse

Employee Engagement

Measure and benchmark employee engagement, satisfaction, and eNPS across teams.

Build the right features first

Separate basic expectations from performance features and unexpected delights, then turn the result into a practical product roadmap.

Get started See pricing

No credit card required6 Kano categories supported

Prioritize features by customer value.

Features create different kinds of value

List the features. Each one becomes a functional/dysfunctional pair.

Feature roles in customer satisfaction

Classification process

Feature categories

Satisfaction and dissatisfaction effects

Development priorities

Investment strategy by category

Feature roadmap

See the full report from summary to conclusion.

Improvement priority

Feature map

Answers by feature

How firm each classification is

Improvement direction by feature type

Must-be — Keep to Standard

One-dimensional — Invest Proportionally

Attractive — Differentiation Opportunity

Indifferent — Reallocate Resources

Conclusions & next steps

What customers expect and value

More survey methods

Van Westendorp PSM

AHP Priority

CBC Conjoint

Driver Analysis

Brand Awareness

Employee Engagement

Build the right features first

Improvement priority

Feature map

Answers by feature

How firm each classification is

Improvement direction by feature type

Must-be — Keep to Standard

One-dimensional — Invest Proportionally

Attractive — Differentiation Opportunity

Indifferent — Reallocate Resources

Conclusions & next steps

Prioritize features by
customer value.