A Kano survey template helps you find out how individual product or service features affect customer satisfaction. It pairs a question about having a feature with a question about not having it, then uses the two answers to classify the feature as something customers expect, value, do not care about, or may actively dislike.
What a Kano Survey Measures
The Kano model is a way to understand how customers respond to specific attributes, rather than simply asking them to rate an entire product. A customer may be pleased by a quick checkout, for example, but take a working checkout for granted. Another feature, such as a novel customization option, might delight some people even though they did not expect it.
The model is associated with quality researcher Noriaki Kano and colleagues. Its central insight is that satisfaction does not always rise in a straight line with feature performance. Some attributes prevent dissatisfaction when present; others increase satisfaction as their performance improves; still others create a pleasant surprise. A Kano survey is useful when a team needs to distinguish these different expectations before deciding what to improve or build.
It is not a general-purpose satisfaction survey, a vote on which feature is most popular, or proof that a proposed feature will succeed. It provides a structured view of stated reactions to particular features. Teams should interpret it alongside customer context, feasibility, and other evidence.
How the Paired Questions Work
For each feature, respondents answer two questions. The functional question asks how they would feel if the product had the feature. The dysfunctional question asks how they would feel if it did not. Both questions use the same answer choices, typically: I like it that way; I expect it that way; I am neutral; I can live with it that way; and I dislike it that way.
For example, a service might ask about appointment reminders:
- Functional: If the service sent you a reminder before an appointment, how would you feel?
- Dysfunctional: If the service did not send you a reminder before an appointment, how would you feel?
The pair matters because a positive response to the first question alone cannot show whether the feature is essential, merely welcome, or unimportant. The second answer adds the missing contrast. Each respondent’s answer pair is looked up in a Kano evaluation matrix to assign a category. When the answers are inconsistent or do not fit the usual pattern, the result may be recorded as questionable rather than forced into a meaningful category.
Kano Survey Template
Copy this blank table into a document or spreadsheet. Replace the example feature wording with one clear attribute at a time. Give respondents the same five answer choices for both questions: I like it that way; I expect it that way; I am neutral; I can live with it that way; I dislike it that way. Leave the classification blank until you have applied a consistent evaluation matrix.
| Respondent ID | Feature or attribute | Functional question answer | Dysfunctional question answer | Kano category | Optional comment |
|---|---|---|---|---|---|
Sample only—fictional details: Respondent F-014; feature: appointment reminder by text; functional answer: “I expect it that way”; dysfunctional answer: “I dislike it that way”; category: must-be; comment: “I want a reminder the day before.” This one response is an illustration, not a finding about customers generally. In a real study, classify all valid response pairs and look at the distribution across participants.
What the Kano Categories Mean
- Must-be (basic): Customers generally expect the attribute. Having it may not generate much praise, while its absence can cause strong dissatisfaction. A reliable way to complete a basic transaction is a common kind of example, though expectations depend on the audience and context.
- One-dimensional (performance): Satisfaction tends to rise as the attribute improves, and fall when it performs poorly. Shorter waiting times or more accurate search results could behave this way for a particular group.
- Attractive (delighter): Customers may not expect the attribute, but its presence can please them. Its absence is often tolerated. A useful surprise feature may fit this pattern, but novelty alone does not make a feature a delighter.
- Indifferent: The attribute makes little difference to satisfaction for the people surveyed. That does not automatically mean it has no value to any customer or in any situation.
- Reverse: Some respondents prefer the attribute not to be present. This can reflect differing tastes, contexts, or a feature that adds unwanted complexity. Investigate who gave these answers rather than assuming the whole audience agrees.
- Questionable: The answer combination does not produce a useful, internally consistent classification under the matrix. Confusing wording, misunderstood questions, or an accidental response can contribute; review the item and response data.
These labels describe patterns in answers, not permanent truths about a feature. A delighter can become an expectation as customers get used to it, and different segments can classify the same attribute differently.
Scoring and Reading the Results
Use the same published or documented Kano evaluation matrix throughout the analysis. The matrix maps each combination of functional and dysfunctional answer choices to a category. Do not assign categories by intuition after seeing which result seems convenient. Because matrix layouts and category abbreviations can vary in presentation, keep a copy of the exact mapping with the survey records.
For each feature, count the valid classifications and report the number of responses as well as the share in each category. A feature with 12 responses is not on equal footing with one answered by 200 people, and a close split can be more informative than a single label. Some teams also calculate satisfaction and dissatisfaction coefficients from category counts. If using such measures, state the formula and denominator clearly; conventions can differ, and the figures should not be presented as precise forecasts of business impact.
Interpret the pattern with comments and customer segments in view. If one group sees a feature as essential while another sees it as unnecessary, an overall average can conceal the difference. A high must-be share may justify protecting basic quality, while a high attractive share may suggest an opportunity to test a differentiating experience. Neither classification alone tells you development cost, strategic fit, accessibility implications, or the size of the opportunity.
Choosing Features and Writing Neutral Items
Survey a manageable set of attributes that respondents can understand and judge. Each item should describe one feature, in plain language, without embedding a benefit claim. “The booking page shows available times before you enter personal details” is more specific than “A much easier booking experience.” The latter combines several possible improvements and leads respondents toward a favorable answer.
Before sending the survey, check that each attribute is:
- Specific: Respondents can picture what is included and what is not.
- Single-purpose: It does not bundle unrelated features into one question.
- Relevant: The people receiving the survey have enough experience or context to answer.
- Balanced: The wording does not imply that one answer is more desirable.
- Distinct: It is not a near-duplicate of another attribute in the questionnaire.
Consider adding a short, neutral definition where a technical term could be interpreted in different ways. If respondents have not used the product, frame the questions around a clearly described concept and be cautious about treating imagined reactions as actual experience.
Common Problems and How to Avoid Them
A frequent mistake is asking only whether customers want a feature. That misses the difference between an expected basic and a surprising extra. Another is using vague wording: people cannot reliably answer a paired question if they imagine different versions of the feature. Keep the description identical in both questions; change only whether the attribute is present.
Long surveys can also encourage rushed or repetitive answers. Prioritize the attributes that matter to the decision, group related items logically, and pilot the questionnaire with a few people who resemble the intended respondents. Ask them to explain what they thought each feature meant. A pilot can expose ambiguity that a spelling check will not.
Do not discard reverse or questionable results merely because they complicate the story. Check whether a feature is unwanted by a particular segment, whether the prompt is unclear, or whether a response was incomplete. Also avoid treating a category as a priority ranking. A must-be feature may be crucial to protect, while an attractive feature could be worth exploring; costs, customer reach, dependencies, and strategic goals still matter.
When to Use Kano—and What It Does Not Replace
Kano analysis is most useful when a team has a set of candidate attributes and needs to understand the kind of satisfaction each might influence. It can support early product discovery, service redesign, or a review of customer expectations. It is less suited to measuring overall satisfaction over time, diagnosing every cause of a poor experience, or estimating willingness to pay.
Compared with a simple importance rating, Kano asks about both presence and absence, revealing whether a feature behaves like a basic expectation or a potential delight. Compared with open-ended interviews, it is easier to summarize across a larger group, but offers less depth about why people feel as they do. These methods can complement each other: interviews can identify attributes worth testing, a Kano survey can classify reactions, and follow-up research can explore trade-offs and real-world behavior.
Use the results as one input to prioritization, not as an automatic roadmap. A feature that scores as attractive may still be too costly, confusing, or irrelevant to the target market. A feature classified as indifferent in one sample could matter greatly to a smaller audience or under different conditions.
Frequently Asked Questions
What are the standard answer choices in a Kano survey?
The common five are “I like it that way,” “I expect it that way,” “I am neutral,” “I can live with it that way,” and “I dislike it that way.” Use matching choices for both the functional and dysfunctional question.
How many features should a Kano questionnaire include?
There is no universal ideal number. Include enough attributes to answer the decision at hand, but keep the survey short enough for careful responses. Pilot the length and wording with representative participants rather than relying on a fixed rule.
Can one feature have more than one Kano category?
Yes. Individual respondents can classify the same feature differently, and the overall results may be mixed. Report the distribution and, where useful, examine meaningful customer segments instead of hiding variation behind one label.
Is a Kano survey the same as a customer satisfaction survey?
No. A satisfaction survey usually measures perceptions or experiences, while Kano pairs hypothetical or experience-based feature-presence questions to classify attribute effects. A Kano survey does not replace ongoing satisfaction measurement.
Does a delighter always stay a delighter?
No. Expectations can change as a feature becomes familiar or common. Repeat research when the market, audience, or product context changes, and avoid treating an old classification as permanent.