Future of Library User Experience


Published on

A talk on The Future of Library User Experience For the Urban Libraries Council webinar keynote on June 17th, 2009

Published in: Technology, Business
1 Comment
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Future of Library User Experience

  1. 1. The Future of Library User Experience 2009 Urban Libraries Council Webinar Keynote
  2. 2. Social Impact of Technology, UCSD 10 years, 1,200 participants, 231 studies Hey I’m Nate Co-author “Remote Research” Robotic Dog Treat Dispenser
  3. 3. Founded in 2002 San Francisco 7 People One Book
  4. 4. ulcwebinar.com
  5. 5. #ulctalk @boltron
  6. 6. The Bad News.
  7. 7. “Est-ce que Google nous rend idiot ?” Nicolas Carr. Le Monde. June 5th, 2009
  8. 8. 1829 tech⋅nol⋅o⋅guy
  9. 9. It Really Is A Series of Tubes Molly Wright Steenson - Princeton
  10. 10. Chaco, Rin What the Angel Gave Me 1 million copies
  11. 11. What is User Experience ?
  12. 12. Peter Morville Semanticstudios.com
  13. 13. Frank Spillers Bryce Glass Experiencedynamics.com
  14. 14. Michael Cunnings | uxdesign.com
  15. 15. e quot;Universequot; of User Experience Packaged APIs Design Deliverables Interaction Solutions Architecting the Usability Design Technology Prototyping Back-End Creative Design Information inking (Visual & UI) Architecture Flash Programming AJAX (JavaScript) Designing the Experience Content User Research DOM Front-End Scripting User Experience Development CSS Delivering the Problem Accessibility Experience Framing Business Intelligence User Markup Agents Defining the Problem Requirements Account Gathering / Project Mgmt. Research Mgmt. Managing the Project
  16. 16. The Elements of User Experience Jesse James Garrett jjg@jjg.net A basic duality: The Web was originally conceived as a hypertextual information space; 30 March 2000 but the development of increasingly sophisticated front- and back-end technologies has fostered its use as a remote software interface. This dual nature has led to much confusion, as user experience practitioners have attempted to adapt their terminology to cases beyond the scope of its original application. The goal of this document is to define some of these terms within their appropriate contexts, and to clarify the underlying relationships among these various elements. Web as software interface Concrete Completion Web as hypertext system Visual Design: visual treatment of text, Visual Design: graphic treatment of interface elements (the quot;lookquot; in quot;look-and-feelquot;) Visual Design graphic page elements and navigational components Interface Design: as in traditional HCI: Navigation Design: design of interface design of interface elements to facilitate elements to facilitate the user's movement user interaction with functionality Interface Design Navigation Design through the information architecture Information Design: in the Tuftean sense: designing the presentation of information Information Design Information Design: in the Tuftean sense: designing the presentation of information to facilitate understanding to facilitate understanding Interaction Design: development of Interaction Information Information Architecture: structural design time application flows to facilitate user tasks, defining how the user interacts with Design Architecture of the information space to facilitate intuitive access to content site functionality Functional Specifications: quot;feature setquot;: detailed descriptions of functionality the site Functional Content Content Requirements: definition of content elements required in the site must include in order to meet user needs Specifications Requirements in order to meet user needs User Needs: externally derived goals User Needs: externally derived goals for the site; identified through user research, ethno/techno/psychographics, etc. User Needs for the site; identified through user research, ethno/techno/psychographics, etc. Site Objectives: business, creative, or other internally derived goals for the site Site Objectives Site Objectives: business, creative, or other internally derived goals for the site task-oriented Abstract Conception information-oriented This picture is incomplete: The model outlined here does not account for secondary considerations (such as those arising during technical or content development) that may influence decisions during user experience development. Also, this model does not describe a development process, nor does it define roles within a user experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today. © 2000 Jesse James Garrett http://www.jjg.net/ia/
  17. 17. seems complicated
  18. 18. People Before Systems
  19. 19. Experience Before Systems
  20. 20. Logic ≠ Intuition
  21. 21. Logical photo by flickr.com/photos/80849382@N00/3306939463/
  22. 22. Intuitive photo by flickr.com/photos/51035750608@N01/117683322/
  23. 23. Make Wikipedia Easier to Edit.
  24. 24. Your Organizational Hierarchy is Showing.
  25. 25. The Future of Library User Experience
  26. 26. Not the future of libraries photo by flickr.com/photos/zac-attack/202605234
  27. 27. And, umm, how far in the future, exactly?
  28. 28. “10 Years.” Bill Buxton Principle Researcher, Microsoft.
  29. 29. “30 Years. I write science fiction, and for some reason people think that this means I can predict the future.” Charlie Stross Login, 2009
  30. 30. “We walk backwards into the future” Marshall McLuhan
  31. 31. 10 Years. Location Electronic Shift of Aware Ink Focus Devices WWDC It’s Been 10 From Library Years Legacy Systems to Experience
  32. 32. Screw That, Future Boy. What Can Libraries Do Tomorrow to Improve UX facing a 5%-7% Budget Cut?
  33. 33. 1 2 3 Watch Draw or Play With Three Build One a Free People Web Page Open Tool Use Your Site Don’t ask That doesn’t Freebase, G them a thing take into Squares, until they are account your Google Wave done. current Preview, architecture
  34. 34. Even Farther In The Future
  35. 35. Three Principles 1 Open Architecture Wins 2 Build Small 3 Behavior not Opinions
  36. 36. Open Architecture. It’s not open source.
  37. 37. API Application Protocol Interface
  38. 38. Build Technology That Plays Well With Others
  39. 39. Electricity
  40. 40. Small and Open
  41. 41. Build Small Forget about large system consequences
  42. 42. Research Behavior. Ignore Opinions.
  43. 43. Bonus Principle: Weird but Good Marty Neumier: The Designful Company
  44. 44. Read all the links at ulcwebinar.com
  45. 45. What Public Libraries are Doing Right and Wrong
  46. 46. Open Library Awesome.
  47. 47. Heuristic Review Boulder Charlotte Orlando
  48. 48. Closed System
  49. 49. A Window to Your Database
  50. 50. Proximity Matters
  51. 51. The Summary
  52. 52. Tomorrow Three Easy User Experience Improvements
  53. 53. 10 Years. Electronic Ink, Location Dependent Devices, Shift of Focus
  54. 54. 30 Years. Open Architecture Wins, Build Small, and Behavior not Opinions
  55. 55. More McLuhan
  56. 56. OH: “I wish there was like a netflix for books. Like you can just order whatever you want, and then when you’re done you can just give it back and take out another one.”
  57. 57. @boltron nate@boltpeters.com ulcwebinar.com
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.