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

1. The Future of Library
User Experience
2009 Urban Libraries Council Webinar Keynote

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

4. Founded in 2002
San Francisco
7 People
One Book

5. ulcwebinar.com

6. #ulctalk
@boltron

8. The Bad News.

9. “Est-ce que Google
nous rend idiot ?”
Nicolas Carr.
Le Monde. June 5th, 2009

10. “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.”

11. tech⋅nol⋅o⋅guy

12. It Really Is A Series of Tubes
Molly Wright Steenson - Princeton

13. Chaco, Rin
What the Angel Gave Me
1 million copies

17. What is User Experience ?

18. Peter Morville
Semanticstudios.com

19. Frank Spillers
Bryce Glass
Experiencedynamics.com

20. Michael Cunnings | uxdesign.com

21. e "Universe" 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

22. 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 "look" in "look-and-feel") 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: "feature set":
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/

23. seems complicated

24. People Before Systems

25. Experience Before Systems

26. Logic ≠ Intuition

27. Logical
photo by flickr.com/photos/80849382@N00/3306939463/

28. Intuitive
photo by flickr.com/photos/51035750608@N01/117683322/

29. Make Wikipedia Easier to Edit.

30. Your Organizational Hierarchy is Showing.

31. The Future of Library User Experience

32. Not the future of libraries
photo by flickr.com/photos/zac-attack/202605234

33. And, umm, how far in the future,
exactly?

34. “10 Years.”
Bill Buxton
Principle Researcher, Microsoft.

35. “30 Years. I
write science
fiction, and for
some reason
people think
that this means
I can predict the
future.”
Charlie Stross
Login, 2009

36. “We walk backwards into the future”
Marshall McLuhan

37. 10 Years.
Location Electronic Shift of
Aware Ink Focus
Devices
WWDC It’s Been 10 From Library
Years Legacy
Systems to
Experience

38. Screw That, Future Boy.
What Can Libraries Do
Tomorrow to Improve UX
facing a 5%-7% Budget
Cut?

39. 1 2 3
Watch Draw or Play With
Three Build One a Free
People Web Page Open Tool
Use Your
Site
Don’t ask Outside your Freebase,
them a thing current Google
until they are architecture. Squared,
done. Use Open
Wordpress. Library,
Google Wave
Preview.

40. Even Farther In The Future

41. Three Principles
1 Open Architecture Wins
2 Build Small
3 Behavior not Opinions

42. Open Architecture.
It’s not open source.

43. API
Application Programming Interface

44. Build Technology That
Plays Well With Others

45. Even Google

50. “Open playing field for generative
books.”
George Oates. Open Library.

51. Build Small
Forget about large system consequences

52. Research Behavior.
Ignore Opinions.

53. Read all the links at
ulcwebinar.com

54. What Public Libraries are
Doing Right and Wrong

56. Heuristic Review
Nashville Boulder Charlotte Orlando

57. Open, user-generated

58. But…What does ‘Database by Topic’ mean?

59. Links that say different things…
but go to the same place

60. A Window to Your Database

62. Closed System

64. Proximity Matters

65. Mental Models
Indi Young
As PDF or Book

66. The Summary

67. Tomorrow
Watch three people. Draw or build a wordpress page.
Play with an open free tool.

68. 10 Years.
Electronic Ink, Location Dependent Devices, Shift of Focus to
Experience

69. 30 Years.
Open Architecture Wins, Build Small, and Behavior not
Opinions

70. How do you know when
something is innovative?

71. “It’s been done before”
- Bill Buxton | You remember him from the intro right

74. “It’s scary”
- Marty Neumeier | The Designful Company

75. @boltron
nate@boltpeters.com
ulcwebinar.com
flickr.com/photos/striatic/