Why? Lucas says this: “the increasing pace of technology change requires us to be more innovative in how we both adopt and maintain technologies,” and then provides some tips on how to do this. The tips are:
- Research technologies not only before you adopt them, but also while you’re using them.
- Don’t get emotionally attached to a particular technology.
- Continuously research competing technologies to the ones you are using now.
- Don’t build yourself into a corner.
I have heard more than one library IT department say things like “we are a Microsoft shop” or “we’ll never go Mac.” Instead of saying these things, why not do this instead: look at the technology landscape, assess your library’s needs, and then base your decisions on goals and potential outcomes? if you did that, it’s quite possible that some of those “Microsoft Shop” types of statements would go away.
For example, in the web world many libraries are traditionally IIS/.asp/MS SQL users. But if you really assess emerging web trends, you might notice that most of the emerging web uses Linux/Apache/MySQL/.php (better known as LAMP) these days. And many of the newer APIs and add-on web 2.0 services gravitate towards LAMP. So – is your web and/or IT department starting to look seriously at migrating from Microsoft to Linux? From IIS to Apache? And if not, why not?
Another thing to think about – how many of your IT departments understand web 2.0 – blogs, RSS, Wikis, and instant messaging, for starters? Not just grasping the general concept, but actually participating in it? Using and testing out these new web-based tools? My guess is not too many. It’s important for IT departments to not only understand how to maintain the back-end of a blog on a web server, but to also really know how they work. And that requires a certain amount of immersion into the technology. It requires them to read and subscribe to blogs; see how trackbacks work; find out how to hack into some APIs to make these fledgling services better. Etc.
Becoming a technology agnostic will steer us out of that corner and back onto the innovation track.