Monday 5th October 2020
Hello I’m Emma, the e-resource manager at OpenAthens. I’m also a qualified librarian and worked in UK higher education libraries for over 20 years. Working with a range of IT colleagues over the years, I found it can be tricky if you’re not accustomed to talking ‘tech’ to understand each other’s perspectives. It can get in the way of working towards goals you might have for your library service.
In celebration of Libraries Week, here are some hints and tips to help you get those conversations going.
Talk to your users [virtually] about your project. Establish their needs and test out your hypothesis. Our simple guide will help you get started on Guerrilla research with your users. It’s easier to ‘sell’ a new project if you can show what the end goal is for your library users.
Who are the key stakeholders? If your IT team knows your goals and what your plans are well ahead of time it’s more likely that things will go smoothly. Equally, you can often help out your IT colleagues with queries about library services and systems.
This may be the same as the library, or it may not. But you need to get in with your new project before priorities and budgets are set for the year. If it’s hard for you to tell the amount of technical input needed this is especially true.
Every field has them. They can be a barrier and a reason for misunderstandings. Don’t be afraid to ask for clarification. Your IT colleagues may also need help with library acronyms and jargon. Better yet try and avoid both!
Try and breakdown technical concepts before you talk to your IT team, so you feel confident in what you’re talking about or asking for. For example, we recommend librarians read the Access to Online Resources – A Guide for the Modern Librarian.
Show your IT team examples of what you’re hoping to achieve. Not sure if someone else has done what you’re working on? Try asking your community by posting on relevant mailing lists, list-servs, or social media threads.
This can be a great way to ‘sell’ your project to your IT team. It could mean that you won’t need to ask for so much of their time in the future. Will your new project result in a more reliable service where less support needed? For example, your staff or students could be more self-sufficient.
Both can be super helpful in the early days of any IT project. Technical and legal requirements can cause issues further into your project if they’re not dealt with early on.
If you’re thinking of introducing a new resource or system think about including your IT team. This is especially true if you’ve got a requirement for them to be involved in set-up. It can save you having to relay complex technical information between the vendor and your IT team. Ultimately it will save you heaps of time in the long run.
Huge thanks to NISO and our technical support team for inspiring this blog.
Share your top tips with us for library IT projects #librariesweek.
Share this article