After having listed various evaluation methods, Jordan provides a guideline for choosing the most appropriate method(s) depending on the level at which a prototype is developed and shows an example of how such testing might be conducted.
Scott Jenson defines 'feature blindness' as users being blinded by a feature list. He identifies the bottom-up approach of creating a user persona and a task scenario as more efficient than the top-down approach, in terms of organizing a commonsensical hierarchy of a product's features. The ideal visualization would be to 'tame' the feature list and prioritize features in accordance to a set of usage requirements and subsequent usage frequency.
