BoardSnap is an iOS app that reads a Kano model whiteboard — features plotted by satisfaction vs. implementation — and produces a structured feature classification with strategic implications.
The Kano model answers a question that standard prioritization frameworks miss: which features create delight, which create baseline satisfaction, and which are just expected? The model categorizes features into three types — Basic (expected, cause dissatisfaction if absent but don't drive satisfaction if present), Performance (more is better, linearly improve satisfaction), and Delighters (unexpected, create disproportionate delight when present).
Building a Kano diagram on a whiteboard during a product strategy session is significantly more useful than doing it in a spreadsheet. You can argue about where a feature belongs, draw the satisfaction curves for each category, and negotiate the position of ambiguous features in real time. The whiteboard makes the theoretical model tangible.
The output — which features are Basic, which are Performance, which are Delighters, and crucially, which might be over-invested Basics — drives real product investment decisions. But those decisions depend on the whiteboard being correctly captured. A Kano diagram is one of the most visually complex boards BoardSnap reads.
Two axes: Y-axis is customer satisfaction (bottom = very dissatisfied, top = very satisfied). X-axis is product functionality/implementation (left = not implemented, right = fully implemented). Draw and label both axes clearly. This is the canvas for the three category curves.
Basic needs (Hygiene): starts high-dissatisfied when absent, quickly reaches neutral when present — never drives satisfaction above neutral. Draw this as a curve from bottom-left to flat middle-right. Performance: linear diagonal from bottom-left to top-right. Delighters: starts neutral when absent, curves sharply upward as implemented — draw as an upward-curving line from middle-left to top-right.
Write each feature as a sticky note and place it in the area that corresponds to its category. Basics go in the flat lower section of the diagram. Performance features go along the diagonal. Delighters go in the upper curve area. Features you're unsure about go in the center for discussion.
For each feature, ask: 'If this were absent, would customers be dissatisfied or just indifferent?' Basic features cause dissatisfaction when absent. Delighters are neutral or positively surprising when absent. Discussion of ambiguous features often reveals misaligned team assumptions about what customers care about.
Basics that are receiving disproportionate engineering investment get a red marker — they're not generating proportional satisfaction. These are investment reduction candidates. Performance features below the expected satisfaction line are under-invested — green marker.
Open BoardSnap. The Kano diagram with axes, three curves, and sticky notes placed in each zone. BoardSnap AI reads the zone labels and the position of each feature name relative to the zones.
A structured Kano analysis with features classified by type: Basic Expectations, Performance Features, and Delighters. Over-invested Basics and under-invested Performance features are flagged. Strategic implications are described — where to invest more, where to pull back. The output drives product and engineering investment conversations.
The team placed 24 existing features on the Kano diagram. Five features they'd been investing in heavily turned out to be Basics — customers expected them but they weren't driving satisfaction. Three underinvested features were identified as Delighters. The Kano session shifted the roadmap allocation before the quarterly plan was set.
Before building a new product area, the team ran a Kano session with customer interview data. Seven features that felt innovative to the team were identified as Basics in the target market — customers expected them from any tool in the category. The team's innovation energy shifted to six genuine Delighter opportunities.
BoardSnap AI reads labeled zones on the diagram, not the curves themselves. Draw the three curves as background context, but more importantly, label each zone clearly — 'Basic,' 'Performance,' 'Delighter' — and place features in the corresponding zones. The zone labels are what the output is structured around.
Use the functional/dysfunctional question pair: 'How do you feel if this feature is present?' and 'How do you feel if it's absent?' A feature where presence is neutral and absence is dissatisfying is a Basic. A feature where presence is exciting and absence is neutral is a Delighter. You can run this as a team exercise with assumptions as a starting point, then validate with real customer data.
Yes. Delighters become Performance features and eventually Basics as the market matures — this is a well-known pattern. Store each Kano session as a separate board in the same BoardSnap project. The AI chat can compare classifications across sessions and identify features that have migrated categories.
Snap the board, ship the action items in ten seconds.