Redesigning UBC Library

783 views

Published on

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

Published in: Design
2 Comments
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total views
783
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
2
Likes
0
Embeds 0
No embeds

No notes for slide

Redesigning UBC Library

  1. 1. Redesigning UBC Library John Chan July 25, 2012Friday, 5 April, 13
  2. 2. A Little HistoryFriday, 5 April, 13
  3. 3. June 1997Friday, 5 April, 13
  4. 4. July 1999Friday, 5 April, 13
  5. 5. October 2000Friday, 5 April, 13
  6. 6. February 2003Friday, 5 April, 13
  7. 7. June 2007Friday, 5 April, 13
  8. 8. September 2008Friday, 5 April, 13
  9. 9. January 2010Friday, 5 April, 13
  10. 10. September 2010Friday, 5 April, 13
  11. 11. January 2011Friday, 5 April, 13
  12. 12. July 2011Friday, 5 April, 13
  13. 13. December 2011Friday, 5 April, 13
  14. 14. The recent rapid changes led to a lot of frustration. Change meant recreating instructions and starting over.Friday, 5 April, 13
  15. 15. So our redesigns reflected the path of least resistance. We paved over the cow paths.Friday, 5 April, 13
  16. 16. But still, a redesign was long overdue.Friday, 5 April, 13
  17. 17. And now... today.Friday, 5 April, 13
  18. 18. Our FocusFriday, 5 April, 13
  19. 19. Our Focus A value proposition that explains the purpose of academic libraries.Friday, 5 April, 13
  20. 20. Our Focus Homepage sections that reflects our site’s contents and priorities.Friday, 5 April, 13
  21. 21. Our Focus An improved navigation with more clarity and utility.Friday, 5 April, 13
  22. 22. We’ve heard this before.Friday, 5 April, 13
  23. 23. A Brand New StartFriday, 5 April, 13
  24. 24. If we remove the shackles of the past, what are the possibilities?Friday, 5 April, 13
  25. 25. Complete User ExperienceFriday, 5 April, 13
  26. 26. Complete Design ProcessFriday, 5 April, 13
  27. 27. Let’s talk about process.Friday, 5 April, 13
  28. 28. Design culture at LSITFriday, 5 April, 13
  29. 29. Design culture at LSIT “Too little, too late”Friday, 5 April, 13
  30. 30. Design culture at LSIT “Too little, too late” ConsultationFriday, 5 April, 13
  31. 31. Design culture at LSIT “Too little, too late” Consultation FeedbackFriday, 5 April, 13
  32. 32. Design culture at LSIT “Too little, too late” Consultation Feedback ResourcesFriday, 5 April, 13
  33. 33. Design culture at LSIT “Too little, too late” Consultation Feedback Resources TestingFriday, 5 April, 13
  34. 34. Design culture at LSIT “Too little, too late” Consultation Feedback Resources Testing NoticeFriday, 5 April, 13
  35. 35. We heard you.Friday, 5 April, 13
  36. 36. Here’s what we changed.Friday, 5 April, 13
  37. 37. A Dedicated Working GroupFriday, 5 April, 13
  38. 38. A Dedicated Working Group Multiple Internal Feedback SessionsFriday, 5 April, 13
  39. 39. A Dedicated Working Group Multiple Internal Feedback Sessions Preview Working DesignsFriday, 5 April, 13
  40. 40. A Dedicated Working Group Multiple Internal Feedback Sessions Preview Working Designs More Comprehensive Data CollectionFriday, 5 April, 13
  41. 41. A Dedicated Working Group Multiple Internal Feedback Sessions Preview Working Designs More Comprehensive Data Collection Earlier Project LaunchFriday, 5 April, 13
  42. 42. Better Communication + Better TransparencyFriday, 5 April, 13
  43. 43. How did we do?Friday, 5 April, 13
  44. 44. Complete User ExperienceFriday, 5 April, 13
  45. 45. What makes user experience complete?Friday, 5 April, 13
  46. 46. Jesse James Garrett author of “The Elements of User Experience”Friday, 5 April, 13
  47. 47. Jesse James Garrett From “The Elements of User Experience”Friday, 5 April, 13
  48. 48. Site Objectives User NeedsFriday, 5 April, 13
  49. 49. Functional Content Requirements Requirements Site Objectives User NeedsFriday, 5 April, 13
  50. 50. Interaction Information Design Architecture Functional Content Requirements Requirements Site Objectives User NeedsFriday, 5 April, 13
  51. 51. Information Design Navigation Design Interaction Information Design Architecture Functional Content Requirements Requirements Site Objectives User NeedsFriday, 5 April, 13
  52. 52. Visual Design Information Design Navigation Design Interaction Information Design Architecture Functional Content Requirements Requirements Site Objectives User NeedsFriday, 5 April, 13
  53. 53. In the past, we were only able to design in sections.Friday, 5 April, 13
  54. 54. Visual Design Information Design Information Architecture Functional Requirements User NeedsFriday, 5 April, 13
  55. 55. Fragmented considerations, means poorer design choices...Friday, 5 April, 13
  56. 56. ... hence, our default answer to most feedback is “no”.Friday, 5 April, 13
  57. 57. BUTFriday, 5 April, 13
  58. 58. Our team at LSIT don’t have all the answers. We see the world as:Friday, 5 April, 13
  59. 59. Visual Design Navigation Design Interaction Information Design Architecture Functional Requirements Site Objectives User NeedsFriday, 5 April, 13
  60. 60. We need YOU to see the rest.Friday, 5 April, 13
  61. 61. We need EACH OTHER to see the rest.Friday, 5 April, 13
  62. 62. Don’t panic.Friday, 5 April, 13
  63. 63. We’re on the road to recovery.Friday, 5 April, 13
  64. 64. Keep the dialogue going.Friday, 5 April, 13
  65. 65. Thank you. @jtcchan jc@37signals.comFriday, 5 April, 13

×