On Using New Technology
We spent the past few months playing with and comparing various social software technologies, but if or when the time comes to implement social software in the places we work, we are sure to come up against resistance. (Unless you work in an office culture where technology is embraced, and even that has its downfalls.) Across the board, I think the three issues we would mostly likely face are time, training, and utility.
This is a phrase we have all used at one point or another in our workplace and undoubtedly will be one we may hear. If that is a case, we may want to look at technologies that require zero or very little set up and/or maintenance. RSS feeds are a one time only setup and social bookmarking is another tool that can be incorporated into someone’s daily routine, especially if they have installed the browser buttons like in del.icio.us.
There are many approaches we can take to address these objections. One approach is to target who will be using a specific technology. Web 2.0 tools strength lies in their often customizable interface as in mashups. Another approach is to deemphasize the technology while emphasizing the benefits of the tools such as how they can streamline workflow or improve day-to-day tasks. Lastly, training opportunities are a must – and these do not necessarily have to use Web 2.0 tools. If someone knows there are resources available to them to ease this techno-transition, they may be more likely to play with the tools and see how it benefits them or institutional goals for themselves.
Utility: “Why do we need these tools, anyway?”
The last possible objection I want to discuss is one that needs to be answered at every step of the technology implementation process. From deciding on the tool to presenting a prototype to colleagues to assessing effectiveness. Goals should be outlined, so they can be periodically checked to see if these new, “fancy” tools are in fact meeting the goals that had been originally outlined. I also want to say that goals do not have to be large or complex, they can be as simple as:
1) We want to have a place where all departmental documents that relate to processing can be housed and edited (wiki or blogs).
2) We want to be able to share news with our patrons. (RSS feeds or blogs)
3) We want to be able to experiment with virtual reference. (screencasts, podcasts, IM, or MUVEs)
What would you imagine being an objection you might hear in implementing social software and how would you recommend meeting that challenge or if you have implemented social software in a library, what objections have you heard and how have you discussed those issue?
