Must Be, the basic features. Customers expect it to be there. Presence earns no satisfaction, absence causes strong dissatisfaction. The example in the skill is clean bedding in a hotel: an illustration of an expected basic condition, not a prediction of a particular review. The consequence for your roadmap is counterintuitive: prioritise validated expectations, then assess reliability, accessibility, safety and other requirements before deciding whether to invest further.
One Dimensional, the performance features. The conceptual model associates better fulfilment with greater satisfaction, not a measured straight-line relationship. Specify direction for speed, battery life or price; a higher price is not automatically better. Choosing two or three is a focus convention. A linear satisfaction sketch says nothing about the cost of each improvement.
Attractive, the wow features. Customers do not expect it. The feature can delight respondents, while loyalty remains a separate outcome to measure. The example from the file is the handwritten note included with an online order. The rule the skill attaches to it is sharp: consider one or two at a time as a scope convention, but estimate actual cost and complexity; attractive does not mean cheap.
Indifferent, the neutral features. The customer does not care either way. Whether it is there or not makes no difference. These are often internal features the team is proud of but which the customer never sees. Consider deferral or removal only after checking other segments and operational, accessibility or mandatory dependencies. Survey indifference does not measure wasted capacity.
Reverse, the reverse features. Presence leads to dissatisfaction. Too many notifications, too many onboarding steps, functions that mainly get in the way. Actively remove them or make them switchable per segment, because what one group experiences as Reverse can be a wow feature for another.
There is a sixth outcome, and it is not a category: Q for Questionable. It appears when the two answers contradict each other. The skill is not allowed to make anything of that either. It asks the question again or marks the feature as undetermined, and that is a result, not a problem.
These are shortened hypotheses from the worked example, not measured customer findings. The table preserves a distinction between a proposed category and the decision to develop, defer or investigate an item.
--- roadmap-meeting.txt
+++ kano-analysis.md # hypothetical pairs and categories; proposed actions and unverified drift
Dark mode is a quick win, let's add it in.
Dark mode: hypothetical neutral/neutral gives Indifferent; defer pending segment and accessibility checks.
Our AI categorisation is our big differentiator.
AI categorisation: One Dimensional hypothesis; validate improvements. A two-year drift scenario is unverified.
The bank connection is finished, customers are going to be pleased with that.
Bank integration: Must Be hypothesis. Validate expectations and reliability needs; customer loss is not guaranteed.