Library:Web Design Process

From UBC Wiki
Jump to: navigation, search

Introduction

The LSIT web design process consists of the following steps:

  1. Discover
  2. Define
  3. Design
  4. Develop
  5. Test
  6. Launch

Process.png

As can be seen in the above diagram, the process is not entirely linear, but has an "iteration loop" between Design, Develop and Test. This allows for flexibility in the development process and provides the opportunity to test designs in parallel with design and development.

Discover

Library:Web Design Process/Discover

Define

Library:Web Design Process/Define

Design

Library:Web Design Process/Design

Develop

Library:Web Design Process/Develop

Test

Overview

Testing will take place over multiple iterations, in parallel with as much of the design and development as possible. There are three main phases to testing, though each of them will most likely be iterated multiple times. I order of increasing complexity they are:

  • Message Analysis: 5-Second Test,
  • Task Analysis: Navigation Test, and
  • Task Analysis: Interaction Test.

Each of each type of test has the same basic elements, as laid out below:

  • Goal
  • Requirements
  • Design
  • Analysis

Message Analysis: 5-Second Test

Goal

  • To provide context that the primary message is received so that users understand what this site is trying to accomplish.
  • Do they “get it”?

Requirements

  1. A mock-up prototype of the screen. It does not need to be interactive, but should have copy (text) on it.
  2. A laptop to display it on is ideal, though a printout would be sufficient.
  3. A script. See "Questions" below.
  4. A helper. The test can be done solo, though it is easier to manage in pairs.
  5. Participants. Choose a high-traffic area, such as the IKBLC. The participants are therefore likely to be mostly undergraduates. Try to select from a range of people, but input from staff and faculty is not critical at this stage.

Design

  • Create a script that you can use to talk to participants, such as the following:

    Hey there, do you have 2 minutes? Can you help me with something? I work for the library and I need your opinion on something. We’re designing a new web site and we want to know if we’re doing it right. In a moment, I’m going to show you a web site and for just 5 seconds and I want to see if you can understand what this site is trying to do.

    • It is not necessary to memorize the script exactly, but try not to vary your introduction and questions too much as they may add unnecessary variation to the results.
  • For questions, use something like this:
    1. "What did you see?"
    2. "What do you think the site is trying to do?"
    3. "If you were to [perform a typical action], how would you do it?"
      • For example, in the Search Portal test, the question was "If you were to look for a book, how would you do it?".
  • Come up with a pass/fail metric. Most likely, it is whether they can satisfactorily answer Question 3 above.
  • Set up a spreadsheet called "Test Results" of something similar for recording your results on. Using a service such as Google Docs can make collaboration on this easier. Some suggested columns include:
    • Participant ID. This is useful to keep track of participants during analysis.
    • Participant Type, i.e., student, faculty, librarian, other staff, visitor, etc. This is helpful for demographic breakdowns. If it is not clear which group the participant is in, make sure to ask. Also, make sure to specify "librarian", as they will appreciate evidence that they have been consulted.
    • Q1-Q3. Try to note down as much information as possible from their responses.
    • Pass/Fail
    • Other Keywords. This can be done later by referring to the responses to Q1-Q3. A simple keyword analysis can be done, looking for the presence of certain terms or their synonyms, such as "search", "image", "tab" or "catalogue".
  • Try to get at least 8 participants per session.
  • Perform at least 5 sessions, or until pass/fail ratio is stable and satisfactory.

Analysis

  • The analysis at this stage is quite simple. Calculate how often the various terms are used (percentage of total). Calculate the pass fail percentages per session, as well as the overall pass/fail rate. Graphing the change in the pass/fail ratio can graphically communicate the effect of the testing procedure:
    Lib web pass-fail.png

Task Analysis: Navigation Test

Goal

  • Is the navigation easy and helpful?

Requirements

  • A navigation prototype. It should be low-fidelity but usable for testing labels, copy and options.
  • A testing environment consisting of:
    • 2 laptops, a mouse, and an extension cord
    • A table & chairs
    • A sign, saying "FREE CHOCOLATE BARS! Help up test our design for x minutes" or something similar.
  • Guerrilla testing software, such as Silverback.
  • Chocolate bars, or similar incentives.
  • An assistant. You will be busy with the person you are testing, so it helpful to have a person to assist and field questions from passersby.
  • A high-traffic, public location, such as the main foyer (Level 2) of the Irving K. Barber Learning Centre.
  • Participants. Guerrilla-style testing means that you will not have a lot of control over the demographics of participants. This is not too important in this test, but becomes more of an issue in the next one.

Design

  • Design a set of tasks that lead participants to perform all of the options available in the UI. These tasks should be created with the assistance of the Librarian Consultation Group. If there are more complex options, make sure that there are multiple tasks that cover most of the primary uses.
  • The tasks in this test are just to see if users are heading in the right "direction". There is no need to them to continue with the task once they have ade their original navigation decision.
Sample Tasks:
  • Here are the tasks used for the Search Portal navigation test, for reference. They are not ideal, and could have been improved with more librarian consultation.
  1. Please show me where would you look to see if the library has a copy of the book titled The Tipping Point by Malcolm Gladwell.
  2. You are taking English 112 and your professor tells you that "Strategies for University Writing", an online document, is available on Course Reserve. How would you go about finding it?
  3. You are in Woodward Library and you would like to locate an illus­trated encyclopedia about trees; where would you look to see if it’s at Woodward?
  4. Where would you find a journal article on how tropical forest fires impact the environment?
  5. You have discovered that a former professor at UBC has an unpublished dissertation on the exact topic that you are studying. Where would you locate it?
  6. In your psychology class, you are studying the effects of attention deficit disorder in the classroom. Where would you find books on helping students with ADD succeed in school?
  7. You are working on a Political Science project and you want to track down the proceedings from the House of Commons from last year. How would you do that on this site?
  8. You are doing a research study on global warming; please tell me where you would look to see if the library has any DVDs about global warming.
  9. You have heard that UBC has a digitized collection of Vietnam War-era protest posters available online. Where would you locate them?
  10. You are doing a lab on the reproductive habits of fish in your biology class. Your professor has recommended that you use “Web of Science” database to find relevant articles. How would you do that on this site?
  11. You want to perform statistical analysis on the travel patterns of Canadians overseas. Where would you go to download information to work on?
  12. You are writing a paper for a course in computer science. Find the 2001 article titled “Internet Under Siege” by Lawrence Lessig in the journal called Foreign Policy.
  13. Where would you look to locate the most recent issue of The Journal of the American Medical Association?
Test Structure:
  • ~13 tasks, ~3 tasks/test (keep sessions 5-10 mins), ~20 tests/session, ~3 sessions
  • discussion, analysis, design, development between each session
  • keep tasks the same between sessions for comparative analysis

Analysis


Task Analysis: Interaction Test

Goal

  • Can people find what they’re looking for?

Requirements

  • same as Navigation Test
  • more focus on specific user groups, if possible. Now is the time to invite Librarians to do testing. Communicate clearly the goals of the test, and let them know that a chance for more feedback will be forthcoming

Design

Questions:
  • specific and interaction-focused tasks
  • can they achieve their goal?
Test Structure:
  • modify Navigation tasks based of feedback from previous test and further consultation with Librarian Consultation Group
  • same task/test/session structure
  • at least 3 sessions, more if possible.
  • focused sessions with key patron types?

Analysis

Launch

Library:Web Design Process/Launch