1. The document discusses redesigning a library website based on user research and usability testing. It emphasizes understanding user needs and involving both librarians and technical staff in the redesign process. 2. Various user research methods are described, including usability testing, analytics, card sorting, and patron modeling to understand how different groups use the site. 3. The redesign process should include staff buy-in through sharing research findings and soliciting input. Ongoing evaluation and evolution of the site is also important.

1. Taking the Reins: Website Redesign by the Librarians, for the Users Mark O’English Washington State University Pullman, WA [email_address] Pacific Northwest Library Association Annual Conference Post Falls, ID. August 7 th , 2008

3. What we told our tech people we wanted…

4. What our tech people turned it into…

8. Google Analytics: How To http://www.google.com/analytics/ (or just “Google” Google Analytics ) Once you sign up, it’ll give you a piece of complex coding similar to this: <script type=&quot;text/javascript&quot;> var gaJsHost = ((&quot;https:&quot; == document.location.protocol) ? &quot;https://ssl.&quot; : &quot;http://www.&quot;); document.write(unescape(&quot;%3Cscript src='&quot; + gaJsHost + &quot;google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E&quot;)); </script> <script type=&quot;text/javascript&quot;> var pageTracker = _gat._getTracker(&quot;UA-3540679-3&quot;); pageTracker._initData(); pageTracker._trackPageview(); </script> Have your tech people paste that coding into the end of every website you want to track. Then tell Analytics you’re ready to go…

9. Google Analytics provides… Data on how frequently, and for how long, individual pages are being used.

10. What search terms people found your pages with. What sites people came to you from. What languages their browsers are set to. Their computers’ technical capabilities. And much much much more…

12. Patron Modeling Three questions: 1. Who are your user groups? 2. What does each user group want? 3. How will each group look for it?

14. Our set-up: Testee in the middle at the computer. One observer perched on each desk wing, looking over their shoulders.

15. BEFORE AFTER BEFORE AFTER

18. Trying to break out of our own blind spots: Usability testing before design.

20. Card Sorting

22. Staff Buy-In Your internal staff need to feel like… a) they had a voice in it, and b) its worthwhile. Share your process: Everything we just talked about gives you support! “ Usability showed our patrons did…” “ Website statistics shows that nobody uses…” “ We looked at our users and saw that group X was not represented in…” Solicit staff input!