Project & Development
Kano Model for Beginners: Sort Features by 2 Questions and Pick What to Build First
Beginner | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Beginner: No technical terms. Just answer the whiteboard's questions, following the examples, and it takes shape.
The Kano model sorts features into 5 quality types with two questions, then sets the build order.
Read more Show less
List candidate features and ask users two questions for each, with it and without it, answered as pleased, neutral, or bothered. Find each quality in the quick chart and count people. Build must-be gaps first, then one-dimensional, then attractive features. Ask again when answers contradict, such as pleased to both. The model comes from the paper "Attractive Quality and Must-be Quality" by Noriaki Kano et al. (Hinshitsu, vol. 14, no. 2, 1984); this template narrows the answers to three choices.
Unlike importance-and-urgency ranking, it separates needs from mere delights. Plan on 5 to 10 users, about 10 minutes each for 6 features.
The whiteboard has 4 A4 pages: set the goal and features, record answers, sort into 5 types, assign what to build. The example reorders upgrades to an internal supply-request tool. The task board has 5 columns, 4 parent tasks, and 12 subtasks.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Kano Model Feature Quality Sorting Board
How to use (4 pages): ① Page 1: set the goal, list features, read the chart (boards①–⑤) → ② Page 2: ask 5 users two questions, fill the table (boards⑥–⑦) → ③ Page 3: sort answers into 5 types, vote on what to build (boards⑧–⑩) → ④ Page 4: set owners, due dates, and a re-ask date (boards⑪–⑭)
1/4 Set the goal and features
① Goal, timing, people (start here)
- Goal e.g. Decide the order of fixes to our internal supply-request tool over the next six months
- Timing e.g. The third week of November, 10 minutes per person during breaks
- Participants e.g. 4 people from IT ask the questions; 3 factory users and 2 office users answer
② Candidates (applying)
- How to fill in: write one at a time, as something the tool can do
- e.g. Apply from a phone
- e.g. Copy the last request and send it
③ Candidates (approval, contact)
- How to fill in: also write what users or other teams asked for
- e.g. Get a notice when a request is approved
- e.g. Require a reason on every request (asked by accounting)
④ Candidates (stock, delivery)
- How to fill in: skip what the current tool already has
- e.g. See stock counts on the request screen
- e.g. See an estimated delivery date
⑤ Quick chart (with × without answers into 5 types)
| Pleased without it | Neutral without it | Bothered without it | |
|---|---|---|---|
| Pleased with it | Contradictory (ask again) e.g. answered "pleased" to both | Attractive (nice to have) e.g. charging at the cafe seat | One-dimensional (better = happier) e.g. fast Wi-Fi at the cafe |
| Neutral with it | Reverse (unwelcome if present) e.g. a sign-up demand on every visit | Indifferent (no difference) e.g. a new flyer by the register | Must-be (a problem if missing) e.g. the cafe Wi-Fi connects |
| Bothered with it | Reverse (unwelcome if present) e.g. loud music at your seat | Reverse (unwelcome if present) e.g. a survey pops up at every order | Contradictory (ask again) e.g. answered "bothered" to both |
2/4 Record answers in a table
⑥ Answers per feature from ②–④ (with / without)
| Factory user 1 | Factory user 2 | Factory user 3 | Office user 1 | Office user 2 | |
|---|---|---|---|---|---|
| Apply on phone | e.g. pleased/neutral | e.g. pleased/neutral | e.g. pleased/bothered | e.g. neutral/neutral | e.g. pleased/neutral |
| Copy last request | e.g. pleased/neutral | e.g. neutral/neutral | e.g. pleased/neutral | e.g. pleased/neutral | e.g. pleased/pleased |
| Approval notice | e.g. neutral/bothered | e.g. neutral/bothered | e.g. pleased/bothered | e.g. neutral/bothered | e.g. neutral/bothered |
| Required reason | e.g. bothered/neutral | e.g. bothered/neutral | e.g. neutral/neutral | e.g. bothered/pleased | e.g. neutral/neutral |
| Stock display | e.g. pleased/bothered | e.g. pleased/bothered | e.g. pleased/bothered | e.g. neutral/bothered | e.g. pleased/neutral |
| Delivery date shown | e.g. neutral/neutral | e.g. neutral/neutral | e.g. pleased/neutral | e.g. neutral/neutral | e.g. neutral/bothered |
⑦ Reasons for answers, things to re-ask
- Reasons for answers (factory) e.g. Without a notice, I walk to the office to ask if it was approved (factory user 1, approval notice)
- Reasons for answers (office) e.g. Writing a reason every time slows down entering a request (office user 1, required reason)
- Contradictory answers and what to ask again e.g. Office user 2 answered pleased to both for copying the last request. Ask again next week
3/4 Sort into 5 types and pick
⑧ Answers from ⑥ by 5 types (3 round-stamp votes each)
| Matching features | People (of 5) | In the tool now? | |
|---|---|---|---|
| Must-be | e.g. approval notice | e.g. 4 people | e.g. no (it is missing) |
| One-dimensional | e.g. stock display | e.g. 3 people | e.g. no |
| Attractive | e.g. apply on phone, copy last request | e.g. 3 people each | e.g. neither exists |
| Indifferent | e.g. delivery date display | e.g. 3 people | e.g. no |
| Reverse | e.g. required reason | e.g. 3 people | e.g. no (do not add it) |
⑨ Build order (missing must-be first)
- 1 Missing must-be e.g. Approval notice. People are bothered without it, and the current tool has none
- 2 One-dimensional e.g. Stock display. The better it gets, the happier people are
- 3 Attractive e.g. Apply on phone. Copying the last request waits until you ask again
⑩ Chosen and skipped features, reasons
- Chosen features and reasons e.g. Approval notice (4 votes), stock display (4 votes), apply on phone (3 votes). 4 people called the notice must-be, and the tool lacks it now
- Skipped features and reasons e.g. Delivery date display: 3 people are indifferent. Required reason is a reverse feature: 3 people said it would bother them
- Features to decide after asking again e.g. Copy last request (1 vote). One contradictory answer, so ask again before deciding
4/4 Assign what to build
⑪ Split the ⑩ picks into build steps
- The 3 chosen features
- Approval notice e.g. Email people when a request is approved or returned
- Stock display e.g. Show the remaining shelf count on the request screen
- Apply on phone e.g. Build a screen people can use from the factory break room
- Who tries it first e.g. 2 factory users and 1 office user try it for a week
- If short-handed e.g. Move apply on phone to the second half of the six months
⑫ What to re-ask in 6 months, and whom
- How to fill in: for each feature, write whom to ask again in one line
- e.g. Copy last request - office user 2, who is asked again next week, gets asked once more in six months
- e.g. Apply on phone - ask the 3 factory users
- e.g. Stock display - ask the same 5 people as before
⑬ How to ask (same 2 questions)
- How to fill in: ask the same questions with the same three choices
- e.g. 10 minutes per person during breaks
- e.g. Keep the answers in the same table form as ⑥
- e.g. Check whether attractive features have become must-be
⑭ Owners, due dates, and signals
- Owners and due dates (approval notice, stock display) Owner: ____ Due: __/__ e.g. Owner 1 handles the approval notice by end of December, and owner 2 the stock display by end of February
- Owners and due dates (apply on phone) e.g. Owners 3 and 4 by end of April. If hands are short, move it to the second half as in ⑪
- Date to ask again e.g. In the second week of next May, ask the people in ⑫ the way described in ⑬
- Signals (continue, change, stop) e.g. Continue: people coming to the office to ask about approval drop to 5 times a month or fewer (now about 20). Change: no drop after 3 months. Stop: nobody opens the notices. If you stop, go back to (board⑧)
Task board contents
List candidates 16 items
Decide what to ask
On page 1, write the goal, timing, and participants, list the candidate features to ask users about, and check how to read the chart. Once the features are set, you can ask users on page 2. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.
Note goal and timing
Write the goal, timing, and participants on the three notes of board①. Done when all three are filled in.
List the features
On boards②–④, write one feature to add per note, phrased as "can ...". Done when you have the same 6 as the rows of the table on page 2.
Read the chart
Read board⑤ and check which of the 5 qualities each pair of answers gives. Done when the 4 people asking agree that contradictory answers (pleased to both, bothered to both) get asked again.
Record the answers
On page 2, ask 5 users two questions per feature and jot down each answer with a one-line reason. Once the answers are in, you can sort them into 5 qualities on page 3.
Agree on wording
Agree that the 4 people asking will use the same two questions, "How would you feel if this feature existed?" and "How would you feel if it did not?", and the same three choices (pleased, neutral, bothered). Done when you write the wording on a note and stick it beside the table on board⑥.
Ask 5 users
Spend about 10 minutes per user asking the two questions for the 6 features, and write each answer in the table on board⑥ in with-it / without-it order. Done when all 30 cells are filled.
Note the reasons
Write the one-line reasons and any contradictory answers on board⑦. Done when you know whom to ask again and about which feature.
Sort into 5 types
On page 3, sort the answers into 5 qualities with the quick chart, count people, then vote with the build order as the guide to choose the features. This takes the most time because the features chosen here become the content of the six months of upgrades.
Sort and count
Match each answer on board⑥ to the quick chart on board⑤, and write each feature and its headcount on board⑧ in the row of its most common quality. Done when all 6 features sit in some row.
Order and vote
On board⑨, line up features as must-be gaps, then one-dimensional, then attractive, and have the 4 people each place 3 round stamps on the features on board⑧. Done when 12 votes are placed.
Write why you chose
On board⑩, write the chosen features and reasons, the skipped features and reasons, and the features to decide after asking again. Done when all 3 notes are filled in.
Assign what to build
On page 4, break the chosen features into build steps, then set owners, due dates, and whom to re-ask in six months and how. Track the chosen features in the "Build" column of the task board.
Map the build steps
On the branches of board⑪, write for each chosen feature what to build, who tries it first, and how to rotate work when hands are short. Done when all 5 branches are filled in.
Set owners, re-ask
Write the owner and due date for each feature on board⑭, and the features, people, and way of asking for six months later on boards⑫⑬. Done when everyone has an owner.
Decide on signals
Three months after launch, check the signals on board⑭ and decide whether to continue, change, or stop. Done when you add your decision to the signal note on board⑭.