The Essentials of Great Search Design (ECIR 2010)
18 likes1,237 views
This document outlines an essential search design process called "Sprint 0" that involves cross-disciplinary collaboration. It emphasizes learning from stakeholders, users, and technical experts to understand business goals, user needs, and technological capabilities. Concepts are developed through inspiration, ideation, and iterative prototyping and testing of interaction and technical designs. The goal is to unite business goals, user needs, and technological possibilities to discover solutions and innovate through an inclusive design process.
The Essentials of Great Search Design (ECIR 2010)
- 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. Dialog It requires and Cross-diciplinary Collaboration with
- 11. Users Users Customers Customers Employees 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. Business Goals Concept Development User Needs Product Backlog Technological Interaction Technology Capabilities Design Design Inspiration Ideation Implementation
- 15. We call it Sprint 0
- 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. Stakeholders It’s not an ego trip... Business Information Value Systems Architect Architect Emotional Process Innovation Innovation User Functional Technological Innovation Needs Capabilities Users Techies Interaction Designer
- 18. IncludeEverybody in the design process!
- 19. Because we all see things a bit differently
- 20. What kind of designer are you?
- 21. 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. Problems Find the that you need to solve later!
- 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 “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. 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. 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 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 test the 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. IncludeEverybody in the design process!
- 44. Seek to unite Business Goals User Needs and Technological Possibilities
- 45. Problems Find the that you need to solve later!
- 46. Ask, try, learn, repeat... Business Goals Concept Development User Needs Product Backlog Technological Interaction Technology Capabilities Design Design Inspiration Ideation Implementation
- 47. We discover the best solutions Together
- 48. Presentation by: Vegard Sandvold Designer / Information Architect http://twitter.com/vsandvold http://thingsontop.com