{"id":22,"date":"2014-11-25T21:21:27","date_gmt":"2014-11-25T21:21:27","guid":{"rendered":"http:\/\/apps.lib.ua.edu\/blogs\/webservices\/?p=22"},"modified":"2014-11-25T21:23:26","modified_gmt":"2014-11-25T21:23:26","slug":"usability-studies","status":"publish","type":"post","link":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/2014\/11\/25\/usability-studies\/","title":{"rendered":"Usability Studies"},"content":{"rendered":"<blockquote><p>&#8220;It is far better to adapt the technology to the user than to force the user to adapt to the technology.&#8221;<br \/>\n&#8211; Larry Marine<\/p><\/blockquote>\n<p><a href=\"http:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/usability-l.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-medium wp-image-30\" src=\"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/usability-l-300x269.jpg\" alt=\"usability-l\" width=\"300\" height=\"269\" srcset=\"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/usability-l-300x269.jpg 300w, https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/usability-l.jpg 547w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a> Web services knew that usability studies would be imperative for the successful redesign of the website. To build a better site we needed to see exactly how students were using it. By user experience standards, watching users interact with the site is \u201cthe most effective way of understanding what works and what doesn\u2019t in an interface&#8221; <a href=\"http:\/\/www.nngroup.com\/articles\/task-scenarios-usability-testing\/\">(Nielsen, 2014<\/a>).<br \/>\nOur objectives for the study were simple:<\/p>\n<ul>\n<li>How do students navigate through the website?<\/li>\n<li>How long will it take to complete a task?<\/li>\n<li>Do the libraries naming conventions align with users&#8217; perspectives?<\/li>\n<\/ul>\n<p>The usability study process started in April, and after approval from the IRB and obtaining generous Target gift card incentives during the summer, we were ready to find our study population at the start of the fall semester. We wanted to test students who had the least experience with the library website, leading us to freshmen and sophomores. We maintained the underlying thought that a website\u2019s navigation should be so universal, that novices and experts alike can find exactly what he or she is looking for. To bring in students for our studies, we advertised everywhere; flyers for participation in Week of Welcome orientation bags, posted calls on LibGuides, and flyers in lecture and residence halls across campus.<\/p>\n<p><a href=\"http:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0423.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-35\" src=\"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0423-300x296.jpg\" alt=\"IMG_0423\" width=\"300\" height=\"296\" srcset=\"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0423-300x296.jpg 300w, https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0423-1024x1012.jpg 1024w, https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0423-900x889.jpg 900w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p><strong>Tasks<\/strong><br \/>\nTo get started, we included a brief survey about website usage and knowledge. We then tested students on our current site, asking if they could complete various tasks. Tasks were common question or situations that a student would face at the library. A few examples:<\/p>\n<ul>\n<li>Locate tomorrow\u2019s opening hours for Bruno.<\/li>\n<li>Find instructions on how to print.<\/li>\n<li>Locate the contact information for the circulation desk.<\/li>\n<li>Locate a subject guide that is specific to your major.<\/li>\n<li>Where is the 3D printing studio located?<\/li>\n<\/ul>\n<p>We allowed students to take as much time to complete tasks, but also had a time-limit to determine successful or incomplete tasks, which was anything over 2:00 minutes. Students were unaware of the time limit. As designers of the navigational structure of the site, we felt that spending more than 2:00 minutes to locate basic information would be a failure in the design. We also asked students to talk aloud during their tasks, and express their frustrations, concerns, or other comments about the interaction.<\/p>\n<p>For navigation testing, we needed to test on at least 5 participants. Jakob Nilesen, a well-known usability expert, discovered years ago that 5 users could point you to at least 85% of the issues of the site. Of course, we would have preferred to test a larger group of students, but determined that a small group would help us see what the more obvious issues of the site are, especially for basic user tasks. If a majority of users had the same issues and frustrations with the identical tasks, then that would be a good indication to review content. Not to worry though, usability studies will now be a part of the workflow as the website changes over time.<\/p>\n<p><strong>Observations<\/strong><\/p>\n<ul>\n<li>Students preferred to browse for an answer rather than search, and resorted to search only after all other options had been exhausted.<\/li>\n<li>Students could not determine that the library header linked to branches and found it very confusing<\/li>\n<li>Students used the left-hand menu to navigate, and seldom used the main content area<\/li>\n<li>If unsure of an answer, students always visited \u201cNeed Help?\u201d or \u201cAsk a Librarian\u201d<\/li>\n<li>Multiple participants used Scout as a site search and demonstrated unfamiliarity with the functions of Scout<\/li>\n<li>If students could not find an answer between 00:30 and 01:00, they would often give up the task.<\/li>\n<\/ul>\n<p>The most common incomplete tasks are as follows:<br \/>\n(Bold entries indicate tasks directly related to site navigation or design)<\/p>\n<ol>\n<li>Find today\u2019s issue of \u201cThe International New York Times\u201d<\/li>\n<li><strong>How long can an undergraduate check out a book? <\/strong><\/li>\n<li><strong>Where is the 3D printing studio located? <\/strong><\/li>\n<li>Find the journal \u201cScience\u201d<\/li>\n<li><strong>Find a video tutorial on how to search \u201cScout\u201d<\/strong><\/li>\n<li><strong>What do you do if you have problems logging into online resources? <\/strong><\/li>\n<li><strong>Locate a research guide that is specific to your major. <\/strong><\/li>\n<\/ol>\n<p>We observed that branch specific information and inconsistent link names made it difficult to locate information. Students seemed to expect that similar types of services or resources would be located together. A few examples:<\/p>\n<ol>\n<ol>\n<ul>\n<li>Computers with software<\/li>\n<li>Audio and visual equipment to check out with circulation\/borrowing<\/li>\n<li>Research guides linked with subject liaisons<\/li>\n<li>Tutorials related to a topic to be included with that specific topic\/area<\/li>\n<\/ul>\n<\/ol>\n<\/ol>\n<p>When students used the search bar, they would enter their query into Scout, and then continue searching anything and everything once they reached the Scout interface. Also surprising was how little students interacted with the main content area, and the overwhelming preference to use the left menu bar. Students seldom used the tabbed options on the search bar (Scout, Databases, E-Journals, Digital Archives, and Site).<\/p>\n<p><strong>Card Sorting<\/strong> <a href=\"http:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0630.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-51\" src=\"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0630-300x225.jpg\" alt=\"IMG_0630\" width=\"300\" height=\"225\" srcset=\"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0630-300x225.jpg 300w, https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0630-1024x768.jpg 1024w, https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/IMG_0630-900x675.jpg 900w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><br \/>\nWe ran three card-sorting sessions to see how students reacted to certain terms from the library site. We are still scheduling these sessions, but there were a few front-runners for content labels.<br \/>\nAs top-level navigation categories, students prefer:<\/p>\n<ol>\n<ol>\n<ul>\n<li>\u201cUsing the Libraries\u201d over \u201cServices\u201d<\/li>\n<li>\u201cResearch Tools\u201d over \u201cResearch\u201d<\/li>\n<li>\u201cHow Do I\u2026?\u201d over \u201cLibrary Help\u201d.<\/li>\n<\/ul>\n<\/ol>\n<\/ol>\n<p>The trend seems to be choosing specific names with actionable behavior, over vague terminology.<br \/>\nNot only did we see the choice for specific and actionable terms, but we also saw students combining content areas for simplification. For example:<\/p>\n<ol>\n<ol>\n<ul>\n<li>\u201cWhere to Study? \u201d over \u201cGroup Study Rooms\u201d and \u201cStudy Carrels\u201d<\/li>\n<li>\u201cClasses, Workshops, and Tours\u201d over \u201cLibrary Instruction\u201d and \u201cWorkshops\u201d<\/li>\n<\/ul>\n<\/ol>\n<\/ol>\n<p>Overall, the Web Services team found the usability sessions to be incredibly informative. By watching students interact with the site, it was easy to see what aspects of the design needed to change, such as better explanations about services or resources, consistent font types and sizes, consistent link names, navigational menus, front page content. <a href=\"http:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/grumpy-cat-meme-website-awful.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-medium wp-image-36\" src=\"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/grumpy-cat-meme-website-awful-300x199.jpg\" alt=\"grumpy-cat-meme-website-awful\" width=\"300\" height=\"199\" srcset=\"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/grumpy-cat-meme-website-awful-300x199.jpg 300w, https:\/\/apps.lib.ua.edu\/blogs\/webservices\/files\/2014\/11\/grumpy-cat-meme-website-awful.jpg 470w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a> Users still seek a more streamlined website experience that is easier to navigate and interact with on a regular (and often, irregular) basis.<\/p>\n<p>It is the mission of our department to create a website that provides easy access to library resources and services. The processes laid out for this redesign will help us achieve that mission and we can provide users with a website that successfully places them at the center of the design.<\/p>\n<p>References<br \/>\nNielsen, Jakob. (2000, March 19). Why You Only Need to Test With 5 Users. Retrieved from <a href=\"http:\/\/www.nngroup.com\/articles\/why-you-only-need-to-test-with-5-users\/\">http:\/\/www.nngroup.com\/articles\/why-you-only-need-to-test-with-5-users\/<\/a><br \/>\nNielsen Norman Group. (2014, January 12). Turn User Goals into Task Scenarios for Usability Testing. Retrieved from <a href=\"http:\/\/www.nngroup.com\/articles\/task-scenarios-usability-testing\/\">http:\/\/www.nngroup.com\/articles\/task-scenarios-usability-testing\/<\/a><\/p>\n<p>Images<br \/>\n<a href=\"www.worldusabilityday.org \">www.worldusabilityday.org <\/a><br \/>\n<a href=\"www.grumpycatpics.com\">www.grumpycatpics.com<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;It is far better to adapt the technology to the user than to force the user to adapt to the technology.&#8221; &#8211; Larry Marine Web services knew that usability studies would be imperative for the successful redesign of the website. To build a better site we needed to see exactly how students were using it. &hellip; <a href=\"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/2014\/11\/25\/usability-studies\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Usability Studies<\/span><\/a><\/p>\n","protected":false},"author":449,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[515,20208],"tags":[],"class_list":["post-22","post","type-post","status-publish","format-standard","hentry","category-usability","category-website"],"_links":{"self":[{"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/posts\/22","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/users\/449"}],"replies":[{"embeddable":true,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/comments?post=22"}],"version-history":[{"count":38,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/posts\/22\/revisions"}],"predecessor-version":[{"id":64,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/posts\/22\/revisions\/64"}],"wp:attachment":[{"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/media?parent=22"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/categories?post=22"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/tags?post=22"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}