#15: Library 2.0

The various perspectives on Library 2.0 were very interesting. As I was reading about this topic, I couldn't help but try to put this within the context of what these changes mean for those of us who work in technical services operations. Questions I wrote down to ponder at a later date included the following:

• How will the changes on the public side continue to directly impact the way technical services operations perform their work in the future?
• How can we reinvent the services we provide to meet our stakeholders/partners in their space as opposed to ours?
• How can we make our services more user-centric and inviting?
• How can we evoke Web 2.0 principles to develop newer services that are more simplistic, customer-friendly, and more self-service?
• How can we improve the way we work with our stakeholders so that they are truly participants, co-creators, builders, and consultants?

I particularly enjoyed reading Michael Stephens' thoughts on how to be a "Librarian 2.0." How do we not only embrace constant change, but also make " ... good, yet fast decisions"? How do we find the time in the workday to watch trends, play and learn about new technologies, etc.?

Two interesting quotes from the Wikipedia entry on Library 2.0 were particularly interesting

"Beta is forever."

"Rigidity breeds
failure."

I see that more pondering is in order ...