Search:

Product Information All Elsevier Sites   Advanced Product Search
SiteStat.jsp
Library Connect Volume 3.2

ASK UCD

Chris Jasek of Elsevier’s User-Centered Design Group answers your usability questions.

Q: Should my library staff have some usability expertise?

A: Yes, definitely. Since the majority of library users visit the library online to find the information they need, it is critical to have usable online services. Considering the usage patterns of the library today, I believe many libraries have underinvested in the design of their online services and instead continue to overinvest in the physical library.

So, how might you gain that usability expertise in your staff if you don’t already have it? First, you might consider hiring someone with this skill. A number of library schools have programs that focus on information architecture and usability. The University of Michigan’s School of Information is one of them and two graduates from this program are members of Elsevier’s User Centred Design Team. You might also consider training existing staff. The Usability Professionals Association (External link   www.upassoc.org) offers an annual conference where practical usability training can be received. Another good usability related conference for librarians would be the IA Summit (External link   www.iasummit.org) which focuses more on design and information architecture. A third option would be to tap into other resources at your institution. Look for students in human factors, industrial engineering, engineering psychology or computer science, whom you might fund as research assistants or enlist to do student projects related to library usability. Fourth, there are always consultants available for hire, but this option is short-term and less of an investment in the future skills of your staff. As a final thought, consider establishing a usability working group at your library and then give that group some authority to influence the design and usability of your systems.

Printer-friendly version   Printer-friendly version