york

5 UX insights for library web-design

For the last few months I’ve been leading a project to completely redo my library’s website from scratch. It has been full-on, and rewarding, and most importantly the new site is live as of midday today.

I’ll post about the project process later, but for now I want to focus on what the UX fieldwork with our users told us, as these insights will hopefully be useful for anyone redesigning their org’s website.

I’d love you to go to york.ac.uk/library (opens in a new window) and take a look, then come back here and tell me what you think!

This post focuses on the organisation of the site; part 2 will be on the content.

Use colour with intention

As you can imagine, we’re working within the limits of the University CMS (Content Management System) and don’t have a lot of control over colours - most of the content types are white, but several can be set to cream, teal or dark blue. I must admit when I first started designing the pages, I just used colour to mix things up a bit and add some visual interest - a strip of colour here, a nice accent there. But the users told us in the UX sessions that they wanted the colours to mean something - they expected consistency across the pages (for example opening times always one colour, as shown below; quotes from students always another colour) and in particular they wanted the darker colours to signify something especially significant - a call to action, or really essential information.

The teal strip showing opening hours. The fact the Help Desk opening hours are on there too, and the fact that the Easter vacation is explicitly mentioned even though the hours aren’t changed, are both as a direct result of student suggestions during the UX.

Topic based organisation beats audience based navigation

A perennial debate for designing anything for users, websites included, is: do we organise things by theme, or by who is accessing information? Do we say ‘PGs go here, UGs go here’ or do we talk about space on one page, resources on another?

In a literature review carried out at the start of the project, my colleague Alice Bennett wrote, on the topic of a particular study finding topic-based organisation to be significantly preferable: “This is potentially a more inclusive approach, as it better allows for intersectional user identities and better accommodates search behaviour, with users typically searching for specific information, rather than looking to find themselves in the menu.”

This was really borne out by the UX. I asked one distance-learner where all the distance-learning information should sit in the new structure. They said “I wouldn't separate it. Because you don't like to treat yourself as a second class [citizen] and just look for, okay, where is the info for the distant learner people?” And to Alice’s point about intersectionality, we also had an International Students guide - many of our distance learners are also international students, so where do they look? And of course the contents were extremely similar. In the end we have a nice ‘basic introduction to the library essentials’ page which is for everyone: universal design wins again.

Your users will tell you which compromises are worth making

Compromise is inevitable in this sort of process - library websites have too much complex information and too many responsibilities to our users to just make a super slick, neat website. The top-level navigation is one of the biggest changes between the old site and the new - the old site had about 15 overlapping ways in to the info down the left of the screen; the new one has just six top-level landing pages.

The top-level navigation of the new site

We thought loooong and hard about how to group the information - we spent weeks planning this before we even had access to the CMS. But still we changed it during the UX process, because our users told us the compromise we’d made wasn’t the right one.

Our info for Researchers was split across the Skills & Training page you see listed above, and a Facilities page. The Facilities page has loads of useful info, but no flow and no cohesion - and more importantly when we spoke to Researchers in the fieldwork we set them tasks to find Open Access info, and they couldn’t do it. The split of info which had internal logic for us simply didn’t make sense for the user, and they couldn’t get to what they needed.

So we now have Research and Digital Creativity. This too is a compromise because that pairing isn’t as natural as the others (skills & training, for example) but those are two important aspects of the library offer that are really easy to find, so it’s a better way to go.

KnowING it’s important to invert the pyramid isn’t enough!

We all know about inverting the pyramid, right? I talk about it all the time. But knowing how important it is and ruthlessly acting on it turned out to be two different things… Even when I actively tried to do it with the website, I wasn’t doing it enough. One participant in the UX literally said ‘this page is upside down’… It’s so tempting to try and set the scene and lead people through the information, but they just want the important stuff at the top and that’s what we should be doing.

So: invert the pyramid, and invert it hard. (And then come back later and check it’s still fully inverted.)

Pictures have more than cosmetic valuE

“I’m never going to read that.” This a common refrain from students when faced with dense, lengthy text. We tried to simplify and reduce where possible, but sometimes in libraries there just IS detail - so breaking that up with images really helps. It’s not just that the images can help illustrate what you’re talking about, it’s that they make the user more likely to read even long passages of text because it’s broken up into chunks. It makes it manageable.

We also made sure to use the same image for thumbnail links to pages, as you find at the top of the pages themselves when you click the links. This reassures the user that they’ve clicked the right thing, and creates a sense of familiarity which helps make the info less intimidating.


A part 2 post detailing what the users told us about the Content of the site will be coming soon!

How do you truly embed UX at an institutional level?

At the glorious UXLibs IV Conference (more on which below), Michelle Blake and I presented on embedding UX at York. By this we mean, attempting to move the ethnography and design ideas / techniques / methods which sit under the User Experience in Libraries umbrella, from novel and niche to mainstream and, if you'll forgive the management-speak, Business As Usual. Part of the culture. 

We're not all the way there yet and don't profess to have completely nailed it, but it is something we've consciously tried to achieve in the Library and we're having come success with it. Some of what we've done is outlined briefly in the presentation below, to which I've added an explanatory sentence to most slides so they make more sense without us talking over the top of it.

I'd reccomend this post from Shelley Gullikson which nicely summarises several talks and sessions from UXLibs IV, and Andy Priestner's 50 Photos post gives a nice flavour of the conference as a whole.

Embedding ethnography Part 1: long term UX in the Library

The User Experience in Libraries Conference is looming next week, and I've got a series of UX related posts (not all by me!) lined up for this blog. (Read post 2, A UX Intern writes... here.) Apart from writing about last year's conference, and creating the UX Resource List for anyone interested in an introduction to the area, I've not really talked much about ethnography on here, but I've been doing a lot.

Apparently someone recently asked Andy Priestner (UXLibs Chair) what 'the next fad in libraries will be after UX'! To me this totally miscasts what User Experience in libraries is all about. Purely and simply, UX is an umbrella term for a suite of methods to help us understand our uses better, and design changes to that service so it works more successfully for those users. That is not a new or faddish need. It isn't going to go away. The methods may be new to libraries (in the UK at least; they're more established in the US and Scandanavia particularly) but there is a growing community of libraries and librarians getting amazing understanding and insight with them, so we'll continue to use them. More and more info pro jobs are starting to get elements of UX in the job description. This stuff is here to stay not because it is fashionable, but because it works.

The posts over the next two or three weeks will cover three projects undertaken at the University of York, including guest posts from UX Interns we had for two of them. The first covered Postgraduate students, the second covered specifically just Postgraduate Researchers, and the third, still ongoing at the time of writing, focused on academics. All of them have been fascinating and rewarding, but by no means plain sailing...

The Fairhurst Building at the University of York, the HQ for all our UX projects. Photo used by permission, copyright of Paul Shields.

The Fairhurst Building at the University of York, the HQ for all our UX projects. Photo used by permission, copyright of Paul Shields.

UX at York: project overviews

I'll go into more detail in subsequent posts but here's an introduction to each project.

  • Project 1: Summer UX. This was a 2 month project with the aim of building a UX Toolkit - essentially understanding the UX techniques and methodologies in a York context, see how they worked, what we could learn etc. We had an intern working part-time during the 2 months, and we used 5 ethnographic techniques across a total of 25 participants. These were all Postgraduates, both PGRs and PGTs, from a mix of disciplines.
  • Project 2: PGR-UX. The second project also featured an intern, and was more focused - we spoke to fewer people, and the participants were all Research PGs. We targeted people from specific departments, and really only used three of the ethnographic techniques.
  • Project 3: Understanding Academics. This project is absolutely huge and still on-going. It involves everyone in Academic Liaison, will last several months, and involves academics from every single Department at York. We have spoken to around 100 people in total for this, and used two ethnographic techniques. The analysis has just started.

Embedding ethnography

The key to our approach at York has been to try and integrate ethnography into our regular routine right from the start, rather than having a little UX silo where UX projects happen in isolation. We now try and utilise UX wherever appropriate in the Library, although quite honestly we've been better at embedding the ethnography than we have at the design-thinking / human-centred design aspect that completes (or continues) the UX-cycle, but that side of things is coming. We aim to consistently supplement our existing data collection methods with a nuanced UX approach, and because of the amount of work involved in ethnography and the sheer amount of time it takes, we target specific groups and areas we want to know more about and use ethnographic techniques with them. Each time we do, we learn more about that group of users then we've ever known about a group of users before. It's fantastic.

The five of us who attended UXLibs set ourselves up as available to be brought in on any wider projects happening in the library, to provide advice and guidance of if, where and how ethnography might be useful. So although the first project listed above, Summer UX, was primarily a way to try out UX in a York context, the subsequent two have been existing projects which have been deemed suitable for ethnographic input, and we've been brought in to advise on how best to go about it.

Next time will be the first guest post in a very long while on this blog - our first ever UX Intern, Emma Grey, has written about her experiences working with us when completely new to both libraries and User Experience, and the five ethnographic techniques she employed, including how she refined them as she went along. 


Header pic by the Library Photographer at the University of York, Paul Shields. Used with permission.