Library Leadership Is Stewarding the Wrong Thing
Ask what a library leader is supposed to protect, and the answers you get most often are a building, a budget, and a collection. Renovate the space. Defend the headcount. Preserve the archive. Those are real responsibilities. But they are means, not the mission.
That’s not because the field lacks the right language. A 2025 Ithaka S+R survey found library leaders already rate their own institutions closer to service-oriented than collection-oriented, and call research support, critical-analysis skills, and instruction highly important almost unanimously. The problem isn’t what leadership says the priorities are. It’s what happens when a budget tightens or a reorg lands. What gets protected first is what a spreadsheet or a floor plan can show got protected: the space, the collection, the budget line, the org chart. Not necessarily the capability that made the stated priority real.
The space problem
A lot of library leadership vision starts and ends with square footage. Renovate the ground floor into a maker space, add a café, brand a wing as a “third place.” Spaces matter, and a good one draws people in. But a vision built around space treats the library as a destination rather than a participant. It measures success in gate counts and renovation photos instead of in what got discovered, built, or published because the library was in the room. A space is a container. Leadership that stops at the container has confused the shape of the thing for what the thing does.
The museum problem
The other default vision is custodial: the library as steward of a permanent collection, protecting what already exists. That instinct is not wrong, it is incomplete. Stewarding the scholarly record matters. But an institution that only stewards what already exists has nothing to say about what gets created next. The library’s most valuable seat is not in the archive, it is in the research partnership, the instruction collaboration, the infrastructure decision, at the point where new knowledge is actually being made. A vision that stops at custody protects the past. Leadership has to also build the conditions for what comes after it.
The bean-counter problem
Underneath both of those sits a third pattern that is not really about libraries at all. Higher education broadly has absorbed a management style built for cutting cost and counting output, and library leadership has absorbed it too: efficiency ratios, consolidation, headcount as the primary lever. That style is not rooted in any evolved sense of what the mission is now. It optimizes an org chart against a budget line without asking what capability the actual work of knowledge creation requires today. A library run like a cost center will be run efficiently and will not lead anything.
The cargo-cult problem
Layered on top of all three is a pattern of following structural fashion instead of function. Consider the recurring move from subject-based liaison structures to centralized functional teams. Either model can work, and libraries that made the switch often had real reasons: aligning with institutional strategy, building research support a generalist liaison couldn’t. The cargo-cult version isn’t picking one model over the other. It’s adopting one because peer libraries did, without first naming the service failure it’s supposed to fix, mapping the relationships it will disrupt, or defining how anyone will know afterward whether it worked. A structure copied because it is currently in fashion, with no answer to any of that, is not a strategy. It is a costume.
These are four different substitutions for strategy: place, possession, efficiency, and structure. Each is easier to see and manage than the harder, distributed work of actually helping knowledge get made.
The irony
The clearest sign of the substitution is what it does to technology. Librarianship describes itself as grounded in information science. Libraries have in fact repeatedly adopted new information technologies: networked catalogs, digital licensing, link resolvers, repositories, discovery systems, open-source platforms. The troubling pattern isn’t adoption speed. It’s that leadership keeps approaching each new wave through risk, policy, procurement, and vendor management, instead of claiming a substantive role in shaping how it organizes knowledge. Caution is necessary. Caution that never turns into technical capacity, experimentation, or governance on the field’s own terms isn’t caution anymore. It’s spectatorship. Metadata, knowledge organization, information architecture, controlled vocabularies, the entire discipline of making information findable and trustworthy: those are not adjacent to what AI and open science need right now. They are indispensable parts of what is needed, and the field that has spent a century building that expertise keeps acting like it belongs to someone else.
The claim worth making
Library leadership’s actual job is stewarding the conditions under which knowledge can be created, organized, accessed, and sustained, not the room it happens in, not the objects it already produced, not the org chart around it. That means showing up as a research partner, not a landlord. It means treating instruction, data infrastructure, and open science as core mission, not adjacent service. It means leading with the field’s real expertise instead of importing someone else’s management vocabulary to feel legitimate.
That is a harder vision to build toward than a renovated lobby, and it is the only one that matches what the profession actually knows how to do.