I’ve taught Writing for the Web for Library Juice Academy for several years, the last time being this past March 2018. And I’m so pleased that the fabulous Heidi Burkhardt will be adapting it and teaching it in the future. My colleague Nicole Capdarest-Arest and I co-created this course back in 2014, and it’s been so much fun to teach.
So now seemed like a good time to share the lectures (I’m also sharing lectures from my other course on Usability Testing).
Much of the content is also covered in my book on writing effectively. Feel free to use and adapt, and I hope you enjoy!
I’ve taught Do-it-Yourself Usability Testing for Library Juice Academy for the past four years. I’m stepping back from teaching due to other commitments, so thought it would be a good time to share my lectures publicly. These were last updated about a year ago.
Hope these prove useful even outside the context of the course. Much of the course content is also reflected in my usability testing guide from 2014. Feel free to use, adapt, and share these videos!
At the University of Arizona Libraries, we’re replacing Millennium and Summon with Alma and Primo later this month as our library services platform and primary discovery tool. Needless to say, it’s a critical piece of the library’s experience. It’s the main way people find library materials (both digital and print), access full text, request holds, and manage their accounts. So checking and improving its usability is key.
The team
The focus of our (small but mighty) UX team the past couple months has been Primo. It’s critical, so we were all in.
We hired a grad student intern from the School of Information, Louis Migliazza, who focused his summer internship on Primo usability. That was awesome. Student worker Alex Franz and content and usability specialist Cameron Wiles took turns pairing with Louis for the testing.
We also met weekly for an hour with Erik Radio, our metadata librarian and product owner for Primo. He helped us come up with solutions and worked on the backend to make improvements, contacting Ex Libris when needed.
And we met weekly with the broader Primo implementation and discovery teams, which included stakeholders from throughout the library and were led by our fearless project manager, Joey Longo. At these meetings, we regularly shared our findings and gathered feedback on our plans to address them.
The methods
Louis and Erik’s leadership over the past 6 weeks made it possible for us to conduct a ton of usability testing and make significant customizations to the interface. Building on preliminary research and testing we’d started earlier in the spring, we ultimately tested 22 tasks with 91 participants.
We used Tiny Café (our pop-up food/drink station in our Main Library lobby) to recruit passersby for testing, who were by and large undergraduate and graduate students. We had a handful of library staff stopping by, too. We did this on Tuesdays and Wednesdays for two hour blocks (4 hours a week total). Ultimately, we held 27 hours of Tiny Café, intercepting 84 passersby.
Tiny Café
We’d usually test 2 or 3 tasks per participant. And the tasks changed nearly every week as we learned what we needed to learn, made adjustments to the interface, tested again, and/or moved on to the next tasks we needed to test.
We also recruited faculty with help from our liaison librarians. The majority of those sessions were lengthier, moderated, remote tests using Zoom.
All told, participants included 36 undergrads, 31 grad students, 7 faculty, 7 library staff, and 10 community users.
Findings
Searching and filtering
Participants were 100% successful at:
Finding a specific item by title
Searching for journals by topic or title
Renewing an item
One grad student said, “Looks pretty intuitive, pretty easy to navigate.” And one undergraduate said, “I think it’s easy to find what you’re looking for.”
Original Primo basic search interface, where participants would start their search
They were mostly successful at using filters, specifically:
Using facets to narrow results (84% success)
Finding an item at a specific library (83% success)
Some of those who weren’t successful would only use the search box to narrow their results, avoiding filters entirely. Or they would skim through their results to try and find an item like what we were describing. (In our scenarios, we intentionally didn’t ask them to “use the filters” to avoid leading them in that direction. Rather, we asked them to “narrow your results to only books from the last ten years” and “find a book that’s in the Health Sciences Library.”) That said, we did make a number of changes to our filters along the way (described later on), hopefully making them a bit more useful.
Original Primo search results page, without customizations
Signing in
We observed some issues with signing in, too. Only 83% of people successfully signed in to see the due dates of checked out items. To address this, we changed the language in the top-right utility navigation from “Guest” to “Sign in/account.” We also removed the word “English” along with the language options, which caused confusion (and disappointment, since Spanish wasn’t an option and we’re a Hispanic-serving institution).
Customized utility navigation
Saving items
Interestingly, only 2 of 8 students successfully saved an item to their account. But then 4 faculty and PhD students were successful on first attempt. This might tell us that undergrads don’t tend to think of or use this feature. It doesn’t fit with their mental model when it comes to saving articles.
When asked, they said they would use other methods outside the tool, such as bookmarking the URL or emailing themselves. We didn’t make any changes to the interface based on this, but found it interesting.
Only faculty and PhD students were successful in using the pin icon to save their results
Requesting items
The most challenging task was requesting a hold. Only 40% of participants were successful. This is because you have to be signed into Primo in order to see the “Request” link. If you’re not signed in, the option doesn’t appear. We ran a subsequent test where we were already signed in, and 100% of participants were successful.
By default, Primo has a yellow bar that says “Sign-in for more options,” but people didn’t notice this most of the time. Especially since it’s in the “View it” section of the records, and people tend to be looking near the “Find it” section.
“View It” and “Find It” sections of Primo item records, without customizations
We found it problematic that the interlibrary loan option appears when not signed in, but the hold option does not. In contrast to requesting a hold, 90% of participants were successful in requesting an interlibrary loan, using the link: “Borrow this item from another library.” By requiring users sign in, the interface essentially hides functionality from the user, causing a significant usability issue.
Ideally, we think, the “Request” link should always appear and upon click, the user is prompted to sign in. (This is how our current catalog works). But with this not being possible, the only thing we could really do is customize the message. So we changed it to say: “Want to place a hold? Sign in.”
Custom text to indicate people need to sign in to place holds
User impressions of usability
A few weeks into our testing, we decided to add on a System Usability Scale survey after each session to gather overall impressions in a more systematic way. Of the 32 people who filled it out:
89% thought various functions were well integrated
84% would use Primo frequently
83% thought most people would learn to use Primo very quickly
78% think Primo is easy to use
70% were very confident using Primo
Needless to say, we were pretty happy with these numbers.
Other customizations
Changing terminology
We found that some of the default terminology wasn’t ideal. For example, one grad student said, “Loans? I think about money…I just don’t like the word ‘loans.’”
Here are a few terms we updated:
Item in place > In library
Full text not available > Available to request
Fetch item > Find a specific item
Expand my results > Include results beyond UA Libraries
Loans > Checked-out items
Updating the homepage search box
To mimic existing Summon and Catalog options while focusing on the most common search behavior, we:
Created drop-down options for title, author, and call number
Put an Advanced search link in the bottom right
Added buttons to take users to the most common alternate starting points: See all databases and Find a journal
Simplified homepage search box
Removing less helpful or redundant elements
To make things as intuitive as possible, we:
Removed the vendor product name
Removed the sign-in banner for users on campus
Removed redundant title attributes from the tile menu
Removed Personalize option (redundant with subject filters)
Reduced and re-ordered the Send to options
Customized “Send to” options and ordering
Making search results and filters more intuitive
To reduce cognitive load, we:
Moved filters from the right to the left
Re-ordered filters so that the most-used options are at the top
Changed “Availability” to “Show only” as a filter category
Customized the icons to be more consistent and recognizable
Removed filters that were confusing, less useful (e.g. “Call number range”), or redundant (e.g. “Location” in favor of “Library”)
Reduced number of items displaying by default underneath each filter category
A preview of our filter customizationsCustomized icons for book, article, and multiple versions
Putting content at point of need
To help users along, we:
Added a Locate button to print records that takes people to the call number guide
Put searching tips below the Advanced search option as well as the Library search landing page
Added suggested librarians for when people search particular disciplines
Added a link to WorldCat above the search box
Customized primary (tile) menu
Next steps
This is a huge change for our users, but we’re feeling pretty good about where we’re at. We did a lot of testing and a lot of tweaking, and participants were overall successful at completing the primary tasks we’d identified.
We go live on July 20(ish), and are sure to discover more UX concerns once we have people using the system in their daily lives.
We’ll continue to gather feedback and make adjustments as needed.
Perhaps one undergraduate said it best: “I think I liked the old interface better because I’m comfortable with it…I’m sure once I get used to [Primo], it will be ok.”
Last fall, I was asked to help lead an ambitious, library-wide project. It aimed to reimagine our strategic planning process through an inclusive, human-centered, design thinking approach. Having just moved into our library administration (from our technology team), it was a perfect opportunity to foster and support UX thinking across the organization.
With outside consultant Elatia Abate to guide us, over 117 library staff worked in teams to gather information, empathize with our end users, and iterate on solutions to grand “How might we…?” challenges. Library staff got to practice conducting user interviews, synthesizing findings, creating personas, and prototyping ideas. They also worked together with staff from other departments, building trust and long-lasting relationships.
I presented our work through a hands-on workshop at this year’s Designing for Digital back in March. Then in May, the University of Arizona Libraries unveiled one of the outcomes from this project: our new strategic map.
Slides from the March presentation, titled “Design Thinking for the Masses: Creating a Culture of Empathy Across a Library Organization”:
I had the privilege of presenting as part of an online panel last October with my brilliant colleagues, Emily Daly from Duke University and Josh Boyer from NCSU. We talked some shop and had a lot of fun. Check out the full recording if you’re interested in learning more about what it’s like to do UX work in large academic libraries.
This session was organized by the University Libraries Section (ULS) of the Association of College & Research Libraries (ACRL). The first session was pretty popular, so we hosted a “part two” in February where we dived into more details and examples of our work. Here it is for those of you who missed it!
I work at the University of Arizona (UA), and in talking with a colleague across campus a few weeks ago, we realized that there is no venue for like-minded UXers to get together.
So we formed an informal group, UX@UA. Everyone interested in user experience is welcome! Join the conversation in our UX@UA Slack Team (use your UA email) and our community in Meetup.
At our first meetup in August, we had about 20 people attend from all across campus, including web designers, web developers, graphic designers, business analysts, and teaching faculty. We watched a webinar on selling the value of UX.
At our second meetup in September, we had just a handful of people, including faculty and grad students. We watched a webinar on identifying users’ “top tasks,” and talked about future collaborations.
At our third meetup, we’ll hear from two members on their recent UX projects. Hope to see you there!
2019 update: We have grown to over 300 members and now have an official UX@UA website through the University of Arizona!
I presented a webinar for LibUX last week that was super fun. I talked about knowing your readers, organizing your content, and writing with clarity.
Check out the full recording:
At Designing for Digital last month, I presented a 4-hour workshop on Building Your Content Strategy Toolkit. I appreciated hearing about other librarian’s content challenges, brainstorming over how to tackle them, and learning from each other throughout the day.
I’ve posted my slidedeck below and made it available along with associated activities at tinyurl.com/d4dcontent.
From the description:
Do you struggle with web content that is complicated, outdated, or irrelevant? In this workshop, learn how to identify content challenges, define messaging, create standards and style guides, and establish workflows to keep things going once a project is over. Whether you’re in the midst of a web project or just trying to get your feet wet, this workshop is for you.
I’m excited to attend Code4Lib for the first time this week. While I don’t code currently, I do manage a team of uxers, designers, and coders. I’m looking forward to meeting likeminded colleagues and learning lots!
Mike Hagedon is our dev team lead and I’m our design team lead, and we’ll be presenting a poster on our design + dev experiments in agile methodologies. I hope if you’re attending you’ll come chat with us! Learn what we’ve tried, where we’ve succeeded, and where we’ve failed.
We also want to hear others’ perspectives and experiences. The poster will be interactive, so we’ll ask you to annotate it with questions, examples, and ideas. Here is the poster we have so far:
Writing plays a role in almost everything we do. It’s how we document our knowledge, share our stories, and ask our communities for help. It’s a tool to teach, influence, and persuade those around us. And in today’s digital age, we’re all publishers, sharing content with the world at the push of a button (literally). From webpages, to signage, to emails – writing is fundamental to our everyday lives.
Sadly, there is a lot of mediocre content out there: policy-driven websites with mountains of text, building signs that don’t actually tell you what you need to know, convoluted emails that leave you wondering, What was the point of that? Today’s reader is bombarded with endless streams of information and simply doesn’t have the time to sift through and make sense of it all.
Let’s do our part to end the madness. Writing Effectively in Print and on the Web: A Practical Guide for Librarians encourages you to put your readers at the heart of all your content, ensuring that it is engaging, relevant, and useful. You’ll learn techniques to write with clarity, precision, and purpose, which will serve you well in both your professional and personal life.
