The Essentials of Great Search DesignSearch User Experience
As an enterprise search consultant            Oslo,            Norway
Working both public and private sector
I’ve learnt   Onevery important thing
Search is aWicked ProblemPeter Morville, not me.
Enterprise Search is harder...High AmbitionsVague GoalsTight BudgetsEven Tighter Deadlines
...than you would imagineWeak InfrastructureLegacy SystemsFaulty MetadataScanned DocumentsConvoluted Security
To solve it takes more than      Clever Algorithms,         Beautiful Code and             Lots of Data
DialogIt requires              and      Cross-diciplinary Collaboration with
StakeholdersProduct OwnersProject ManagersSales/marketingHuman Resources
Users     Users      Customers        Customers               Employees        Employeesflickr.com/papazimouris
Techies        Sysadmins        Programmers        Web designersflickr.com/aaronvandike
To create something trulyEfficientUsableDesirable
You need a process to explorerequirements ahead of iterativedevelopment.    Business Goals                          Concep...
We call itSprint 0
Stakeholder          Concept       System        Revising                                                                 ...
StakeholdersIt’s not anego trip...                                  Business     Information                    Value     ...
IncludeEverybody     in the design process!
Because we all see things a bit differently
What kindof designerare you?
Seek to unite    Business Goals       User Needs and    Technological Possibilities
Because innovation happenswhere diciplines intersect.           “If I had asked people what           they wanted, they wo...
ProblemsFind the     that you need to solve later!
flickr.com/ijzerman
Okay...Let’s dive in!
Seek inspiration             flickr.com/nedrichards
Learn from Stakeholders what makes them    Successful                                 I Won!flickr.com/photos/sepblog
Ask questions like:How do you know its a problem?Who are most effected by the problem?How would you measure progress?What ...
Learn from Users what makes themProductive
Ask questions like:How is it like where you work?What tasks do you perform?When do you typically seek information?What is ...
Learn from Techies what makes themReassured
Ask questions like:Who uses the system and for what?What kind of documents does it contain?What’s the projected growth in ...
Document the basis     for your design decisions.
Document user needs asPersonas and User Stories                    “I want an automatic search on the                    c...
To help stakeholders make priorities.                            HIGH                     Benefit to Personas             ...
Organize entities, categories and facets     in Information     Models
To help users make sense of information
Sketch out concepts that integratePersonas,User StoriesandInformationModels.
Supported bySearch Modes   Behaviors       Design PatternsKnown-item     Narrow          Auto-CompleteExploration    Pearl...
Prototype and test the interaction design to discover potential usability issues.
Prototype and test the technical design todiscover potential bottle-necks and pitfalls.Fileserver loadFaulty security mech...
Let’s go over that   Again...
IncludeEverybody     in the design process!
Seek to unite    Business Goals       User Needs and    Technological Possibilities
ProblemsFind the     that you need to solve later!
Ask, try, learn, repeat...    Business Goals                          Concept                                          Dev...
We discover the best solutions        Together
Presentation by:Vegard SandvoldDesigner / Information Architecthttp://twitter.com/vsandvoldhttp://thingsontop.com
The Essentials of Great Search Design (ECIR 2010)
Upcoming SlideShare
Loading in...5
×

The Essentials of Great Search Design (ECIR 2010)

2,829

Published on

Enterprise search is a wicked problem - a problem that can't be solved merely with clever algorithms, beautiful code and lots of data. It takes dialog and cross-diciplinary collaboration with stakeholders, users and techies to explore all the requirements for a possibly great enterprise search solution.

Published in: Technology
2 Comments
18 Likes
Statistics
Notes
  • Best one
    Hope you are in good health. My name is AMANDA . I am a single girl, Am looking for reliable and honest person. please have a little time for me. Please reach me back amanda_n14144@yahoo.com so that i can explain all about myself .
    Best regards AMANDA.
    amanda_n14144@yahoo.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Awesome :)
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
2,829
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
2
Likes
18
Embeds 0
No embeds

No notes for slide

The Essentials of Great Search Design (ECIR 2010)

  1. 1. The Essentials of Great Search DesignSearch User Experience
  2. 2. As an enterprise search consultant Oslo, Norway
  3. 3. Working both public and private sector
  4. 4. I’ve learnt Onevery important thing
  5. 5. Search is aWicked ProblemPeter Morville, not me.
  6. 6. Enterprise Search is harder...High AmbitionsVague GoalsTight BudgetsEven Tighter Deadlines
  7. 7. ...than you would imagineWeak InfrastructureLegacy SystemsFaulty MetadataScanned DocumentsConvoluted Security
  8. 8. To solve it takes more than Clever Algorithms, Beautiful Code and Lots of Data
  9. 9. DialogIt requires and Cross-diciplinary Collaboration with
  10. 10. StakeholdersProduct OwnersProject ManagersSales/marketingHuman Resources
  11. 11. Users Users Customers Customers Employees Employeesflickr.com/papazimouris
  12. 12. Techies Sysadmins Programmers Web designersflickr.com/aaronvandike
  13. 13. To create something trulyEfficientUsableDesirable
  14. 14. You need a process to explorerequirements ahead of iterativedevelopment. Business Goals Concept Development User Needs Product Backlog Technological Interaction Technology Capabilities Design Design Inspiration Ideation Implementation
  15. 15. We call itSprint 0
  16. 16. Stakeholder Concept System Revising UI Prototype Sketching Architecture Wireframes Interview Process Prioritizing User Integration Modelling User Testing Product Interviews Testing Backlog Personas & User Information Concept Hardware & System Final Report & Stories Modelling Review Specification Presentation Indexing All in just 4 weeks! Technology Content Wireframing Performance Assessments Inventory Testing
  17. 17. StakeholdersIt’s not anego trip... Business Information Value Systems Architect Architect Emotional Process Innovation Innovation User Functional Technological Innovation Needs Capabilities Users Techies Interaction Designer
  18. 18. IncludeEverybody in the design process!
  19. 19. Because we all see things a bit differently
  20. 20. What kindof designerare you?
  21. 21. Seek to unite Business Goals User Needs and Technological Possibilities
  22. 22. Because innovation happenswhere diciplines intersect. “If I had asked people what they wanted, they would have said faster horses.” - Henry Ford flickr.com/sandcastlematt
  23. 23. ProblemsFind the that you need to solve later!
  24. 24. flickr.com/ijzerman
  25. 25. Okay...Let’s dive in!
  26. 26. Seek inspiration flickr.com/nedrichards
  27. 27. Learn from Stakeholders what makes them Successful I Won!flickr.com/photos/sepblog
  28. 28. Ask questions like:How do you know its a problem?Who are most effected by the problem?How would you measure progress?What would show that youre successful?When do you need results?
  29. 29. Learn from Users what makes themProductive
  30. 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. 31. Learn from Techies what makes themReassured
  32. 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. 33. Document the basis for your design decisions.
  34. 34. Document user needs asPersonas and 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.” Age 20 years Role Account manager Background High school Computer Much time online, Experience Facebook, YouTube
  35. 35. To help stakeholders make priorities. HIGH Benefit to Personas Work on Work on these these features features LATER NOW LOW HIGH Technical Technical Feasibility Feasibility Ignore these Work on features, these possibly features forever. later. MAYBE LOW Benefit to Personas
  36. 36. Organize entities, categories and facets in Information Models
  37. 37. To help users make sense of information
  38. 38. Sketch out concepts that integratePersonas,User StoriesandInformationModels.
  39. 39. Supported bySearch Modes Behaviors Design PatternsKnown-item Narrow Auto-CompleteExploration Pearl Growing Best BetResearch Pogostick Guided NavigationRe-finding Agonizing Universal Search Scanning Personalization Pivot
  40. 40. Prototype and test the interaction design to discover potential usability issues.
  41. 41. Prototype and test the technical design todiscover potential bottle-necks and pitfalls.Fileserver loadFaulty security mechanismsDependencies with other systems
  42. 42. Let’s go over that Again...
  43. 43. IncludeEverybody in the design process!
  44. 44. Seek to unite Business Goals User Needs and Technological Possibilities
  45. 45. ProblemsFind the that you need to solve later!
  46. 46. Ask, try, learn, repeat... Business Goals Concept Development User Needs Product Backlog Technological Interaction Technology Capabilities Design Design Inspiration Ideation Implementation
  47. 47. We discover the best solutions Together
  48. 48. Presentation by:Vegard SandvoldDesigner / Information Architecthttp://twitter.com/vsandvoldhttp://thingsontop.com

×