Technology planning

One of the readings from this week's unit that I could most identify with was Stephens’ Technoplans vs. technolust, as I see quite a few people around me enamored with technolust, although I don’t think this is a bad thing so long as it helps the library users, the users being the overriding concern of any technology plan. I also liked Stephens’ point that technology plans are often implemented without full regard as to how the affect the front lines. As a middle manager this is part of my job, to be the buffer between the technology and other implementations from the top and the front-line staff. Procedures and workflows help considerably, but it’s also important to make sure that you’re not overloading your staff.


I really enjoyed Schuyler’s article “Life is what happens to you when you’re making other plans.” I see this all the time with our library technology group. They are constantly dealing with small but time consuming issues that are not written into the technology plans, such as a cyberattack on self check hard drives, viruses in the digital signage software, new printers needing to be configured, etc. I’ve also noticed how our primary technology services coordinator quickly moved up the command chain in the last 3 years, and deservedly so given the responsibilities of his job and the greater part that technology plays not only in the work of staff but in the day-to-day needs of our users.