1. I want results, not a results page Kristoffer Dyrkorn UXLX 2010

2. How do we design search?

4. results pages

5. 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

6. But… what about complexity? http://yamaha.com

7. http://amazon.com Context switch? http://amazon.com

8. Compression? 4 out of 128 (3%) result item results metadata http://amazon.com

9. In short http://amazon.com

10. The search process

11. visualization concept query words GOGO GOGO formulation interpretation clarification wordscontentresults selection visualization clarification

12. http://visualthesaurus.com http://google.com http://carrot2.org Example: Concept maps

13. clarification concept query words GOGO GOGO formulation interpretation wordscontentresults selection visualization selection

14. Example: Pearl growing http://google.com

15. Pearl growing – alternate take result item Property Importance Value Property Importance Value Property Importance Value query text site header

16. 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!

17. BEKK CONSULTING AS SKUR 39, VIPPETANGEN. P.O. BOX 134 SENTRUM, 0102 OSLO, NORWAY. WWW.BEKK.NO Kristoffer Dyrkorn Manager kristoffer.dyrkorn [at] bekk.no