# Kano Survey Template

Use this template after the JTBD interview pass when you already have a feature list tied to real jobs.

## Survey Rules

- Target 15-25 features max per survey
- Write every feature in customer language
- Use the same 5 response options for every question
- Pair each feature to a related job or outcome

## Response Options

- I like it that way
- I expect it that way
- I am neutral
- I can tolerate it that way
- I dislike it that way

## Feature Block Template

### Feature: [Feature Name]

[1-2 sentence description in customer language]

**Functional question**

If this feature were available in the product, how would you feel?

- [ ] I like it that way
- [ ] I expect it that way
- [ ] I am neutral
- [ ] I can tolerate it that way
- [ ] I dislike it that way

**Dysfunctional question**

If this feature were NOT available in the product, how would you feel?

- [ ] I like it that way
- [ ] I expect it that way
- [ ] I am neutral
- [ ] I can tolerate it that way
- [ ] I dislike it that way

**Optional importance rating**

How important is this feature overall?

- 1 = not important
- 5 = moderate
- 9 = critical

## Classification Reference

- Delighter: creates disproportionate delight when present
- Performance: more of it creates more satisfaction
- Must-be: expected baseline, absence hurts more than presence helps
- Indifferent: little satisfaction effect either way
- Reverse: presence creates dissatisfaction

## Feature List Worksheet

| ID | Feature | Description | Status | Related Job / Outcome |
|---|---|---|---|---|
| F1 |  |  |  |  |
| F2 |  |  |  |  |
| F3 |  |  |  |  |
| F4 |  |  |  |  |
| F5 |  |  |  |  |
| F6 |  |  |  |  |
| F7 |  |  |  |  |
| F8 |  |  |  |  |
| F9 |  |  |  |  |
| F10 |  |  |  |  |

## Description Checklist

- Uses customer language, not internal jargon
- Describes the user experience, not technical architecture
- Specific enough to evaluate
- Does not prescribe implementation detail

## Output Summary Template

| Feature | Kano Class | Confidence | Related Opportunity | Notes |
|---|---|---|---|---|
|  |  |  |  |  |
|  |  |  |  |  |
|  |  |  |  |  |

## Combined Prioritization Reminder

Kano does not replace JTBD opportunity scoring.

Use Kano to answer:
- what kind of satisfaction effect a feature creates

Use JTBD / ODI to answer:
- whether the underlying job is important and underserved