170 likes | 261 Views
I want results, not a results page. Kristoffer Dyrkorn. UXLX 2010. How do we design search?. How do we design search ?. results pages. A results page should contain…. Navigation artifacts Specification artifacts Related searches Manipulation artifacts Expanded navigation artifacts
E N D
I want results, not a results page Kristoffer Dyrkorn UXLX 2010
How do we design search? results pages
A results page should contain… • Navigation artifacts • Specification artifacts • Related searches • Manipulation artifacts • Expanded navigation artifacts • Results artifact • Alternate revenue artifacts • Default sorting • Prioritised placement Source: Mario Santoyo http://adaptivepath.com
But… what about complexity? http://yamaha.com
Context switch? http://amazon.com http://amazon.com
Compression? results metadata 4 out of 128 (3%) result item http://amazon.com
In short http://amazon.com
concept words content results formulation interpretation query words GO visualization visualization clarification clarification selection
Example: Concept maps http://google.com http://carrot2.org http://visualthesaurus.com
concept words content results formulation interpretation query words GO visualization selection clarification clarification selection
Example: Pearl growing http://google.com http://google.com
Pearl growing – alternate take site header query text result item Property Property Property Value Value Value Importance Importance Importance
Summary • Concept -> words -> content -> results • Change the results page • Present results at the concept level • Interact directly with the results • Find other ways! • Read “Search Patterns” by Moreville & Callender Thank you!
Kristoffer Dyrkorn Manager kristoffer.dyrkorn [at] bekk.no