On getting staff members to buy into a new technology
So you may be all gung-ho about a new technology you've read about and really want to implement in your library. You're sure it will benefit your patrons a great deal. However, it is likely that it's your staff who will be doing the heavy lifting of implementing the technology, marketing it and making it successful. And if they aren't as committed to this technology as you are, they likely will not be as committed to its successful implementation. The key to the success of any new technology is an enthusiastic and committed staff. As an administrator, it falls on your shoulders to build up that enthusiasm. Here are some tips that will help to ensure staff buy-in:
Do not decide things unilaterally
I've heard horror stories about library directors who have unilaterally decided that they want to implement some hot new technology in the library. I was recently on an e-mail list where a school teacher was complaining about how the administration had decided that they wanted teachers to do podcasting for students, and that they just sent this directive down to the staff who would have to implement it. The teacher not only didn't know how to implement podcasting, but he didn't take the technology seriously and hoped for it to fail. You don't want this to be seen as "my supervisor's pet project."
Involve staff in planning
The best way to get staff committed to a new technology is to involve them in every aspect of planning. A good way to do this is to form some sort of a committee to discuss new technologies. Michael Casey of Library Crunch described the Emerging Technology Committee at his library:
All of the members of my team are either young in age or new to the field of library science, and all bring with them some expertise or strong interest in an area of technology that I am lacking.
Where I disagree with Michael is the involvement of only tech savvy staff members on this committee. I think it's of the utmost importance to also include members who are representative of the entire staff (and not just those who are tech savvy or those who hold an MLS). Any discussion of technology will benefit from the involvement of people who are uncomfortable with technology and people willing to play the devil's advocate.
Encourage staff members to voice their concerns about the new idea. Sometimes staff members may be reluctant to adopt new technologies because they assume they're just the "hot new thing" that won't last. Perhaps they're afraid of the technology because they fear it will be difficult for them to learn. If you want to engage your staff in the process, you will need to address these concerns. To address them, you will need to create an environment where staff members feel comfortable sharing their concerns. Otherwise, they will continue to hold these negative beliefs about the technology.
Involve IT in planning
How often do librarians go to IT staff with a fully-formed great new idea only to be shot down? IT staff have their own priorities (security, control, etc.) which may sometimes run counter to the priorities of the public services staff. Including IT staff in early discussions about library technologies will allow them to voice their concerns and for both parties to find a way to make things work. The relationship between IT and the library should be collaborative, not adversarial.
Encourage staff to "kick the tires"
By actually playing with a new technology, staff member will likely think of a lot of issues that need to be resolved before implementing it in the library. At our library, we were very excited about a new technology until we tried it out and realized that it would not work well with our distance learners on military bases whose computers are behind serious firewalls. Encourage all staff members to play with the technology; it's likely that they will discover something you'd never thought of.
Offer training
Once you have decided that your library is going to implement a specific technology, you will need to start teaching your staff how to use it. Just because you think something is intuitive and easy to use, doesn't mean it is easy for everyone to use. If staff members are not comfortable using the technology, they will make it clear either by not using it or not using it enthusiastically.
Don't rush it
It may take time and persistence to get staff members on board with your ideas. Patience is probably the most important virtue for an administrator and probably the most difficult part of implementing a technology you're really excited about. Just remember, if it's a good idea for the long-term future of your library, it'll keep.

Excellent post, Meredith.
An intriguing companion piece might be targeted towards library technologists (whether librarian or IT staff in a library), and focused on getting encouragement or buy-in from folks higher up in the chain of command, e.g., how to sell non-techie librarians and administrators on Fedora vs. DSpace, or on Python vs. Perl, and so forth.
Some of the pointers in this piece can translate into the other piece, I think, but other strategies will probably be necessary as well.
Thanks again. :)
-Mike
Meredith,
Thanks for the reminder about inclusion of staff who are *not* comfortable with technology (or change). Those are the hardest people to get on board, and involving them right from the start certainly helps to get them 'inside the tent'.
Anne Beaumont
Senior Research & Development Coordinator,
The Office of eStrategy & Innovation
State Library of Victoria
328 Swanston St, Melbourne 3000
Voice: +61 3 8664 7100 Mobile: 0419 109 285
Mailto: ABeaumont@slv.vic.gov.au
I completely agree with your comment about collaborating more with our IT departments!
I work in a large academic library. One of the things I wonder about in larger academic libraries is why we don't have our emerging technologies/R&D units staffed with more techies. It is good to have that interaction between librarians and techies. We do not have very many folks in our organization that speak both languages, so we should encourage more staff to develop those "translator" skills. Additionally, in projects that I have been involved with that have involved both IT folks and library folks some really cool, innovative solutions have been found for our library.
Thanks to all of you for creating this blog!
twila
Thank you so much for this post Meredith. I will be using your handy list of reminders as my library embarks upon some new technology projects. A lot of this reads as common sense, but so many of us (yes, I do too sometimes) forget certain parts of this in excitement or a rush to get things out. It's a great reminder to take things slow and involve everyone.
I have a question that is related to your topic.
I am doing a presentation in a class I am taking towards my MLS degree. I am looking for current trends or issues that you or any other members of the techessence group think are important in the automation of academic libraries, migration to new systems and planning for the automation process.
Penelope N
Nassau Bahamas