1. The Essentials of Great Search Design Search User Experience

2. As an enterprise search consultant Oslo, Norway

3. Working both public and private sector

4. I’ve learnt One very important thing

5. Search is a Wicked Problem Peter Morville, not me.

6. Enterprise Search is harder... High Ambitions Vague Goals Tight Budgets Even Tighter Deadlines

7. ...than you would imagine Weak Infrastructure Legacy Systems Faulty Metadata Scanned Documents Convoluted Security

8. To solve it takes more than Clever Algorithms, Beautiful Code and Lots of Data

9. It requires Dialog and Cross - diciplinary Collaboration with

10. Stakeholders Product Owners Project Managers Sales/marketing Human Resources

11. Users Customers Employees Users Customers Employees flickr.com/papazimouris

12. Techies Sysadmins Programmers Web designers flickr.com/aaronvandike

13. To create something truly Efficient Usable Desirable

14. You need a process to explore requirements ahead of iterative development. IdeationImplementation Concept Development Technology Design Interaction Design Business GoalsUser Needs Technological Capabilities Product Backlog Inspiration

15. We call it Sprint 0

16. Stakeholder Interview User Interviews Personas & User Stories Technology Assessments Content Inventory Information Modelling Process Modelling Concept Sketching System Architecture Integration Testing Concept Review Wireframing Indexing Performance Testing Hardware & System Specification User Testing Revising Wireframes UI Prototype Prioritizing Product Backlog Final Report & Presentation All in just 4 weeks !

17. Business Value Technological Capabilities User Needs Interaction Designer Information Architect Systems Architect Process Innovation Emotional Innovation Functional Innovation It ’ s not an ego trip... Stakeholders TechiesUsers

18. 1 Include Everybody in the design process !

19. Because we all see things a bit differently

20. What kind of designer are you?

21. 2 Seek to unite Business Goals User Needs and Technological Possibilities

22. “If I had asked people what they wanted, they would have said faster horses.” - Henry Ford Because innovation happens where diciplines intersect. flickr.com/sandcastlematt

23. 3 Find the Problems that you need to solve later !

24. Because a weak foundation may topple your masterpiece. flickr.com/ijzerman

25. Okay... Let’s dive inn!

26. Seek inspiration flickr.com/nedrichards

27. Learn from Stakeholders what makes them Successful I Won ! flickr.com/photos/sepblog

28. Ask questions like: How do you know it's a problem? Who are most effected by the problem? How would you measure progress? What would show that you're successful? When do you need results?

29. Learn from Users what makes them Productive

30. Ask questions like: How is it like where you work? What tasks do you perform? When do you typically seek information? What is relevant information to you? Who recieves the information you find?

31. Learn from Techies what makes them Reassured

32. Ask questions like: Who uses the system and for what? What kind of documents does it contain? What’s the projected growth in data size? How are other systems integrated? How is access control managed?

33. Document the basis for your design decisions.

34. Document user needs as Personas and User Stories Age20 years RoleAccount manager BackgroundHigh school Computer Experience Much time online, Facebook, YouTube “I want an automatic search on the customer when a phone call comes in, so that all customer information in the CRM system automatically pops up on my screen.”

35. To help stakeholders make priorities. Work on these features NOW Work on these features LATER Work on these features later. MAYBE Ignore these features, possibly forever. HIGH Technical Feasibility LOW Technical Feasibility HIGH Benefit to Personas LOW Benefit to Personas

36. Organize entities, categories and facets in Information Models

37. To help users make sense of information

38. Sketch out concepts that integrate Personas, User Stories and Information Models.

39. Supported by Search ModesBehaviorsDesign Patterns Known-itemNarrowAuto-Complete ExplorationPearl GrowingBest Bet ResearchPogostickGuided Navigation Re-findingAgonizingUniversal Search ScanningPersonalization Pivot

40. Prototype and test the interaction design to discover potential usability issues.

41. Prototype and testthe technical design to discover potential bottle-necks and pitfalls. Fileserver load Faulty security mechanisms Dependencies with other systems

42. Let’s go over that Again...

43. 1 Include Everybody in the design process !

44. 2 Seek to unite Business Goals User Needs and Technological Possibilities

45. 3 Find the Problems that you need to solve later !

46. Ask, try, learn, repeat... IdeationImplementation Concept Development Technology Design Interaction Design Business GoalsUser Needs Technological Capabilities Product Backlog Inspiration

47. We discover the best solutions Together

48. Presentation by: Vegard Sandvold Designer / Information Architect http://twitter.com/vsandvold http://thingsontop.com

50. [Tease Your Idea] Poor understanding and coordination of business goals, user needs and technological possibilites breeds confusion, conflict and disappointing failures. A balanced approach to design for great search user experience requires dialog and cross-diciplinary collaboration with stakeholders, users and techies.

51. Stakeholders