Peter Graham (Syracuse)
Gerry Munoff (UC-Irvine)
Summary
Prompted to have this discussion because of a failed search for an AUL for Technology and Information Services at Syracuse. The discussion began with the question, "What is the "organizational" place for technology in the library?"
Search processes have surfaced a variety of qualifications and candidate visions regarding where technology should be "placed" within the organization. A number of directors described aligning the organizational structure with candidate interests and strengths.
One new and popular model is having a "Technology Officer" but really an AUL with no reports. This person is most involved in the creative works with less problem-solving and day-to-day management (focused on advanced projects). In this particular example, Library Technical Services Department does all the problem-solving and operational management. Another model is to move to project teams, with a librarian involved in each team.
One of the directors recently had a successful experience with recruiting firm Gossage and Sager. This search surfaced 6-7 good candidates. Important to remember when using a search firm, some of candidates are not on job market. So, they may need to be "enticed" to apply and consider which places an increased level of responsibility on the library for outreach and "selling".
Words of wisdom: Expensive to use firm
Told by firm that if the library is not prepared to pay six figures, don't bother with search
Overall, a variety of trends surfaced in this discussion:
*Libraries are hiring library technology leaders at AUL level with less management responsibility than traditional AUL positions
*Look at what you have and work with it
*Technology leaders do not have to be librarians
*Sharing a position with other campus units has been a successful experience at several institutions
*Libraries are investing in developing current staff with potential and technology visionary interests
*Example titles: Virtual Library Architect, Information Architect, "Library Provacator"
Overview
Several ads have appeared in the past year for ARL positions described as "Associate University Librarian for Information Technology and Technical Services." The searches have had mixed success. They point up the difficulty of dealing with the current stage of technology needed in libraries.
We are well past the point where technology (primarily computing) was deemed to reside in the Systems Department, reporting either to an AUL or to the UL. At most libraries some level of facility with technology is now an expectation for present staff and even more for most new hires. Yet technology changes rapidly -- yesterday's knowledge of OPACs does not necessarily mean one is facile today with wireless or with preservation metadata.
Libraries must manage technology. We aren't yet ready to say that technological sophistication must be inherent in every position (as we assume some level of bibliographic knowledge). Yet technology is affecting every activity of the library.
Possible questions for discussion:
Does it still make sense for technology to be "located" in the organizational structure of the library? If so, where?
Library postings and strategic plans often call for "leadership" in guiding the library toward effective technology use. If technology leadership is located in a staff position, how does the incumbent make things happen? If it is located in a line management position, what kinds of units should report to it?
Technology and technical services have often been linked because of the historical development of the OPAC and because the mindset and skill set were thought to be similar. Is this still true? (Was it always true?)
For most libraries the outsourcing of systems development, as opposed to the building it within the library, has predominated since the 1980s. Under what circumstances should a library "build it here"? How does this affect organizational structure?
What are the successes and failures people have recently in filling senior technology positions?
Technology is changing the demographics of skills, making the people we look for very desirable (hirable) in competitive fields. How do we represent or require technology in our leadership positions in a way that is attractive?