IL2009: Connecting Through “Lights, Cameras & Action”
Speakers: Michael Porter, David Lee King, and Sean Robinson

Sean Robinson started by talking about storytelling.  He showed us a video about the library, showing a woman finding a book at a library (an Amy Tan book incidentally) then read that book during her day — in the morning, at lunch, and at night after work.  Nice, positive, happy video.  Then the Library 101 Project launched with David Lee King & Michael Porter taking the stage.  They were both wearing disco-shiny-pants, jackets, sunglasses, etc.  Quite a fun entrance.  Library 101 includes a new video and a new website including a lot of content from many library world folks trying to explain what it’s about being in a library today, and what you need to know to succeed in today’s information environment.  A big point about the whole Library 101 project is to cut loose, relax, engage in informal ways with our communities.

They premiered the Library 101 video for the first time.  You can see the Library 101 website now.   Anyone can comment and add to the list of skills, resources, and ideas on the Library 101 site, so it’s now an interactive community project.  They also offer a Facebook page of which you can become a fan.

In addition to the video, there are a number of essays on what makes a Library “101″ today, including essays from Meredith Farkas, Stephen Abram, Cindi Trainor, Maurice Coleman, Roy Tennant, Helene Blowers, Janie Hermann, Jason Griffey, and yours truly :)   Check out the essays.

There is also a description of what Library 101 is, Library 101 skills, resources to help you build your skills up, and more.   The skills are divided into past, present, and future.  You can add your own content here too, so add away!

Incidentally, the website was designed by the same designers, SIDESHOWgraphix, who designed my website.

At the end of the session, they invited all audience members to begin participating by recording video live about what they want the world to know about libraries.

IL2009: Information Overload is the Devil

This was a shared session, and my half was about dealing with information overload – which is the devil.  I stand by that assertion.  I also stand by my assertion that information overload does indeed exist.  Anyone who says it’s a myth clearly isn’t as busy as the rest of us, or hasn’t studied the history of information overload over the last century’s progress, and/or simply hasn’t invited enough inputs into his or her life to know what it’s like to want to cry when you open your feed reader or inbox.

Anyway, you can view my PowerPoint on Slideshare and below.

IL2009

IL2009: Technology: The Engine Driving Pop-Culture-Savvy Libraries or Source of Information Overload

Speaker: Elizabeth Burns

Burns started by talking about texting, using mobile devices, and more often inspire poor reactions in libraries.  Some library staff believe that the public use of mobile devices in the library is a waste of time and distracts them from library resources.  Therefore some libraries ban cell phones.  Even worse, some libraries ban cell phone use by staff.  But if people are using these technologies, it shows that is an untapped option for service provision.  The Library Success Wiki can help you brainstorm good ideas for provoding more innovative, pop-culture-friendly services–roving reference with mobile devices, etc. Are we tech-friendly ourselves in our buildings?  Do we offer power?  Good, fast connections?  Are we helping to find people find digital media online?  Find free TV shows through Hulu?  She also touched on the problem of having one techie person in the library.  If they are the only person providing support for staff & patrons, they will burn out.  If they are the only ones suggesting technology projects, and are told “great – you do it!”, then they will burn out.  She suggests instead that you should form a group of trendspotters.  Don’t reinvent the wheel by having a bunch of local individual libraries doing their own thing when you can band together and do something better.  You have to practice these new technologies.  You have to fine tune projects after launch to continue to improve them.  Don’t invest all of your resources in one project, only to see a new trend emerge when you launch the other one too late in the game.  It’s play; it’s fun.  Expand your networks.

IL2009

IL2009: Trying Not to Filter: Internet Filtering Technologies Update

This is my session for Internet @Schools this year about the status of internet filtering, how it works, our own libraries testing of four internet filters, and our successful battle against a city council member’s proposition that the library begin filtering all public computes.  SJPL remains an unfiltered library, and I am proud of that fact.  This presentation gives some information about that experience and what internet filters are like today.

You can view my presentation on Slideshare and also below.

You can also view the original materials from the San Jose Public Library’s filtering challenge, something we created for our community when the filtering proposal was initially made.  We’ve preserved it on the website as it continues to be an important resource for other libraries and we do still occasionally get inquiries from the public about the outcome and reasons for the city council’s decision.  Some of these documents may add some understanding for folks working on internet filtering issues at their own libraries.

IL2009

IL2009: Selling Tech to Power in Tough Times

Speakers: Danis Kreimeier, Fred Cohn, Kim Bui-Burton, Stacey Aldrich, Kathy Gould

Customers expectations keep growing.  Resources keep shrinking.  We have to find ways to do new initiatives from within the organization.   Use the resources you have to do projects under the radar.

Tell people where you’re headed.

Give them the facts that support your proposal.

Tell them what actions you’re proposing & let them know you thought things over before deciding what to do.

Describe how your strategy fits in with other plans and strategies.

Explain how your strategy takes advantage of existing assets/resources.

Tell them how and when you’ll know whether this is successful.

Show your passion – that you are excited about the project.

Invite them to join you in the project—get them involved with things they can do to help the project.

Quote from Danis Kreimeier: “Once you get them involved, they can’t say no.  It’s like stepping on a puppy or something.”

There’s no such thing as a technology project.  Banish the phrase “technology project” from your vocabulary.  Use the word “business project” instead.  Business projects have technology components.

Challenging and changing times like this mean we have to approach business in a very different sort of way.  If we keep going the same way, we’re going to keep getting the same outcomes we’ve gotten all along.  Look for efficiency opportunities within existing projects and tasks.  Selling tech projects is really about marketing.  What are the buttons of the decision-makers that you can push?  What are the local business and community goals you are trying to reach?  Be careful of your perspective

They also opened it up for audience discussion, and asked us to present examples of when we have presented an idea to management and were turned down.  Some additional advice from that discussion: try to understand what it is that management has to lose if you did do the project, and figuring out how to align your goals with their overall goals.  Be proactive in having conversations around potentially touchy issues – “I already thought about potential problems with XYZ, and here’s what we could do if that happened.”  Use data to back up your proposed projects – how many people in your community are using such and such technology.  You have to understand that the line staff are feeling overwhelmed already, so how can we work through management to figure out what we can give up in current work to make space for the new work.  They also recommended charting your projects in four quadrants along the spectrum of high to low investment & high to low payoff.  High investment, low payoff = bad (of course).  But if you can even think of your projects that way and explain the cost-benefit-ratio of what you are putting out there, and tie it to dollars returned, management is likely to listen.

IL2009

IL2009: I Wanna Be 2.0 Too: 10 LOLcat Laws of Web Services for Smaller, Underfunded Libraries

This was my first session this year at Internet Librarian, focusing on some of the free/cheap online or otherwise digital services that any library can provide.

You can view my PowerPoint on Slideshare (and below).

IL2009

IL2009: Fast-Tracking Usability Testing & User-Centered Design

Speakers: Angela Ballard, Cory Stier, and Robert Bastell

Angela Ballard started her talk by discussing a redesign of their website for the NCSU Libraries.  They wanted to make a good Friends/Giving site with online giving that was secure and standards-compliant and a design that was different from the rest of the website.  Most of the content owners were not convinced that they needed to revise their content — they felt that they only needed a design facelift.  Redesigns start with content strategies; the design comes second.  The purpose of their user studies was to highlight problems with the existing site and create a common language with the content owners to revise the site.  The web team knew there were problems with the content and needed to get user input on grouping and labeling.  There was a facilitator who did the usability testing, and an observer from the Friends of the Library sat in on each session.  There was also someone who was remotely managing the recordings.  They gave people sample tasks to complete, like wanting to buy a memorial brick in the honor of someone.  They had people start at the Support the Library webpage when testing them (Note from Sarah: I think this was because they were really testing this sub-site — but I would wager that few people would think to go to Support the Library to create a memorial brick.)  Angie then showed a video of a user, with the matching screencast, trying to complete the name-a-brick task…completely unsuccessfully, and clicking the mouse like a cicada on crack.  Users aren’t using the pages the way that the Friends thought they would.  Their site was rather text-heavy, participants didn’t make connections between content areas that they thought was evident, and the Friends were relying on the forms to convey a lot of information (improperly).  The users didn’t use search – they would use navigation instead, trolling through link after link after link.  With that type of user, you would have to provide really intuitive navigation as that is the only thing the users are relying on.  They also created a card-sorting testing activity, having users organize cards with navigation terms, but also asking them to duplicate cards when necessary, rename cards, and create their own cards with new labels.  As Angie said, if people duplicate a card across several categories, it might be important to put that item in your main navigation.  Something they found across the various users was people dividing up the giving activities into whether it was a one-time or onging gift, or even the monetary level of the gift.  The web developers came up with various types of sites — one with the organization & content that the Friends wanted, and some others that the web developers drew up.  Some of the user responses: Don’t make me scroll, keep navigation lists short, don’t have big blocks of text, etc.  Users wanted them to use images of students in library spaces to inspire giving.  In the end they went with an approach similar to the UCLA Giving pages.  Much of the navigation they created came directly from the card-sorting activities. They used Morae to record video of the usability participants.

Cory & Robert then talked about their work with the Red Deer Public Library.  Their old website was being run by one person, coding everything by hand and putting it up on the website.  They decided that they needed to expand their website development and looked at stand-along WYSIWYG software, like Dreamweaver and other Macromedia products.  There was the problem of the cost of licensing all of this software for so many different content providers in their library, plus the software was only available on a few select backroom staff computers which limited access and participation.  In 2007 they looked at the various content management systems and decided on Drupal.  Using Drupal allowed them to get content up on their website a lot quicker than in the past, plus everyone had a bit of ownership of the content on the website.  There was discussion about who was going to be involved among the staff in creating content.  Site Admins had administrative control to create user accounts, be in charge of templates, administer top level navigation, and decide on new functionality of the site (new Drupal modules)?  And then the rest of the staff were editors or content managers.  Editors were largely heads of departments — editors for the children’s pages, adult reading pages, etc.  The majority of the staff were creating site content directly.  The staff were trained on writing for the web, marketing standards, and other procedures.  One of the important pieces to consider is the decision on what types of content go where.  Staff may need a little help with audio and video, but if you have standards that makes it easier.  You need to decide how the site will be structured and how many levels are okay to have on each area of the site.  You also need to appoint someone to be responsible for what shows up on the main page (Sarah’s Comment: Make sure this person has all of the following: marketing, web services, and public service experience and exposure).  Some staff need help with formatting too.  They might be used to working with a word processor, but may not understand how that doesn’t translate well to the web.  They might not understand how fonts don’t appear the same on all computers, bolding may look pixelated, etc.  You also need standards for the grammar, spelling, tone and more (writing for the web!).  Standards for graphics and multimedia are essential — are you hosting these files locally or posting them elsewhere and linking to them from the site?  In their WYSIWYG editor, users can upload images but within the editor they can reduce the size.  Instead they are recommending that staff edit/reduce the graphic first in photo editing software and then post it to the website.  Staff also need help with accessibility — adding ALT tags, labels, etc.  Staff need to be told about the legal issues related to using copyrighted material, like taking a book cover from Amazon and re-posting it on the library’s website.  Decisions should also be made about what you’re going to archive from the website and for how long.  They are also training staff regarding search engine optimization.  They are “abolishing content with limited content” — if a webpage has one sentence on it, it gets deleted (as an example).  They are also pushing out the idea of “value over volume” — create a small amount of awesome content instead of a big site filled with useless information.  They also talk to the staff about a difference between content semantics and technical semantics.  Their new website is going to be completely standards compliant.  Hurrah!

IL2009

IL2009: Optimizing Web Presences: SEO & Metrics

Speakers: Marshall Breeding, Andrew White, Joseph Balsamo

Marshall Breeding started the talk with his presentation, titled “SEO: Optimizing Library Web Resources for Enhanced Discovery.”  Some of the digital object management systems do not interface well with search engines.  We need to follow all of the techniques that have been established in the eCommerce world for optimized discovery of and access to our library resources.  “The more that you try to scam the system, the more likely you are to disappear.”  If you break Google’s rules, they will likely erase you and not crawl you again.  Even if you do all the right things, the site won’t harvest all of your pages.  Marshall’s sites are being indexed at a rate of about 90%, though he used to be satisfied with 60-70%.  Marshall’s Library SEO Cookbook ideas!  Use your analytics to establish initial performance benchmarks, develop content, create metadata, publish the content, optimize content delivery, use sitemaps to facilitate search engine indexing, and then finally benchmark and fine tune your content and metadata.  Analytics is understanding the use patterns of your web content.  You also need to understand the benchmarks to document hte impact of your SEO techniques.  You should have specific goals for your websites, not just page views numbers.  Marshall recommends Google Analytics to start with – it’s easy to implement and returns excellent statistics.  Where are people coming from within the various search engines?  What keywords do they type in to get to your website?  As an example of change, Marshall noted that he’s noticing a growing number of users coming through Bing…much more than were coming through MSN’s Search.  The goal is to get more traffic to your website through the search engines, and you can do that by helping them find your content.  What are libraries good at?  Having high quality content.  But we need to provide clean structure and strategic metadata.  You will have a product for a web-based delivery system like ContentDM or other CMSs.  You can have one unique page for every object in the repository.  You can have a permalink.  Minimize the navigational stuff because it confuses the search engines.  You need to have a <title> tag that is unique for every item.  You need to have a description that is about 150 words, and that content is what makes the search results description show up as it does.  You also need to generate a site map.  SiteMapProtocol.org is used by all search engines now, but was originally proposed by Google.  Marshall uses a PERL script to create an automatic site map for his site every day.  If you use Google’s site map tool, you can submit your site maps and it will tell you how they’re doing – how many URLs are indexed out of how many you have, what words get people to the site.  The important thing is to monitor and maintain — keep making incremental changes to make your site more discoverable by search engines.

Andrew and Joseph ‘s presentation was titled “Virtual Tachometer.”  Search metrics are important for collection development, website redesigns, and deciding what new types of virtual services you want to provide.  It can help you justify the decisions for new projects.  They mentioned COUNTER-compliant standards — standards that database vendors are supposed to use when reporting resource use.  They did a comparison between Splunk, Google Analytics, and Woopra.  Google Analytics lets you look at statistics over various time periods of your choice, look at page visits, visitor numbers. Google Analytics also shows you where your visitors are coming from by country, province, city, etc. through recognition of IP addresses.  What types of searches are used when people get to your site — you can see what words people use to describe your services (Sarah’s Comment: Also, you can see what is missing — what do you have that people aren’t searching for, or what words do you use that your users don’t use…it’s important to analyze what _is_ in your statistics, but also what _is not_ there.)  Google Analytics has a more complete mapping functionality, more powerful visualization tools, a better drill-down so you can create customized reports, and advanced network segments.  Woopra gives you percentage of new visitors, times of visits and page views, browser use, etc.  Woopra also shows the breakdown of what countries people are coming from, but not as granular as the map services in Google Analytics.  Woopra does have live stats, something that GA does not have.  Within live stats, you can tag a user based on a particular browser, screen resolution, location, etc.  You can then track that user’s activities over time.  Woopra uses Maps by Google in their live system (that’s odd, no?).  Splunk is a free-form log analysis tool.  Unlike Google Analytics and Woopra where you have to install the piece of code on your web content & those companies do the analysis for you, in Splunk you can take the logs off of your server yourself and do your own log analysis.  There are a bunch of plug-ins that work too so you can look at Apache and other languages/tools’ statistics.  Looking at the top sites that refer users to their site, they could see that Serial Solutions provided a lot of referrals.  Splunk also provides similar bar graphs just like in Woopra and Google Analytics.  It builds the analysis in real time as it processes the log file.  You can set up custom screens, custom reports, and custom search points.  Splunk does seem to be a significant memory & processing hog.

IL2009

IL2009: Library Website Improvement Face-Off

Speakers: David Lee King, Amanda Etches-Johnson, Aaron Schmidt, Jeff Wisniewski

This panel talk was focused on usability and user-centered experiences on library websites.  I liked this presentation as it has some very practical, common-sense takeaways that we can now take back to our libraries and colleagues and say “hey — somebody with authority & expertise said we should do this.”  Maybe that’s the way you can finally get some of this common sense website change done!  Hey…whatever works :)

Amanda Etches-Johnson’s Talk

Amanda started by discussing search boxes.  We’re doing a pretty good job of putting catalog searches on our homepages.  Amanda wants to see more of is to put search boxes on pages other than our homepages.  On Florida State University’s subject guide for English has the search box front & center at the top of the page.  The Articles tab should also be there – you can put search boxes up for databases you already subscribe too.  Why not add a search box for the most relevant database along with the catalog search on other subject-based pages.  Collingswood Public Library used to have a massive search box right in the middle of the page.  The search box also includes a phrase of what is in the search capability – “books, movies, etc.”  Amanda did a great job improving when her presentation exploded and she could not see her slide.  The lack of a QuickTime compressor on the presentation machine caused a problem (good note for future computer configurations).  She also says to be human and be whimsical – think about how we write & present things on our websites.  She gave an example of some language describing a change to the interlibrary loan policy at her library.  She had changed the wording from “the library” to “we.”  She also cut the word number down quite a bit.  Be human when you communicate with users.  The library is not a being who can communicate with your users.  Make yourself more approachable by working through your text on the website to shorten & personalize it.  Dopplr is a website that lets you set up a profile of where you’re going to be traveling and when and connect with close-by friends.  Amanda points out that they put a lot of thought into the experience of using their site.  She also recommends testing the heck out of all of our webpages.  Two tools to use: FiveSecondTest.com (upload screenshots and get designer feedback) and Usability.NYPL.org (a usability tool you can upload to your own servers and test the designs with your users right away).

Aaron Schmidt’s Talk

Aaron says that the first thing you have to do is watch people use your website.  People have tasks they want to accomplish on your website.  You can choose the most important tasks for your website and watch where they do well and where they don’t.  Luckily it’s pretty easy and you can have a quick debriefing and make your changes.  Aaron recommends only testing four people–anything more has diminshing returns.  He recommends hte book Don’t Make Me Think by Steve Krug.  You can present content on your website in different ways to see which one people like better.  Present two different layouts, two different designs, etc. and then see through statistics how people work.  “I don’t care about what people think.  I care about what people do.”  Aaron thinks that focus groups are not helpful – actual task-based user groups have better results.  The second thing is cutting content.  Aaron says that recommending 1/4 of pages on library websites or more would be okay.  Look at analytics, find out what people need to do through user interviews, and cut the rest out.  Then you can concentrate on making the smaller website much more effective.  You should also write for the web, which is very different than writing elsewhere.  The DC Public Library’s “Get a Library Card” page got a lot shorter when Aaron re-wrote it.  It’s an FAQ instead–Who can get a card?  What can I do with my card?  He recommends the book Letting Go of the Words regarding writing well for the web.  People will click all over your site if you give them the confidence to do so.  If you provide adequate wayfinding through sensible links and good breadcrumbing people will find the content they need.  The idea that everything has to be findable within 3 links is a myth.  Do not use the wording “click here.”  He recommends going back right now and getting rid of any of those types of links.  (Sarah’s Comment: Absolutely true.  Those links look not only outdated but dysfunctional.)

David Lee King’s Talk

David promotes Google Analytics – a year and a half of looking through stats at his library’s website.  There are a definite top ten things that their users want to do on the website.  Look at the top ten most popular things and make those ten things much, much better.  “Make them rock!”  Words we find on our websites that suck: account, databases, catalog, materials, Literacy, ESL, Audiences, Research Resources.  Ask customers what words they use and then use those words.  David showed his library’s calendar of events and other examples of database-driven pages.  With some simple CSS work you can create different colors, weights, sizes of the fonts in your database driven pages and make them look much more interesting and easily scannable.

Jeff Wisniewski’s Talk

Jeff started by joking that there’s nothing wrong with our websites; the problem is our users.  Muah ha ha ha.  In talking about our library websites we tend to not take into account our whole information universe and from a user’s perspective we are our databases and we are our eJournals and we are the catalog.  That stuff and the website are not separate entities in the eyes of our users.  We need to focus on the usability of these resources where we are taking people.  Most of us don’t have stuff on our own sites that we want people to linger on; the goal is to get them off of the site to the other resources.  (Sarah’s Comment: I know that is likely true for some types of libraries & some types of websites, but I don’t know if that’s totally true.  If we’re trying to get people to participate on our sites, they want to read through recommended reading, they want to look at the library’s events pages, etc…I think that people will be spending time on our sites as well as these external resources…we are more decentralized & outsourced with our content, which is great, but at least for public libraries we do have info on our websites that is not portal-type in nature).  Easy solution — go out and get a new OPAC.  For so many users the library is the OPAC.  If you are dumping people in a catalog that does not work well and looks old and unusable, that is not good usability practice.  Jeff did a small survey with seven library websites (public, academic, & special).  Some libraries are posting multiple search boxes on their homepages, which is confusing.  One library website had seven search boxes on the homepage — argh!  We need to work toward less search boxes and even a single search box using federated search.  (Sarah’s Comment: I’m sure that’s true for academic libraries, but I don’t think public library users want to search the catalog at the same time as all of our newspaper/magazine databases.  Most people want a book, a movie, music, or articles…rarely do they want a full search of all of them.  I guess it points out the real difference in public & academic libraries’ priorities).  If you are creating advertisements on your websites, especially graphics that look like banner ads, then users are unlikely to pay much attention to them as they have learned on the web to tune them out.

The Results of the Talks

The winner was Amanda Etches-Johnson’s concept to “Be Human & Be Whimsical.”  Being human is always a good idea, right? :)   After some complicated voting with people holding up their cellphone screens to vote, there was some confusion about whether we were voting for a single idea, a group of ideas, or a presenter overall.

Fairy Godmother Wishes

Each speaker was also asked to presented one “Fairy Godmother of Library Websites” wish that would make library websites fabulous, what they would use as their single wish if they could wave a magic wand.

Amanda: She wants to make the “long wow” happen in libraries – what we need is to get customer loyalty from library websites.  We want to wow them enough that they will keep coming back.

Jeff: He wants to have about half of the words on everybody’s library website magically disappear and only leave the ones that are necessary and make sense.

Aaron: He wants to provide a unified experience across all the different products — our websites, catalogs, & database products.

David: He wants all of our administrators to magically become geeked-out people who understand what we’re trying to do with our digital presences and support new projects.

The Results of the Wishes

Aaron won with his “unified experience” idea.  Here here!

IL2009

IL2009: Experience Design Makeover

Speaker: David Lee King

The good experience designer plans and builds deliberate experiences into the website, not just hoping for the best.  No one wants to interact with “a website.”  People want to interact with each other.

The Topeka and Shanee County Public Library had a library website since 2004.  Stephen Abram spoke to the staff at a staff day, and they decided as a result to experiment with a blog.  They had a MySpace page but didn’t know what to do with it.  When David arrived, he did an inventory of the web presence.  They did not have a content management system – no real back-end governing the website.  It was a .ASP program that did their events, bookmobile schedule, and more.  David personally hates ASP.  They got a blog, but it was 2 or 3 clicks in.  The IM Ask a Librarian Meebo widget was added after David arrived.  As David puts it, they were tacking things on to an already bad website.  A lot of the space in the middle of the page was dedicated to advertising – they were using valuable real estate for that.  The catalog was hard to find – 2 or 3 clicks down.  David suggests doing a web search for “public library” and then your state’s name, to see a variety of library websites, which he says are generally not up to snuff (Sarah’s note: Abso-freaking-lutely.)

Their current website has a modern CMS.  They also offer comments on nearly every page on their website.  They offer lots of RSS feeds.  Staff writes content for news blogs, subject guides, and genre-specific recommended materials blogs.  That content is remixed.  David notes that the web is once again becoming decentralized.  They have a Facebook page for the library, one for their art gallery, and one for their teen customers.  They still have a MySpace account (David recommends killing all of the spam-friends like authors & other “questionable” friends).  David connected MySpace to their Twitter feed and they are now starting to get some converation on the MySpace page.  They are having conversations on the website proper in the comments section.  They are having conversations in Facebook–people fanning the page, likiing status updates, & commenting on the wall.  Their Flickr account is quite popular, especially the art gallery photographs.  They also have conversations going on in Twitter as well, and YouTube.  Most of the media organizations in town have subscribed to their Twitter account, and are using that instead as a press release source.

In building their new site, David asked the staff what types of content they wanted on the site . They also asked customers.  David also had items he wanted on the new site: basic 2.0 tools & types of content.  Part of our job is to know what’s new and cool out there, and match that up to what is relevant to our communities.  They switched from Meebo to Library H3lp, which David says was successful.  They made the front page look a little less “database-y looking.”  They created a style guide.  They wrote a social media commenting policy (what comments they can delete, and why, and who does it, who answers complaints, etc.).

And…they are at the point where they are starting to redesign again!  How do you start your own experience makeover?  David has 5 tips:

1) Write an Experience Brief: a one-page story about the experience you want people to have on your website, then build what you wrote.  David says you should refer to it constantly.  An example: they overlaid their patron database on their county resident database; they found that the largest 3 of their non-users were middle-class folks living outside of the city center.  Now they know that is who they need to focus on with their digital services.  David read us a story as an example, highlighting all of the library services and materials that should be on the website and how it should be easy to find.  The content of the site, the look of the site, and the wording of the site is all aimed at helping connect the customer to the information.  Keep the design simple and non-distracting; it is understated.  The site should be intuitively organized and labeled; you shouldn’t have to think about how to make the website work.

2) Take a Touch Point Journey: for example, try getting a library card.  Looking through David’s library’s web statistics, one of the most popular things is getting a library card.  Right now, they don’t have a “get a library card” link.  Under My Account, they have “get an account” but that wording is not intuitive.  The page they’re taken to next to sign up for a card is a boring page.  As David says, the page should show what are you going to be able to do when you get this page.  The page should be inspiring and motivate people to sign up for cards.

3) Conversation is Experience: Do visitors talk to each other when they come to a physical library?  Yes.  They also talk to the staff.  On our websites, customers still want to hold these conversations.  So, are we providing these conversation spaces.  It could be comments, status updates, etc.  David’s library has the R.E.A.D. Dogs, where kids can read to service dogs.  They posted about one of these programs and many members of the public replied to it.  A Facebook status update (most of which come from their Twitter account automatically) had 17 replies – they asked “More than 3000 visitors wlak through our doors every day.  We’ve seen a 19% increase compared to last.  Are you a library visitor?  If so, what brings you in?”  The library is asking people things, providing conversation spaces, and tempting them with a question…inviting them to participate.  17 replies on a Facebook status update is pretty good!

4) Answer the “Why?” Questions.  Why should I care?  Why should I attend that?  Why should I read that?  In their website’s research section, they have a link to “Databases A-Z.”  The word “databases” tells people nothing.  David makes the same point with the link title “Ask a Librarian.”

5) Focus on the Customer.  David uses the example of the email reference service saying they’ll get back to customers within 2 days.  That is staff-centric, not customer-centric.  We would never ask users to wait in-person for 2 days for an answer.  Why do we do that online?  Why not have people working at the reference desk keep email open and answer those questions right away too?

Finally, alwyas say yes.  Always enable instead of trying to control or direct.  Let your customers interact with you, and with each other.  David talked about the library’s Meebo widget project launch.  He came up with a plan, had a process for some of the reference librarians to work on the virtual desk.  Some of the reference librarians came and asked David to move from Trillian to Meebo instead.  David said “yes” and then they got that up and running super fast.  David noted that Meebo had some limits.  Meebo doesn’t let you pass questions around between staff, and has the problem of closing down if the patron moved off of the webpage.  Library H3lp now allows passing a customer to another staff member and since it opens in another window it doesn’t have the accidental closure problem. They still have presences in all of the major IM services.  But they found that it motivated them to improve their email reference service too.  So now they have a simple email address that the reference staff check, instead of having a form that goes to a manager who then distributed the questions out to different staff.

Our patrons are going online.  It’s convenient, but it’s not always easy.  Our goal is to improve their experiences and their bottom line.  David’s book, “Designing the Digital Experience,” is a great read that I recommend wholeheartedly.  In writing my own website project plan, and sub-plans, we used David’s book to help us remember what we should be focusing on (the customer!) instead of just on our technical processes and difficulties.

Questions & Answers:

Someone asked about accessibility.  David does look at issues of accessibility in his design work, absolutely.

Another question was about who works on the digital branch.  The writing of content & interactions with the customers on the digital branch are distributed and decentralized throughout the staff.  So, for Joe Reference Librarian, part of his job is to work on the digital branch.  His Director supports that approach, which is very helpful.  The example he gave was that you never let a public service librarian say “sure, I’ll do collections but I won’t work on the desk.”  Same goes for digital branch work – it’s not acceptable to say no.

Another question was about if the added staff.  They did not add staff to enhance their digital branch.  They dropped some of the less important services and inefficient processes to find time to do this work.

How did staff training work?  David did initial training for staff – writing for the web.  Their webmaster did training on how to post to the CMS.

What do you do when the staff say that users want one thing, but the users actually say they want something else.  David says “This website is not for the staff.  That type of content and organization is for the staff intranet.”

Someone asked about how new ideas for content or features get decided (web governance).  A lot of that is what David does for his job.  The mangers meet weekly, and some of those discussions happen there.  David encourages staff to come to him to chat if they have ideas.  Sometimes though staff have really bad ideas.  Other staff have great ideas, but it might not be the best use of time.  David launches projects as a pilot and then re-evaluates them after a test period.

How do they deal with spam?  They do allow unmoderated comments, and installed a “dirty word” blacklist.  That did create some problems, as they had to delete some of those entries to allow for books with “bitch” in the title, as an example.  Whenever anyone leaves a comment, the author of the original post sees an email with an alert to the new comment.  They do get negative comments, but that’s OK.  They respond to those customers to try to help them (example: their new policy reinstating late fines).

IL2009