A talk I gave on the goals and process of our site redesign and the design culture at UBC Library.

1. Redesigning
UBC Library
John Chan
July 25, 2012
Friday, 5 April, 13

2. A Little History
Friday, 5 April, 13

3. June 1997
Friday, 5 April, 13

4. July 1999
Friday, 5 April, 13

5. October 2000
Friday, 5 April, 13

6. February 2003
Friday, 5 April, 13

7. June 2007
Friday, 5 April, 13

8. September 2008
Friday, 5 April, 13

9. January 2010
Friday, 5 April, 13

10. September 2010
Friday, 5 April, 13

11. January 2011
Friday, 5 April, 13

12. July 2011
Friday, 5 April, 13

13. December 2011
Friday, 5 April, 13

14. The recent rapid changes led to a lot of frustration.
Change meant recreating instructions and starting over.
Friday, 5 April, 13

15. So our redesigns reflected the path of least resistance.
We paved over the cow paths.
Friday, 5 April, 13

16. But still, a redesign was long overdue.
Friday, 5 April, 13

17. And now... today.
Friday, 5 April, 13

18. Our Focus
Friday, 5 April, 13

19. Our Focus
A value proposition that explains
the purpose of academic libraries.
Friday, 5 April, 13

20. Our Focus
Homepage sections that reflects
our site’s contents and priorities.
Friday, 5 April, 13

21. Our Focus
An improved navigation with
more clarity and utility.
Friday, 5 April, 13

22. We’ve heard this before.
Friday, 5 April, 13

23. A Brand New Start
Friday, 5 April, 13

24. If we remove the
shackles of the past,
what are the possibilities?
Friday, 5 April, 13

25. Complete User Experience
Friday, 5 April, 13

26. Complete Design Process
Friday, 5 April, 13

27. Let’s talk about process.
Friday, 5 April, 13

28. Design culture at LSIT
Friday, 5 April, 13

29. Design culture at LSIT
“Too little, too late”
Friday, 5 April, 13

30. Design culture at LSIT
“Too little, too late”
Consultation
Friday, 5 April, 13

31. Design culture at LSIT
“Too little, too late”
Consultation
Feedback
Friday, 5 April, 13

32. Design culture at LSIT
“Too little, too late”
Consultation
Feedback
Resources
Friday, 5 April, 13

33. Design culture at LSIT
“Too little, too late”
Consultation
Feedback
Resources
Testing
Friday, 5 April, 13

34. Design culture at LSIT
“Too little, too late”
Consultation
Feedback
Resources
Testing
Notice
Friday, 5 April, 13

35. We heard you.
Friday, 5 April, 13

36. Here’s what we changed.
Friday, 5 April, 13

37. A Dedicated Working Group
Friday, 5 April, 13

38. A Dedicated Working Group
Multiple Internal Feedback Sessions
Friday, 5 April, 13

39. A Dedicated Working Group
Multiple Internal Feedback Sessions
Preview Working Designs
Friday, 5 April, 13

40. A Dedicated Working Group
Multiple Internal Feedback Sessions
Preview Working Designs
More Comprehensive Data Collection
Friday, 5 April, 13

41. A Dedicated Working Group
Multiple Internal Feedback Sessions
Preview Working Designs
More Comprehensive Data Collection
Earlier Project Launch
Friday, 5 April, 13

42. Better Communication
+
Better Transparency
Friday, 5 April, 13

43. How did we do?
Friday, 5 April, 13

44. Complete User Experience
Friday, 5 April, 13

45. What makes user experience complete?
Friday, 5 April, 13

46. Jesse James Garrett
author of “The Elements of User Experience”
Friday, 5 April, 13

47. Jesse James Garrett
From “The Elements of User Experience”
Friday, 5 April, 13

48. Site Objectives User Needs
Friday, 5 April, 13

49. Functional
Content Requirements
Requirements
Site Objectives User Needs
Friday, 5 April, 13

50. Interaction Information
Design Architecture
Functional
Content Requirements
Requirements
Site Objectives User Needs
Friday, 5 April, 13

51. Information Design Navigation Design
Interaction Information
Design Architecture
Functional
Content Requirements
Requirements
Site Objectives User Needs
Friday, 5 April, 13

52. Visual Design
Information Design Navigation Design
Interaction Information
Design Architecture
Functional
Content Requirements
Requirements
Site Objectives User Needs
Friday, 5 April, 13

53. In the past, we were only able to
design in sections.
Friday, 5 April, 13

54. Visual Design
Information Design
Information
Architecture
Functional
Requirements
User Needs
Friday, 5 April, 13

55. Fragmented considerations, means
poorer design choices...
Friday, 5 April, 13

56. ... hence, our default answer to
most feedback is “no”.
Friday, 5 April, 13

57. BUT
Friday, 5 April, 13

58. Our team at LSIT don’t have all the answers.
We see the world as:
Friday, 5 April, 13

59. Visual Design
Navigation Design
Interaction Information
Design Architecture
Functional
Requirements
Site Objectives User Needs
Friday, 5 April, 13

60. We need YOU to see the rest.
Friday, 5 April, 13

61. We need EACH OTHER to see the rest.
Friday, 5 April, 13

62. Don’t panic.
Friday, 5 April, 13

63. We’re on the road to recovery.
Friday, 5 April, 13

64. Keep the dialogue going.
Friday, 5 April, 13

65. Thank you.
@jtcchan
jc@37signals.com
Friday, 5 April, 13