Introduction (Agenda Items I-V)

Buie asks participants to note what they hope to get out of this workshop.
Some answers include: brainstorming; learn how Web site is developed; learn how usability issues are addressed/solved; learn about ALA structure (in regard to Web site development); learn about how to bring together diverse set of people/divisions for ALA membership via ALA Web site; have this group be able to come to consensus to implement new site; IT needs; information sharing.

Buie says we'll not come out with set of requirements today but will come away with set of goals and objectives that will help to establish requirements.
Buie says we'll start about vision, strategy, goals. This group will not come out with a "document," but instead will come away with action items.

Buie asks for ground rules. Participants determine:

1. No design

2. Process for tabling and moving on

3. Make sure everyone is heard

4. Talk about future

Buie Provides Overview of Usability Assessment

Vision (Agenda Items VI and VII)

*Buie: start with brainstorming: "If you had site you want, what would people say about it?"

*Break up into five small groups, each covering top five descriptions, for discussion, to:

1. crystallize these into goals and objectives (HOW WE CAN MAKE THIS HAPPEN)
Specifics (not how to do it, but what it would do)
2. flesh out abstract terms
3. realistic or idealistic? Buie says in between (don’t list anything you know isn’t possible).

Group Results

Group 1: Morphable/Customizable (presented by Keith M. Fiels)
My ALA (morphable/customizable)
More sophisticated/improved
Availability for nonmembers
More drag and drop
Updates be pushed out (reflected in 'My ALA')
Customized crawlers
Customizable feeds (via RSS or email)
Recommended function (like Amazon, prompting)
Affinity (opps for communication with other members)
Interface (ability to pick your own)
Be able to pick your own language (translation better too)
Own format (larger font size)
Printer friendly version
Wiki-wise web site (more opportunities for you to contribute)
Find out about this (when you renewed, be invited set up My ALA, easy to use tutorial)

Group 2: Participatory/Collaborative (presented by Mary Ellen Davis and John Chrastka)
Functionality for comments on products
Self-forming communities
Social networking (facebook); be able to integrate ‘MY ALA’ into other sites
Wikis, blogs, RSS, podcasts (all tools exist right now)
Be ready with for newly developed tools
Surveys
Cross-structural collaboration

Group 3: Intuitive (presented by Michelle Frisque)
Utilize audience-based navigation
Use language is simple (concise, no jargon)
Represent different types of learning styles (visual, auditory)
Conventional graphic representation , i.e., shopping cart
Develop conventions that apply consistently across all pages (form, graphic, members only, frame)
Have template available for back end
All incons the same
Reduce and define acronyms
Less linear and textual
Info. Should be packaged in many different ways (need built-in duplication/redundancy)
Pages should be current
Links need to go where you think they go
Set up a process to gather data for future Web Development (behavorial); development of site ongoing.

Individuals divide into same five groups to discuss obstacles to ‘Needs’ (brainstorm approaches for obstacles)

Results of Now-Need Group Discussions

Group 1 (presented by Keith M. Fiels)
Talked about issue of “triage”; separate out long, medium, and short terms tasks (three prong approach)
What are things we can do to produce immediate results?
Obstacles: No centralized group to concentrate on improvements (simple TQM model); no way to take usability info. or complaints; and no way to check for duplicate content

The Way Forward (Agenda Item IX)

reorganization of structure (spine)
more bang for buck
reprioritization (stop doing core job for extra thing?)
training department
staff person dedicated to Web site editor position (as opposed to someone doing it with an ‘extra hat’); put this person in neutral category (where does this position fit?)
money (commit money for staff persons or for outsourcing); only going to get good as product as we invest in
testing/trying (Skunkworks group/emerging technologies)
usability testing at conference sites
develop new policy statements, guidelines, and procedures (both high and operational level) to proceed in a new way
organizational commitment to change (change manager and/or group; spirit of willingness to actually implement change)
accountability for change (process for getting buy-in; identify value for groups)
publicize what’s happening—nonelectronic media as well as Web
Resources: 1). for usability engineering of new design; 2). to maintain usability and continuous improvement

Web Site Priorities (Agenda Item X)

Library of Congress Site
Does great job of complicated info. for multiple constituencies
always know you’re on LOC site: site brand and consistent look
good use of graphics
Good delineation of resources for library and nonlibrary needs: families, publishers
Multiple ways of getting to same thing

American Institute for Architects
"great navigation"
good separation of needs/info. of various audiences (not only architects and members)
good graphics
good advocacy piece

American Psychological Association
text-only version (discussion about being good or not)
publications listing
index (on left)
most popular news releases on right (updated every 24 hours)
My APA, which is member customized content
good fly-out menus
BUT TOO MUCH INFORMATION on front page of site

*Third Activity: Break out to vote on Web site priority lists (above); participants use stickers to vote again.

Brief Technological Overview: What do we have? What do we need? (Agenda Item XI)

*Top Three
Networking with Other Librarians
Becoming a Librarian or Library Assistant
Info. for New members

Break out groups consider: What changes do we need for above things to happen

*Group 5 (presented by Cathleen Bourdon)
Buttons revamped; navigation system needs work
All staff access
Institute playtime
Spend money on new tools
Work on building social network

*Group 4 (presented by Mary Ghikas)
Expand tool kit
MySpace Functionality (member profiles)
Architecture needs fundamental change to flatten things out
content: least rich area: information for new members. John been working on this but long way to go; suggest wiki for new members

*Group 3 (presented by Michelle Boule)
Redesign of architecture
Flyouts
Dropdowns
Push content out (subscribe, RSS, be able to see who is online, "buddy list")
Events and calendar system
Chronological list of conferences (of all conferences)
Conferences locations interactive maps
Be able to search conferences by subject topics
Divisions: Do away with acronyms; 90% of content under one button (division)

*Group 2 (presented by Sara McLaughlin)
Networking with other librarians; ways members to customize their profiles (type of librarianship)
Creating communities of practice (users can be approved and can interact within community electronically)
How to Become a Librarian… FAQ, redesign, taking info. already there and “splashing it out here…”

Revamping the joint section (devoting resources to getting it done)
Revamping professional tips and tools (wiki already in place; put in URL)
Money: opportunities ahead: funding available at year end to use for 2010 initiatives (opportunity to roll out reasonably sig. project); funds avail. May 1 if we can articulate project

Internal grant process; certain money available for projects w/ emphasis for collaboration
Opportunity to get something going by May 1

how will position be defined? Place (high level in ITTS), but not primarily a technical position

Fiels: A bit discouraged by process looks like going to take a while.

Resources stepped up to address problems NOW!
Looking for involving additional staff allocation… three months to make that decision. Want someone with reasonably high level within organization (experience with working with members; waiting for signals from Mary, Sherri, and Rob about how to move forward). Access to some additional resources: PRIORITY! (sell it senior management, BARC, board)

Huge jump in user satisfaction (but only half are somewhat satisfied or better)