Search portal design process - aug 9, 2011

1,783
-1

Published on

Covers the new methodologies and projects we're doing at LSIT to alleviate our design challenges and how they've applied to the Search Portal. Highlights the different usability tests we've done and how they informed our design decisions. Presented on August 9th, 2011.

Published in: Design, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,783
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Search portal design process - aug 9, 2011

  1. 1. SEARCH PORTAL DESIGN PROCESS with JOHN CHAN INTERACTION DESIGNER, LSITTuesday, August 9, 2011
  2. 2. HELLOTuesday, August 9, 2011
  3. 3. Things have CHANGED • We have new members on our team • We have new a site development process • We have new tools to help us deal with our challenges • We have a new portal based our new resourcesTuesday, August 9, 2011
  4. 4. Things have CHANGED • We have new members on our team • We have new a site development process • We have new tools to help us deal with our challenges • We have a new portal based our new resourcesTuesday, August 9, 2011
  5. 5. Tuesday, August 9, 2011
  6. 6. Things have CHANGED • We have new members on our team • We have new a site development process • We have new tools to help us deal with our challenges • We have a new portal based our new resourcesTuesday, August 9, 2011
  7. 7. Things have CHANGED • We have new members on our team • We have new a site development process • We have new tools to help us deal with our challenges • We have a new portal based our new resourcesTuesday, August 9, 2011
  8. 8. Things have CHANGED • We have new members on our team • We have new a site development process • We have new tools to help us deal with our challenges • We have a new portal based our new resourcesTuesday, August 9, 2011
  9. 9. new changes = BETTER RESULTSTuesday, August 9, 2011
  10. 10. A New ProcessTuesday, August 9, 2011
  11. 11. In The Past... DiscoverTuesday, August 9, 2011
  12. 12. In The Past... Discover DesignTuesday, August 9, 2011
  13. 13. In The Past... Discover Design DevelopTuesday, August 9, 2011
  14. 14. In The Past... Discover Design Develop Sign-offTuesday, August 9, 2011
  15. 15. In The Past... Discover Design Develop Sign-off LaunchTuesday, August 9, 2011
  16. 16. ProblemsTuesday, August 9, 2011
  17. 17. Problems • We were missing some critical stepsTuesday, August 9, 2011
  18. 18. Problems • We were missing some critical steps • We (usually) didn’t leave enough room for user testingTuesday, August 9, 2011
  19. 19. Problems • We were missing some critical steps • We (usually) didn’t leave enough room for user testing • Longer development timelines - produces overlapping workTuesday, August 9, 2011
  20. 20. Problems • We were missing some critical steps • We (usually) didn’t leave enough room for user testing • Longer development timelines - produces overlapping work • Slow to iteratenew data to changing demands and - inflexibleTuesday, August 9, 2011
  21. 21. Today DiscoverTuesday, August 9, 2011
  22. 22. Today Discover DefineTuesday, August 9, 2011
  23. 23. Today Develop Discover Define Design TestTuesday, August 9, 2011
  24. 24. Today Develop Discover Define Launch Design TestTuesday, August 9, 2011
  25. 25. FixesTuesday, August 9, 2011
  26. 26. Fixes • Added documentation, success and metrics definitions to our processTuesday, August 9, 2011
  27. 27. Fixes • Added documentation, success and metrics definitions to our process • Incorporates user testing through the development cycleTuesday, August 9, 2011
  28. 28. Fixes • Added documentation, success and metrics definitions to our process • Incorporates user testing through the development cycle • Reduced developmentdecisions with better data informed design timelinesTuesday, August 9, 2011
  29. 29. Fixes • Added documentation, success and metrics definitions to our process • Incorporates user testing through the development cycle • Reduced developmentdecisions with better data informed design timelines • Faster iterationsTuesday, August 9, 2011
  30. 30. “Not Enough Designers”Tuesday, August 9, 2011
  31. 31. ProblemsTuesday, August 9, 2011
  32. 32. Problems • Slower project deliveriesTuesday, August 9, 2011
  33. 33. Problems • Slower project deliveries • Difficult to(mobile, testing, R&D, etc.) initiatives develop any forward thinkingTuesday, August 9, 2011
  34. 34. Problems • Slower project deliveries • Difficult to(mobile, testing, R&D, etc.) initiatives develop any forward thinking • We’ll have to relydo design work programmers to on existing interfaces and/orTuesday, August 9, 2011
  35. 35. Problems • Slower project deliveries • Difficult to(mobile, testing, R&D, etc.) initiatives develop any forward thinking • We’ll have to relydo design work programmers to on existing interfaces and/or • Harder to manage look and feel library-wide and creates inconsistenciesTuesday, August 9, 2011
  36. 36. Problems • Slower project deliveries • Difficult to(mobile, testing, R&D, etc.) initiatives develop any forward thinking • We’ll have to relydo design work programmers to on existing interfaces and/or • Harder to manage look and feel library-wide and creates inconsistencies • I get stressed out...Tuesday, August 9, 2011
  37. 37. Dealing with Inconsistencies (my nemesis!)Tuesday, August 9, 2011
  38. 38. Tuesday, August 9, 2011
  39. 39. Tuesday, August 9, 2011
  40. 40. Tuesday, August 9, 2011
  41. 41. Tuesday, August 9, 2011
  42. 42. Tuesday, August 9, 2011
  43. 43. Tuesday, August 9, 2011
  44. 44. Tuesday, August 9, 2011
  45. 45. Tuesday, August 9, 2011
  46. 46. Tuesday, August 9, 2011
  47. 47. Tuesday, August 9, 2011
  48. 48. Tuesday, August 9, 2011
  49. 49. Tuesday, August 9, 2011
  50. 50. Tuesday, August 9, 2011
  51. 51. Tuesday, August 9, 2011
  52. 52. Tuesday, August 9, 2011
  53. 53. me WHYYY?!Tuesday, August 9, 2011
  54. 54. UI Library DemoTuesday, August 9, 2011
  55. 55. Designing SearchTuesday, August 9, 2011
  56. 56. Designing Search Develop Discover Define Launch Design TestTuesday, August 9, 2011
  57. 57. Designing Search Develop Define Design TestTuesday, August 9, 2011
  58. 58. Defining Objectives, Plans, etc.Tuesday, August 9, 2011
  59. 59. Tuesday, August 9, 2011
  60. 60. Tuesday, August 9, 2011
  61. 61. Tuesday, August 9, 2011
  62. 62. Tuesday, August 9, 2011
  63. 63. Tuesday, August 9, 2011
  64. 64. Tuesday, August 9, 2011
  65. 65. ObjectivesTuesday, August 9, 2011
  66. 66. Create an intuitive navigation that highlights the available resourcesTuesday, August 9, 2011
  67. 67. Create and unify a usable interface across the different platformsTuesday, August 9, 2011
  68. 68. Provide appropriate labels and conditions that leads to successful resultsTuesday, August 9, 2011
  69. 69. Cater to new and experienced usersTuesday, August 9, 2011
  70. 70. Testing Our DesignsTuesday, August 9, 2011
  71. 71. “5-Second Test” When new visitors show up do they get it?Tuesday, August 9, 2011
  72. 72. Tuesday, August 9, 2011
  73. 73. Tuesday, August 9, 2011
  74. 74. Tuesday, August 9, 2011
  75. 75. Tuesday, August 9, 2011
  76. 76. Tuesday, August 9, 2011
  77. 77. Tuesday, August 9, 2011
  78. 78. Tuesday, August 9, 2011
  79. 79. “5-Second Test” When new visitors show up do they get it? YES!Tuesday, August 9, 2011
  80. 80. Navigation Test Was the navigation easy and helpful?Tuesday, August 9, 2011
  81. 81. We made a... BIG SIGN that says, FREE CHOCOLATE BARS!Tuesday, August 9, 2011
  82. 82. Tuesday, August 9, 2011
  83. 83. Tuesday, August 9, 2011
  84. 84. Navigation Test Was the navigation easy and helpful? YES!!!Tuesday, August 9, 2011
  85. 85. Task Analysis Could people find what they’re looking for?Tuesday, August 9, 2011
  86. 86. Task Analysis Could people find what they’re looking for? ... sort of?Tuesday, August 9, 2011
  87. 87. Search Portal DemoTuesday, August 9, 2011
  88. 88. CaveatsTuesday, August 9, 2011
  89. 89. We can’t fix a usability issue if the search tool itself is broken Our efforts can only minimize bad searchesTuesday, August 9, 2011
  90. 90. There’s no perfect design - somebody always loses Again, data can tell us how to minimize bad searches, but not alwaysTuesday, August 9, 2011
  91. 91. We had to introduce a different portal design and inconsistency But we think it’s worth it... and yes, we’ll fix the other portals!Tuesday, August 9, 2011
  92. 92. Tuesday, August 9, 2011
  93. 93. Our last iteration isn’t final... or the best. We ran out of time to disprove the final UI but Articles is a tricky subjectTuesday, August 9, 2011
  94. 94. THank You Questions & Comments? john.chan@ubc.ca @jtcchan http://slideshare.net/jtcchanTuesday, August 9, 2011

×