Planning and assessment are both crucial elements of a public library that functions efficiently and flexibly. So why are they often treated as separate processes? This concise book combines planning and evaluation in a holistic approach, helping public library managers and staff put library resources to work for the community. Based on a series of successful workshops, the workflow presented by the authors is made up of manageable steps for integrating outcome-based planning and evaluation (OBPE) into the routine functions of the public library. Offering step by step guidance that’s transparent and easy to follow, this book introduces the concept of OBPE and explains how it can be a streamlined, effective method of getting library users’ feedback; defines “outcomes” and shows why public libraries should use them to plan and evaluate services; shares methodologies for assessing community needs and interests, including key informant interviews, surveys, focus groups, and environmental scans; demonstrates how to use community assessment data to create outcome statements that not only guide the creation of new library services, but also provide targets for measuring the effectiveness of those services; offers techniques for designing services that directly serve the community while also achieving the outcomes the library has targeted; and provides tips for sharing the results with stakeholders and maximizing successful outcome-based programs to leverage the library’s role in the community.Featuring plentiful examples of how to proceed through each phase of the OBPE model, this book boils down planning and evaluation into an approachable, easy to understand process for public librarians, library managers, and grant writers.
Really short book that essentially outlines what the authors covered in a series of workshops they held a few years ago. Very cut and dry and "step-by-step". I feel after reading this book that I could easily train other librarians in this process. It is all "common sense" stuff, but I think it's nice that the authors break it down, identify the "why" for each step and how to go about it. It will add more time to the programming process and the authors readily admit that, but it does create a good documentation trail for reporting to the public and even one's boss for annual reviews.
Initially, this came across as a little too theoretical and dry, but eventually the authors threw in useful suggestions and examples. A decent summary of the most recent trend in measurement.