The document outlines lessons learned from redesigning a public library website. It discusses problems with the old website like it not meeting ADA requirements and having an outdated design. When redesigning, it recommends getting stakeholder buy-in, doing user testing, starting with accessibility, using project management tools, having a phased launch, and continuously getting user feedback. Key lessons include doubling the timeline, prioritizing information architecture and design, celebrating wins, and avoiding being too fancy or re-inventing wheels.
1 of 18
More Related Content
CIL2010: Website Redesign: A Public Library Website Redesign: (aka The Trip to Hades & Back)
1. a public library website redesign Sarah Houghton-Jan Digital Futures Manager, San Jose Public Library Author, LibrarianInBlack.net
3. problems we’re solving 1 website for 2 libraries public library users felt ripped off 7 year-old design, content, and CMS webmaster as gatekeeper = disconnected staff ADA requirements cumbersome in existing environment
4. problems we encountered while solving those unrealistic admin expectations 1 year long RFP & contract process incompetent graphic designers 6 months of lost time due to lost momentum merged web team working on 3 websites
6. redesign planning stakeholders identify org. goals techies, designers, and information architects identify how to meet them identify your givens use planning software (BaseCamp, dotproject) double the estimated timeline
7. staff & customer involvement initial satisfaction surveys for both card-sorting testing for customers early on staff focus groups mock-up task testing for customers transparency to staff and customers
8. usability identify who you are serving focus on the few things you do well tell stories of what your users want look for friction points who is the site for again?
9. accessibility start simple Basic tools: JAWS, WAVE, browser emulators, OS emulators Firefox tools: Firesizer, Firefox Accessibility Extension, HTML Validator, Web Developer Extension, WCAG Contrast Checker
10. communication blogs for staff & customers with email & RSS updates ask for customer & staff input (+ use it) recruit usability testing participants from among “the angry folk”
11. project management set deadlines for everything hold people accountable one person should be in charge of tracking give periodic updates to staff/managers spend the most time on IA and design keep things moving no matter what celebrate small victories
12. launch techniques phased-in launch (notices, pre-testing) beta + feedback = 1.0 + feedback = 1.1 + feedback (and so on) provide brief online & printable orientation if it takes >1 page, start over
13. 5 things to avoid try to be fancy when your brain says “no” allow consultants to push you around have more than one project manager stifle creativity re-invent some wheels
14. 5 things you must do show your ego to the door take risks document everything research everything talk to your users continuously