1 / 49

The Essentials of Great Search Design

The Essentials of Great Search Design. Search User Experience. As an enterprise search consultant. Oslo, Norway. Working both public and private sector. I’ve learnt One v ery important thing. Search is a Wicked Problem. Peter Morville, not me. Enterprise Search is harder...

dyani
Download Presentation

The Essentials of Great Search Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  15. We call it Sprint 0

  16. All in just 4 weeks!

  17. Stakeholders It’s not an ego trip... Information Architect Systems Architect Process Innovation Emotional Innovation Functional Innovation Users Techies Interaction Designer

  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. Because innovation happens where diciplines intersect. “If I had asked people what they wanted, they would have said faster horses.” - Henry Ford flickr.com/sandcastlematt

  23. 3 Find the Problems that youneed to solve later!

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

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

  26. Seekinspiration flickr.com/nedrichards

  27. Learn from Stakeholderswhat 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 Userswhat 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 Techieswhat 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 foryour design decisions.

  34. Document user needs as Personasand User Stories “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. HIGH Benefit to Personas LOW Technical Feasibility HIGH Technical Feasibility LOW Benefit to Personas

  36. Organizeentities, 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 Modes Behaviors Design Patterns Known-item Narrow Auto-Complete Exploration Pearl Growing Best Bet Research Pogostick Guided Navigation Re-finding Agonizing Universal Search Scanning Personalization 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 youneed to solve later!

  46. Ask, try, learn, repeat...

  47. We discover the best solutions Together

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

More Related