Further Resources

The Technology Planning Process

Quick guides to technology planning

If you don’t have time to read a lot and you want to jump right into the process, look at these four documents:

Technology solutions brainstorming for your library

Several state library organizations have created technology standards for libraries. In other words, what sorts of skills, tools, infrastructure and procedures will you find in an ideal library? What do the backup procedures look like? What sort of Web presence is there? What computing services are available to the public (e.g. printing, hands-on assistance from staff, etc.)? How many public computers will you see there? If your library is small, it’ll be difficult to implement all of these suggestions in a single planning cycle, but this standards document from the South Carolina State Library and these five short checklists from the Illinois State Library will help you brainstorm and set goals for yourself.

In-depth information on tech planning

WebJunction has lots and lots and lots of information on tech planning. The most thorough roadmap to technology planning in libraries can be found in Diane Mayo’s book, Technology for Results: Developing Service-Based Plans. An excerpt from the book can be found at WebJunction. Because it’s so thorough, it’s also time-consuming, and may not be appropriate for smaller libraries.

Free tech planning software

TechAtlas has a series of questions and surveys to help you create a technology plan. After you’ve registered for an account and logged on, click on the Surveys tab. Once you’ve taken the assessments, TechAtlas will give you recommendations on how to improve your digital infrastructure. This guided approach is a great way to take the uncertainty and guesswork out of tech planning. The Illinois State Library has a similar online questionnaire. As with TechAtlas, you have to register and log on before you can use the assessment tool.

Key Decision Makers

Strategic and Technology Plans

Building a Technology Team

  • For an in-depth discussion of managing your tech team, check out this workbook from NPower. In particular, this article talks about some of the obstacles you might encounter in building your tech team. It also discusses the value of having a technology vision statement and a “Commitment to Success” letter, two documents that can help direct the work that your team is doing.
  • This article from WebJunction gives you some advice about the mix of folks you’ll want for your technology team. You don’t have to fill every role listed in this article, but it’ll give you some ideas about the types of people you should look for.
  • Finally, this success story from the Perry Carnegie Library in Perry, Oklahoma, demonstrates the value of having an engaged, active tech team.

The Costs and Benefits of Technology

The overall accounting and fiscal management process is way beyond the scope of this site, but here are a few resources related to good accounting (i.e., measuring the costs) to get you started:

  • Since the money management cycle usually begins with the creation of a budget, we’ve pulled together some resources on budgeting in general and technology budgeting in particular in our Writing a Technology Budget tool.
  • There’s no getting around the fact that accounting and budgeting and financial management are painful subjects to learn about. But if you’re in any sort of management position, you’ll have to know at least a few concepts. The SEC has a useful discussion of the basics, though this article is geared towards investors and businesspeople. The Accounting Game is a lively, book-length overview of the same subject.
  • After you’ve mastered some of the universal principles, you might need some grounding in government accounting, which is significantly different from corporate accounting. You’ll find plenty of books and web sites devoted to this topic. The official organization for state and local government accounting standards is the GASB. This overview of accounting in schools might also have some useful information. Finally, the State Library of Michigan has posted an extensive guide to financial management in libraries, though due to some site design issues, a Google search is the best way to navigate the whole document.

Total Costs of Ownership (TCO)

Here are two possible learning scenarios to help you get up to speed on TCO.

  • With everything else you have going on, you probably don’t need to understand the whole TCO methodology.
There are quick descriptions of TCO at TechSoup and LinuxPlanet that are really enough to get you started. The TCO in the Classroom site has another great introduction, though this one is a bit longer. Our TCO/TVO questionnaire will also help you understand this concept.
  • If you do want to understand TCO in more detail, there are a lot of great resources to explore. Start off by reading a few pages on one of the sites mentioned here. It’s dry, difficult reading, so reviewing the information in small chunks is the most effective approach.
  • The TCO checklist was written for school administrators, but a lot of the same considerations apply to libraries.
  • This article has a formula for deciding how much IT staff an organization needs (scroll down to the second half of this page).
  • How does TCO relate to staff development? This article has some answers.
  • A real-world example of TCO with relevance to libraries is the TCO spreadsheet from ALA. It is designed to help you figure out if it makes financial sense for your library to filter its computers. Even if you’re not in the midst of that difficult decision, this is a useful tool, because it translates an abstract methodology into real budget line items.
  • Finally, this look at the TCO of open-source software poses some good questions that apply to just about any technology purchase.

Good Evaluations

There are several evaluation frameworks to help you figure out which measurements best suit your situation. Outcomes-based evaluation, return on investment, and cost-benefit analysis are three of the better-known methodologies. They all take some time to learn and implement, but it’s worth the extra effort if you’re working on a complex, expensive, high-profile project.