Key Takeaways
Treat small projects as low-risk auditions for the leader you might become
Practice before promotion. Project management lets librarians lead without becoming permanent supervisors. A project may be as small as shifting shelves or as large as installing a new library system, but both require organizing people, handling setbacks, and taking responsibility for results. The project lead often has no formal authority over teammates, so success depends on motivating rather than disciplining them. That makes projects a useful place to learn how different people work and how to lead colleagues with more seniority.
Learn what fits. Plans prepare teams to adapt, not to follow a script. The book invokes the D-Day landings: the original first-day objectives were missed, but detailed preparation helped leaders adjust and continue. Projects also reveal whether someone actually wants the enduring responsibilities of management. Strong leadership does not require becoming a supervisor.
What's valuable here is the low-stakes rehearsal: leadership can be tested before a career becomes organized around it. This resembles experiential learning, in which people build judgment by acting, reflecting, and trying again. A temporary project also makes it easier to receive feedback because the roles and consequences are bounded. The limitation is that project leadership cannot fully reproduce the legal, emotional, and long-term obligations of supervision. It is a credible preview, not a complete simulation.
Change leadership style when the people and stakes change
Choose the useful approach. Leadership styles describe how a manager makes decisions and relates to a team. Lewin's three broad styles are authoritarian, democratic, and laissez-faire: decisions made by the leader, decisions made with team input, and a hands-off approach. Each has costs. Speed can come at the expense of morale, while autonomy without direction can leave people adrift. Goleman and colleagues describe six approaches, including coaching, visionary, democratic, and commanding, each suited to different needs.
Context can reverse results. Clara Barton led nurses in dangerous Civil War conditions with an assertive approach, but struggled to adapt that style to running the growing American Red Cross. The point is not to select one permanent label. Managers should notice what the situation requires, remain authentic, and adjust rather than treating a preferred style as a universal solution.
This is a practical version of contingency thinking: effectiveness depends partly on the fit between a leader's behavior and the task, team, and moment. Emergency medicine offers a useful parallel. A clear command structure can save time during an acute crisis, while routine care benefits from shared expertise and patient participation. Flexibility, however, must not become unpredictability. Teams need to understand why authority is shifting, or situational leadership can feel like arbitrary control.
Protect dissent, because agreement can hide a team that has stopped thinking
Expect a difficult middle. Bruce Tuckman's group-development model describes five phases: forming, storming, norming, performing, and adjourning. Teams first learn the task and one another, then contest roles and rules, establish working norms, do the work, and eventually conclude the collaboration. The storming phase can feel like failure, but suppressing disagreement may prevent the group from resolving important questions about authority, responsibilities, and priorities.
Make disagreement useful. The book uses John Lennon and Paul McCartney's creative partnership to illustrate how trusted criticism can improve shared work. A devil's advocate tests a group's dominant view by identifying weaknesses. Conflict becomes destructive when people cannot resolve problems or cooperate; it becomes constructive when discussion gives members voice and helps them reach a workable decision. The leader's job is to protect the process, not to make every exchange pleasant.
The distinction between disagreement and hostility is essential. Research on psychological safety, the shared belief that a group can take interpersonal risks, helps explain why candid debate can improve learning: people must be able to question a plan without fearing humiliation. Yet conflict is not automatically productive. A devil's advocate can become a ritual role whose objections are ignored, or a license for antagonism. Leaders need to make dissent consequential by answering it with evidence and a visible decision process.
Match the project method to uncertainty, dependencies, and team capacity
Fit the structure to the work. A project framework organizes tasks, deadlines, responsibilities, and dependencies. A Gantt chart maps tasks across time, including which can happen together and which must wait. Waterfall suits clear, sequential work; Agile divides work into short sprints and revisits priorities; Kanban makes tasks visible as they move from not started to underway to done. More formal approaches, such as PRINCE2, can clarify roles in large projects with many stakeholders. No single method suits every library project.
Diagnose lateness first. Hoover Dam construction, completed two years early and under budget, is presented as an early example of modern project organization, including Gantt charts. But adding staff to a late project may slow it further. Brooks's law describes how onboarding and communication burdens can outweigh extra labor. When a project slips, identify bottlenecks, scope, and hard deadlines before changing the team.
The book's strongest project-management advice is its resistance to methodological loyalty. In software and operations research, tools are valuable when they expose constraints, not when they become ceremony. A visual task board can help a small team coordinate, while a large, regulated project may need explicit approvals and documentation. The caution is that flexibility can disguise indecision: teams still need a clear owner, a definition of completion, and a way to resolve priorities when the plan changes.
Measure what can change a decision, not everything that can be counted
Start with the decision. Assessment is useful when it helps a library improve, explain its work, or meet accountability requirements. It should begin with a goal and a clear definition of success. For an information-literacy program, a satisfaction survey does not prove that students learned to evaluate sources. A skills assessment or rubric may provide more direct evidence, though it takes more effort to design and administer.
Use complementary evidence. Quantitative data shows measurable patterns, while qualitative responses offer context that a fixed-choice survey may miss. Direct measures examine demonstrated outcomes; indirect measures capture perceptions. Baseline data records conditions before an intervention, while benchmarking compares results with similar institutions. These measures work best when collected consistently and reported selectively. More data is not automatically better: excessive metrics can bury the few findings that should guide action.
This principle echoes measurement theory: a metric is only informative when it represents the construct a decision-maker cares about. Satisfaction, attendance, and learning are related but not interchangeable. Combining outcome measures with interviews or open responses can expose why a program succeeds or fails. A further safeguard is to ask who is missing from the data. Low survey response, uneven access, or selection effects can make a tidy dashboard appear more representative than it is.
Middle managers translate between institutional demands and staff reality
Hold two responsibilities. Middle managers sit between senior administration and the people doing the daily work. They communicate policies downward, carry staff concerns upward, and keep their units functioning. Their authority has limits: making decisions beyond their mandate can create risk, but escalating every small issue prevents others from trusting their judgment. The work is to learn which problems to resolve, which to report, and when a decision belongs to someone higher in the organization.
Think beyond one specialty. A librarian promoted for expertise in reference, cataloging, or electronic resources may find that supervision, planning, and budgeting now take substantial time. Managing a unit also means understanding how its resources and goals fit the wider institution. The transition can be a fulfilling career in itself, not merely a required step toward becoming a director.
The translator role resembles boundary-spanning work in organizational sociology: people in the middle connect groups that have different information, incentives, and vocabularies. That position can help an institution detect problems early, but it can also make the manager a pressure sink, absorbing demands from both directions without enough authority to resolve them. Clear decision rights and a director willing to tolerate reasonable mistakes are therefore not perks. They are infrastructure for effective middle management.
Manage each employee as a developing professional, not a job category
Tailor support to the person. Students, paraprofessionals, and librarians have different goals and experience. Student workers can gain transferable skills when managers connect tasks to career interests, provide training, and ask what they are learning. The book draws on George Kuh's student involvement theory, which links students' engagement in purposeful activities to educational benefits. A student interested in computing might gain relevant experience with a library website or digitization work.
Respect varied expertise. Experienced paraprofessionals may know operations better than a new librarian, so managers should treat them as colleagues and support career development that does not require a graduate degree. Librarians benefit from professional autonomy, mentoring, and opportunities suited to their career stage. Human Resources should be consulted before discipline, dismissal, promotion, or other sensitive actions, since institutional rules and legal obligations are easy to overlook.
This approach aligns with person-centered management: motivation often grows when people see competence, autonomy, and purpose in their work. It also challenges the assumption that development means promotion into management. A strong organization needs expert practitioners, and career paths should recognize that contribution. Mentorship does require boundaries, especially where a supervisor evaluates the person they advise. Clear expectations, equitable access to opportunities, and HR guidance help keep supportive relationships from becoming favoritism.
Let strategy shape what gets funded and what gets refused
Turn values into choices. Strategy is the pattern in an organization's decisions. Strategic planning connects its mission to objectives, concrete actions, and measurable indicators. A library may decline an attractive, expensive event that does not advance its central goals, while accepting a demanding project to preserve and digitize a local newspaper archive because it supports access to information. The plan is a guide for allocating scarce resources, not a list of every appealing idea.
Culture lives in practice. The Competing Values Framework describes four broad organizational cultures: adhocracy, clan, hierarchy, and market, reflecting different balances of flexibility, stability, internal focus, and external focus. A stated value such as work-life balance means little if policies and leaders reward constant availability. Managers can shape a unit's culture through how they allocate time, make decisions, treat dissent, and hold themselves accountable.
The connection between strategy and culture is important because plans do not execute themselves. Budgets, hiring, recognition, and daily routines reveal which priorities are real. This is close to the idea of institutional isomorphism: organizations often copy familiar plans and structures to appear legitimate, even when local conditions differ. The book appropriately emphasizes context. A useful plan should be distinctive enough to reflect the library's community, yet measurable enough that leaders can see when assumptions no longer hold.
Earn executive support by showing how the library solves shared problems
Translate value for outsiders. A director is the library's chief representative, often reporting to an administrator who has never worked in a library. The director must explain how library services advance that administrator's goals, such as student success, community education, or access to information. This is managing up: understanding a supervisor's priorities and pressures, then making the library's contribution legible without simply passing problems upward.
Build a case people remember. Data can show reach and value when presented with context. In 2015, New York Public Libraries served 37 million people, compared with 9 million attendees at major professional sports games. The comparison makes the library's scale easier to grasp. Impact claims should be carefully supported: high library use among a group does not prove the library caused that group's outcomes. Pair useful statistics with stories and be candid about what the evidence can establish.
This is a lesson in translation, not spin. Public value often becomes visible when an institution connects its services to a stakeholder's own objectives, a form of boundary work between professional expertise and political decision-making. Comparisons can make scale vivid, but they can also mislead if the measures differ or obscure quality. Strong advocacy therefore pairs a memorable frame with transparent methods, so a persuasive narrative does not outrun the evidence.
Forecast costs and tradeoffs before creating recurring commitments
Budget for the future. A director needs a usable line-item view of accounts, planned spending, and reserves, plus a working knowledge of the institution's rules and budget calendar. Incremental budgeting starts from the previous year's allocations; zero-based budgeting requires managers to justify expenses anew. Each offers a tradeoff between predictability and scrutiny. Benchmarking against similar libraries can show whether spending is reasonable.
Use resources creatively. Middle managers may control staff time, equipment, and position descriptions even when they do not control the budget. A vacancy can be redesigned around changing needs, or two units can combine resources to support a shared position. Donations and grants are more realistic for defined projects than for routine operating costs. Before adding a subscription or staff line, forecast its future cost: recurring commitments become painful when funding later shrinks. Separate financial duties to protect both the institution and employees.
Budgeting is a form of strategy under constraint. Forecasting matters because a one-time purchase and a recurring salary create very different future obligations, a distinction familiar from public finance and capital planning. Participatory budgeting can also improve legitimacy by giving staff a voice in tradeoffs. Yet participation cannot make scarcity disappear, and shared positions or downgraded roles can carry fairness and retention costs. Efficiency should be weighed against service quality and the long-term health of the workforce.
Plan crisis responses, then communicate honestly one decision at a time
Prepare for ordinary disasters. A crisis may be a hurricane, a pandemic, a budget shock, bed bugs, or a pipe bursting over library materials. Plans should identify likely scenarios, assign authority, set communication channels, and specify equipment and response steps. Texas A&M University-Corpus Christi's library prepares for hurricanes by protecting collections and moving archival materials to higher ground. Drills and tabletop exercises help staff test whether procedures make sense before pressure arrives.
Lead with steadiness and care. During a crisis, communicate promptly without pretending to know more than is known. Staff need accurate updates, clear next steps, and evidence that their safety and personal circumstances matter. Afterward, review what worked, document lessons, and share them so the institution and profession can learn. A calm leader does not need to predict every consequence; the immediate task is to make the next sound decision.
Crisis leadership depends on both operational readiness and social trust. Emergency-management research emphasizes rehearsed roles because stress narrows attention and makes improvised coordination harder. The book's insistence on honest updates complements that preparation: credibility is a resource that cannot be manufactured during an emergency. One caution is that calm should not be confused with certainty. Leaders can acknowledge uncertainty while still making responsibilities, protective actions, and the timing of the next update explicit.
Treat accreditation as continuous maintenance, not a last-minute performance
Keep evidence current. Accreditation and peer review evaluate whether a library meets defined standards and where it can improve. The process is strongest when it is honest, concise, and supported by relevant documentation. A director should identify every standard that applies, audit the library's current practices, address fixable gaps, and record evidence as work proceeds. If a policy or practice is not documented, reviewers may be unable to verify it.
Learn before the visit. Peer review can include a self-assessment report, external evaluators, and a campus visit. Reviewers are not merely inspectors to evade; they can offer perspective from comparable institutions. Accreditation is tied to consequential institutional benefits, including eligibility for federal student aid for universities. Reviewing standards annually reduces the scramble before a formal visit and helps a director push back when proposed changes could undermine required services or resources.
Continuous review turns compliance from an episodic paperwork burden into organizational memory. The same principle appears in safety engineering, where routine checks catch small failures before they combine into major ones. Documentation also protects institutional knowledge when leaders change. Still, standards are proxies for quality, not quality itself. A library can satisfy a checklist while missing community needs, so formal compliance should inform judgment rather than replace it.
Analysis
This book's organizing argument is that library management is learned through successive changes in responsibility, not acquired in a single promotion. Project leadership teaches planning, adaptation, assessment, and influence without formal authority. Middle management adds the harder work of translating between staff and administration, developing employees, and allocating resources. Directors then represent the library outward, manage other managers, secure support, and accept accountability for institutional outcomes. The sequence is persuasive because each level expands the same capabilities rather than discarding them.
Its most useful corrective is to the familiar assumption that managerial advancement is the natural reward for professional excellence. A capable librarian may prefer practice to supervision, and middle management can be a meaningful destination rather than a rung to rush past. The practical examples also resist the fantasy of managerial omnipotence: library leaders operate within budget rules, accreditation standards, organizational politics, and limited authority. Good intentions matter, but the book consistently returns to execution, evidence, and judgment.
The strongest themes reinforce one another. Assessment gives leaders evidence, strategy gives that evidence direction, and communication translates decisions to people who need to support or carry them out. Culture is not separate from these systems: employees learn what the institution values from how it distributes money, authority, recognition, and time. Crisis leadership makes the same point under pressure, when trust and established procedures become operational assets.
A limitation is that many tools are presented as adaptable practical guidance rather than as interventions with quantified effects. Frameworks such as group-stage models and culture typologies are useful maps, but real teams and institutions may not move neatly through prescribed categories. The book is strongest when it treats frameworks as prompts for observation, not rules. Its enduring lesson is therefore not to imitate a single ideal manager, but to build context-sensitive judgment while remaining answerable to staff, patrons, and the institution.
Glossary
Tuckman's model of group development
Five phases of teamworkA model describing how temporary groups commonly develop through forming, storming, norming, performing, and adjourning. Members first learn about the task and one another, then negotiate roles and working rules, establish shared practices, complete the work, and conclude the collaboration. The phases help leaders interpret turbulence, though real groups may revisit or skip stages.
Competing Values Framework
Four organizational culture typesA framework for understanding organizational culture along two dimensions: internal versus external focus, and stability versus flexibility. Their combinations produce four broad culture types: clan, adhocracy, hierarchy, and market. The framework helps managers consider whether workplace norms fit their institution and employees, but it is a diagnostic lens rather than a complete description of any organization.
Brooks's law
Staffing can delay late workThe principle that adding people to a late project can make it later. New team members need orientation, and existing members must spend time communicating tasks and context. Additional labor helps only when the work can be divided effectively and the benefits exceed coordination costs. The idea cautions managers against treating headcount as an automatic cure for delay.
Kanban board
Visual task trackingA board that displays project tasks in categories such as work to do, work underway, and completed work. Team members move task cards as progress occurs, making workload and bottlenecks easier to see. The method is lightweight and useful for teams organizing their own work, but it may not provide enough structure for complex projects requiring detailed roles, dependencies, or centralized control.
Strategic planning
Goals guide organizational decisionsA process in which leaders and stakeholders establish objectives and actions that guide organizational decisions and resource use. It typically connects a mission to evidence gathering, objectives, strategies, performance indicators, review, and implementation. A strategic plan should be revisited as conditions change, and lower-level unit goals should support the wider institution's priorities.
Baseline data
Measures before an interventionData describing conditions before a project or intervention begins. It provides a point of comparison for determining how results change over time. Baseline data is most useful when later measurements use consistent definitions and collection methods. Without it, a library may know what its current results look like but have difficulty demonstrating whether a program made a difference.
Managing up
Support a supervisor's goalsThe practice of understanding a supervisor's priorities, communication preferences, and pressures, then helping make those goals more achievable. For a library director, this includes explaining how library services advance the broader institution's aims, preparing the supervisor for emerging problems, and raising disagreement respectfully. It is relationship-building and clear communication, not simply flattering a superior.
360-degree performance review
Feedback from multiple work relationshipsAn evaluation that gathers input about a manager from people beyond the manager's own supervisor, including colleagues and direct reports. Feedback is often collected anonymously through structured and open-ended questions. It can reveal management problems that are otherwise difficult to detect, but it requires careful handling, clear criteria, and follow-through to avoid turning feedback into an unaddressed survey exercise.
Separation of duties
Split financial responsibilitiesAn accountability practice that assigns different financial tasks to different people. For example, the person approving a purchase should not be the only person reviewing the resulting charge, and cash handling should be separated from deposit preparation and reconciliation. The division reduces opportunities for errors or misuse and helps protect employees as well as the institution.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.