Friday, August 11, 2006

NEKLS Tech Day Redux

Once again, NEKLS Tech Day was a great success thanks to Brenda, Liz, and the whole NEKLS crew.

Keynote: Michael Stephens
Library 2.0: People, Planning & Participation
Moving to a Library 2.0 World

Great points from Michael’s presentation:
Involve your staff in enhancing tech and engaging patrons--social tech isn't just for the techies

Two of the most important Web 2.0 elements:
**Harnessing collective intelligence ** Librarians are smart, patrons are smart: pull all that together
**Rich user experiences** It’s about bringing all that collective intelligence together and creating content together—remember that Web 2.0 is participatory, and it’s fun…you create fun worlds to play and customize and connect

Library 2.0 isn’t just about tech
It’s also about policies and ensuring that library policies don’t create barriers to access, tech, and interaction.
It’s also about places and ensuring that they are places of pleasure not zones of mediocrity.

Make it ok to fail (think like a Gamer—it’s a trial and error world…accept risks; learn more…this is one of the hardest things for me to do…I want to tell others it’s ok to fail, but I can feel my back clinching up just typing this.)

Engage in radical trust.

My post-tech day to-do list
Usually, when I’m sitting in presentations, all the ideas or concepts—particularly those I’ve heard about in the past---just remind me of everything I want to get done…and projects that have moved to the back burner that I need to stir up a bit. Here’s my list that bubbled up as I was listening to Michael and talking to colleagues at tech day:

a. Tag my photos up on flickr as “librarian”

b. We have a myspace page, but we need to start using it better. Who in YA could help with this?

c. Read: The Wisdom of Crowds: the group is smarter than any one

d. Buy-in is important, and one of the best ways to get buy-in is to get your administrators involved with training, with creating a culture of innovation that recognizes failure is just part of the learning process. How do we do this?

e. Talk to Tom Peters about collaborating on more promo and how-to aids for OPAL.

f. Write up a plan with Whitney and Tricia on how to bring JoCoLibrary to the next generation and give staff who want to engage options for engaging online.

g. Put JoCoLibrary up on 43 places (are we there already?) This might be a good way to encourage branch staff to jump in and play.

h. Institute ROI studies before and after a pilot (product costs, staff costs, training costs, implementation, maintenance, etc.)

i. Add to the potential leadership projects: Have a happy, friendly, experience-based sign task force—all signs—the Web page errors, the “blocked” links on filter page—look at every instance in which we’re communicating with patrons, and ensure our messages are friendly, open, and encourage access.

j. Find out what happened to our SMS/text messaging project. We were working with a student from MIT who had developed a nifty program. Where’s that at?

k. Send a note to staff who attended tech day and ask how the Web Content Team can help to implement some of the omg-we-totally-have-to-do-that ideas that bubbled up for them at tech day.

For more on NEKLS Tech Day check out..
Post from David King (who also sat on the Tech Day Panel)
NEKLS Tech Weblog post from Liz


Blogger Degolar said...

I haven't had a chance to really reflect with my manager on her experience there, but one of the things she mentioned in a quick conversation is starting a YA myspace for our branch. I don't have any experience with myspace, but I like the idea.

8:06 PM  
Blogger Kelly Sime said...

Me, me, me! I'm the one who should help you with the myspace thing.

Wait, your first post said I should say "no". Oh, well, okay. "No".

I'll work on the runescape tournament instead. Tee hee.

10:46 PM  

Post a Comment

<< Home