Key Takeaways
Treat knowledge as a workplace practice, not a pile of files
Knowledge lives in action. Organizational knowledge is what employees know and do, including the routines, skills, and shared understandings that shape work. Some of it is explicit, meaning it can be recorded in documents or instructions. Tacit knowledge is the experience and judgment people use but may struggle to explain. A file can preserve information, but it cannot preserve every reason, context, or insight behind the work. Knowledge grows when people interpret information, learn from one another, and apply what they learn.
Start with the purpose. The book’s central proposal is to help staff create, share, organize, and use knowledge in service of a library’s goals. Librarians may expertly organize information for patrons while leaving internal procedures scattered, outdated, or undocumented.
The distinction between storing information and enabling knowledge resembles the difference between a recipe and cooking: instructions help, but judgment develops through practice and feedback. This shifts attention from repository size to whether employees can perform and adapt the work. It also complicates the promise of documentation. Some expertise can be described, but tacit judgment often needs demonstration, conversation, or supervised practice. A useful measure is therefore not how much material a library has captured, but whether colleagues can reliably act on it.
Audit what staff need before buying another platform
Find the gaps first. A knowledge audit examines what information and know-how an organization needs, what it already has, where it travels, and where duplication or bottlenecks occur. The process typically includes planning, gathering evidence, analyzing findings, presenting them, acting on them, and reviewing the results. It helps leaders avoid mistaking a technology purchase for a plan.
The file count tells a story. At the American Legion Library and Museum, staff reviewed about 100,000 shared-drive files. They kept roughly 30 percent as current working material, moved about 40 percent into an organized archive, and removed about 30 percent. The exercise made current documents easier to locate while preserving records with historical value. The lesson is not to save everything, but to decide what deserves a place and why.
An audit is valuable because it treats search failures as symptoms of a workflow, not merely a software defect. This aligns with service design, which begins by observing what people need to accomplish before redesigning the tools around them. It also gives an organization a chance to notice whose knowledge is missing from its records. Audits can become bureaucratic inventories, however. Their findings matter only when someone has authority, time, and resources to change the conditions they expose.
Make sharing safe, useful, and possible across the hierarchy
Culture controls the flow. Employees are less likely to share expertise when they distrust management, fear criticism, compete for recognition, or believe only senior staff have valuable ideas. In a steep hierarchy, people lower on the chart may wait for permission rather than raise problems or offer improvements. Leaders can counter this by sharing knowledge themselves, inviting staff input, recognizing collaboration, and making it safe to question existing routines.
Change the conditions, not just the people. The book recommends an environment that supports trust, empathy, and cooperation, while giving staff some agency in knowledge-sharing activities. It also cautions against treating one culture as universal: employees may differ in what they consider appropriate to share. Staff time, training, and a credible organizational purpose are necessary, not optional extras.
This account connects knowledge sharing to psychological safety, the shared belief that speaking up will not invite humiliation or retaliation. Safety is not the same as avoiding disagreement: a useful workplace needs respectful challenge as well as trust. The book’s emphasis on changing conditions rather than labeling employees as resistant is especially constructive. Yet invitations alone cannot undo incentives that reward individual achievement or punish visible mistakes. Leaders need to align evaluation, workload, and recognition with the collaborative behavior they hope to see.
Let practice communities move expertise between colleagues
Learning happens together. A community of practice is a group of people who share an interest in a part of their work and learn by discussing and improving it. Unlike a project team, it is organized around a shared practice rather than a temporary assignment. Such groups can transmit tacit know-how through questions, examples, feedback, and observation.
The Pittsburgh liaison librarians made it concrete. More than twenty-five liaisons worked across a dispersed library system, but had few reliable ways to compare experiences or reuse one another’s teaching materials. They formed a community with monthly meetings, topic surveys, and short presentations about recent work. A Box repository with tags and metadata made shared resources easier to find. Slack saw little use, a reminder that a tool cannot manufacture a communication habit people do not want.
Communities of practice work because they combine social belonging with practical problem-solving. They can function as informal apprenticeship, particularly for newcomers who need more than a written procedure to understand how experienced colleagues handle ambiguous situations. The Pittsburgh example also shows that adoption is contextual: face-to-face discussion suited this group better than chat. These communities still need care. Without room for dissent or links beyond the group, shared norms can harden into groupthink and circulate familiar answers instead of testing better ones.
Choose tools people can use, then keep their contents current
Fit beats novelty. A wiki, FAQ, shared drive, or cloud repository can support knowledge work, but each has costs: confusing interfaces, weak search, security problems, maintenance demands, and dependence on a vendor or a few technical employees. The right choice depends on the task and the people doing it. City Tech Library’s MediaWiki centralized procedures, yet its markup, security concerns, and upkeep discouraged use. Staff later adopted WordPress more readily because they already knew it.
Curation is part of the system. The University of Arizona Libraries used LibAnswers for a staff FAQ. As it grew beyond 100 entries, review showed that many items had not been viewed; some duplicated public web content. Editors removed or revised material, added access shortcuts, and began monthly checks of links and accuracy. A useful knowledge base is maintained, not merely launched.
Tool selection is a form of organizational design. Familiarity and low friction matter because every extra login, unclear label, or awkward search adds a small cost that can steadily suppress participation. The cases also challenge the assumption that one platform must do everything: several libraries combined systems according to their different strengths. Vendor products can reduce local maintenance, but create risks around price, continuity, and data control. A sound choice weighs the full lifecycle, including who updates content and what happens if the system disappears.
Treat staff departures as a knowledge-risk event, not paperwork
Preserve the work behind the files. Employees leave, change roles, or retire with experience that cannot be recovered from a job description alone. The book recommends collecting knowledge in manageable portions, such as short periodic accounts of how work is done, and arranging transition conversations around recurring duties, priorities, and deadlines. Onboarding, coaching, mentoring, and succession planning help transfer expertise through practice as well as documentation.
One wiki helped, but did not scale automatically. At William Paterson University’s Cheng Library, fourteen employees departed over three years. An assistant to the dean used a password-protected wiki to organize duties by month before leaving. The successor found it invaluable. An attempt to repeat the approach for another position stalled because documentation took time and some staff were unwilling to share their expertise.
A departure is a useful forcing function because it reveals how much of an organization’s continuity rests on one person. The case also exposes a fairness issue: transferring expertise takes labor, and organizations should allocate time for it rather than treating it as a voluntary favor from departing staff. Documentation cannot capture every exception or relationship, so handover should include conversation and opportunities to observe the work. The most resilient plan spreads knowledge before a vacancy appears, reducing both urgency and dependence on a single expert.
Use leadership transitions to clarify work, not multiply confusion
Temporary change still needs structure. At Penn State’s Special Collections Library, two employees jointly led a collection-management team during a six-month gap in supervision. They set shared priorities, held individual check-ins every two weeks, and met monthly with the full team to discuss progress and train staff on archival tools. The arrangement brought technical expertise and institutional memory together while giving the team a voice in hiring its next manager.
But divided authority has a cost. Staff were sometimes unsure which interim leader could make a final decision. Emails multiplied, answers conflicted, and guidance was not consistently shared with everyone. The case suggests that leaders should establish decision rights, communication routes, and a record of key decisions at the start of a transition, even when the arrangement is temporary.
This case illustrates a classic coordination problem: adding capable leaders does not automatically create coherent leadership. Shared management can broaden perspective and distribute workload, but only if roles and escalation paths are explicit. The practice of asking staff what blocks their work also turns supervision into a feedback system rather than a one-way status report. Temporary arrangements deserve less improvisation, not more, because uncertainty already raises the cognitive burden on employees. Clear decision ownership protects both speed and trust.
Build knowledge management as a continuing learning loop
Balance direction with initiative. A workable program combines top-down support, such as priorities and policies, with bottom-up activity, such as peer networks and staff-led problem-solving. The book presents knowledge work as an ongoing cycle: organize and capture useful material, help people share and apply it, then use experience to create better knowledge and discover what is missing. Stories and reflection help employees explain why a process exists, not only what steps to follow.
Assess to improve, not to claim certainty. The authors caution that it is difficult to prove a direct return on investment from a knowledge initiative. Surveys, interviews, usage patterns, and documented outcomes can still show whether access or coordination is improving. A library should revise or remove material that no longer helps. Calling a process “best practice” too soon can signal that learning is over.
The learning-loop perspective fits complex work better than a one-time implementation plan. It treats feedback as part of operations, much as iterative design tests a service, observes how it performs, and adjusts it. This is especially useful when policies and technologies change faster than manuals can be rewritten. Measurement needs restraint, however: page views and edits are activity measures, not proof of better decisions or service. Pairing them with staff accounts and concrete workflow outcomes offers a more credible picture without pretending that every benefit can be reduced to a single metric.
Prepare librarians for AI with data skills and human judgment
Discovery is becoming more automated. The book anticipates search systems that infer relationships among information, rather than relying only on carefully constructed queries. Artificial intelligence and machine learning can help classify large collections, interpret questions written in ordinary language, and automate responses. Enterprise content systems may also apply rules to classify and protect records as they enter a system. These tools still depend on people to define useful rules and understand organizational processes.
New skills bring new risks. The authors expect knowledge workers to need more statistical, analytical, programming, legal, and security expertise. They also warn that automated monitoring of messages and documents could expand surveillance in the name of protecting information. Data science may absorb some traditional knowledge-management tasks, but the human work of interpreting context, supporting collaboration, and deciding what should be shared remains essential.
The forecast captures a lasting tension in automation: machines can make patterns visible at scale, but organizations still choose which patterns count and what actions follow. Those choices encode priorities, omissions, and risks. More technical literacy can help library professionals scrutinize automated classifications rather than simply accept them. The surveillance concern is particularly important because a system designed to protect institutional knowledge can also expose employee behavior. Technical capability therefore needs governance, transparency, and limits, especially when monitoring could affect trust or be mistaken for evidence of wrongdoing.
Analysis
Libraries that Learn is a practical, multi-author guide to a problem hidden in plain sight: institutions that organize knowledge for patrons often neglect the knowledge required to run their own work. Its strongest conceptual move is to shift the goal from capturing an imaginary, complete store of employee expertise to enabling people to create, exchange, and apply knowledge. That shift explains why the cases repeatedly pair technology with training, leadership, workplace culture, and content maintenance.
The case studies make the argument concrete by showing that adoption depends on local conditions. A wiki can preserve one employee’s complex duties yet fail to spread across a department. A community may meet productively in person while ignoring chat. A searchable staff FAQ can help at service desks and still lose value when employees cannot find it or its answers age. These uneven outcomes are more instructive than a polished success story: they show that implementation is not a software choice but a negotiation among usability, workload, authority, and trust. The book’s scope also sets limits. Its cases come from U.S. academic and special libraries, with no public-library case study, and the evidence is mainly practical experience rather than controlled evaluation. Its recommendations for dedicated leadership and broad organizational investment may be difficult for small or underfunded libraries to follow. Claims about future artificial intelligence and data science are useful signals of emerging issues, but remain forecasts, not demonstrated outcomes in the cases.
The enduring contribution is a way to ask better operational questions: What knowledge is needed for this task? Who has it? Who cannot access it? What context is lost when it is recorded? Who maintains the record? These questions connect information systems to organizational learning and continuity. The book is most persuasive when it treats the knowledge environment as something leaders shape through routine decisions, rather than as a repository they can install and declare complete.
Review Summary
There are currently no reviews available for the book Libraries that Learn. The overall rating and number of reviews are listed as null, indicating a lack of reader feedback at this time. Without any reviews to analyze, it's not possible to provide a summary of readers' opinions or experiences with the book. More time may be needed for readers to engage with the work and share their thoughts.
Glossary
Organizational knowledge
What an organization knowsKnowledge embedded in an organization’s people, routines, practices, and norms. It includes individual skills and experience as well as understandings shared by teams. Because much of it is learned through work and interaction, it is not fully represented by documents, databases, or formal procedures.
Tacit knowledge
Hard-to-explain know-howKnowledge grounded in experience, behavior, and judgment that is difficult to express completely in words or documents. An experienced employee may know how to handle a task without being able to list every cue or decision involved. Conversation, observation, mentoring, and shared practice can help transfer it.
Explicit knowledge
Recorded, shareable knowledgeKnowledge expressed in a tangible form, such as a written procedure, diagram, report, or instruction. Explicit knowledge can be stored, searched, and shared more readily than tacit know-how. However, documents may omit the context and judgment needed to apply them correctly.
Knowledge audit
Map needs, resources, and gapsA structured review of the information and knowledge an organization needs, what it currently supplies, and how those resources move through the institution. An audit can reveal missing material, duplication, bottlenecks, and inaccessible expertise. Its findings guide a knowledge plan and should be revisited as needs change.
Community of practice
Peer group learning through workA group of people who share an interest in a topic or area of practice and learn through ongoing interaction. Members exchange experience, solve problems, request advice, and develop approaches together. Unlike a project team, the group forms around shared practice rather than a fixed assignment or formal position.
Social network analysis
Map relationships and knowledge flowsA method for examining connections among people, groups, and information resources. In organizational knowledge work, it can reveal informal networks that are absent from official charts, identify isolated groups, and show where expertise or communication is concentrated. The resulting map can help leaders connect people who need to exchange knowledge.
Sensemaking
Build shared meaning from eventsThe process by which people reflect on experiences, discuss what happened, and develop a collective understanding of events and their significance. In organizations, conversation and storytelling can help reduce ambiguity during routine work or change. Sensemaking is retrospective: people interpret experiences after they occur to guide their understanding and actions.
Socio-technical ecosystem
People, processes, and tools togetherAn organizational approach that treats social relationships, workplace culture, processes, and technology as interconnected parts of knowledge work. People and interaction drive the creation and exchange of knowledge; technological systems support those activities. The approach rejects the idea that software alone can capture expertise or resolve organizational barriers.
Knowledge snapshots
Small, recurring knowledge recordsBrief, periodic records in which employees explain selected aspects of their work, such as how a process is performed, what resources it requires, or why a procedure exists. Incorporating these short accounts into existing reporting routines can make knowledge capture more manageable than asking employees to write comprehensive manuals just before they leave.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.