Library
Consulting
Firms

When every proposal looks the same

Consider a director at a mid-sized regional university who has just received a charge from her provost: produce a plan that renovates the main library, extends its digital collection infrastructure, and positions the institution's research services for the next two decades. She issues a request for proposals and, six weeks later, sits with four submissions from library consulting firms on her desk. Each is well-formatted. Each cites the ACRL Framework for Information Literacy. Each promises stakeholder engagement, needs assessment, and a final program document. Each firm's biography lists impressive institutional names.

She calls a colleague who completed a similar process at a comparable institution. The colleague's advice is direct: proposals all look the same because firms write them to win, not to reveal. What the director needs to examine is what lies underneath the proposal narrative: the method the firm will use to understand her library before it recommends anything, the kind of document it will produce at the end, and whether it has genuine experience guiding institutions through digital library development as well as physical renovation.

This scenario replays itself across academic, public, and special library sectors every year. The proposal document is not a reliable signal of expertise. What separates library consulting firms that deliver lasting institutional value from those that produce polished but generic work is not how they write but how they think — and testing that distinction requires a structured evaluation process before the engagement begins.

A named, repeatable diagnostic method distinguishes evidence-based practice from accumulated professional opinion. Firms with structured instruments produce programs that hold up under board, bond counsel, and provost scrutiny.

Deep familiarity with academic, public, law, medical, and special library environments means that a consultant reads collection data, behavioral patterns, and workflow adjacencies through the right professional lens from the first site visit.

The institutions that benefit most from a consulting engagement are those whose firms treat electronic resource management, knowledge base architecture, and physical space programming as a single, unified service design question.

An independent professional voice carries weight in a boardroom or bond hearing that an internal memorandum cannot replicate. The best firms combine technical program authority with the communication standing to defend findings publicly when institutional decisions require it.

Ask what the firm does, not what it believes

The most reliable way to distinguish library consulting firms before committing to an engagement is to ask each firm to describe its methodology, not its philosophy. A philosophy statement tells you what the firm believes. A methodology statement tells you what the firm does, in what sequence, using what instruments, and to produce what specific outputs. If the answer is vague, that vagueness is itself the finding.

In more than fifty years of practice at Aaron Cohen Associates, the work has consistently fallen into three overlapping roles: diagnostician, strategist, and institutional advocate. The diagnostic role is where methodology is most visible. It requires a structured instrument for observing how people actually use a library space or digital system — not how staff believe they use it, and not how gate counts and usage statistics summarize it. The Visual Scan, a facilitated walkthrough conducted with community members and staff together, generates an observational record of behavior that becomes the evidence base for every recommendation that follows. When evaluating library consulting firms, ask each one to name and describe its diagnostic instrument. If a firm cannot do so with precision, it is relying on accumulated experience rather than repeatable method.

The strategic role requires the ability to translate service aspirations into precise specifications. In physical planning, this means producing a building program that architects can design from and boards can fund: square footage allocations, adjacency requirements, collection capacity models, and technology infrastructure standards. In digital library planning, the same precision applies: an inventory of current resources against actual use, an assessment of where user research breaks down, a coverage analysis by source type, and a service plan that connects access, evaluation, navigation, and instruction into a coherent design. A firm that produces both kinds of specifications, treating physical and digital planning as integrated aspects of the same institutional question, is operating at a level most generalist advisors cannot reach.

The institutional advocate role is the least discussed and often the most valuable. As described in Computers in Libraries by the partners of this firm, consultants function simultaneously as technical expediters and political activists. The external voice of an independent professional carries weight in a boardroom, a provost's office, or a bond hearing that an internal memorandum cannot replicate. When evaluating library consulting firms, assess whether the firm's project leads have the standing, communication skills, and sector credibility to perform that function when institutional decisions require it.

A named diagnostic method with a described sequence and observable outputs — not a vague reference to site visits. The Visual Scan is one such instrument: a facilitated, structured walkthrough that produces an observational record of actual patron behavior.

A structured stakeholder engagement protocol that generates shared institutional understanding rather than a summary of collected opinions. The difference between discussion, debate, and genuine dialogue is methodological, and it is demonstrable.

A demonstrated capacity to produce buildable program documents with technical specifications — not narrative summaries. An architect or vendor should be able to begin work directly from the firm's deliverable without further interpretation.

The ability to address physical space planning and digital library development as integrated aspects of the same service design question — with sector-specific case histories from institutions comparable to yours in type, scale, and planning challenge.

A process, not just a product

A well-constructed engagement proposal describes a process, not just a product. It tells the client how findings will be gathered, how they will be validated with the people who generated them, and how they will be translated into decisions the institution can act on. The absence of a described process is itself a signal: it means the firm intends to decide its method after the contract is signed, based on what seems appropriate at the time.

An Information Needs Assessment framework, as applied in federal library consulting practice, examines the future of library services, the current state of existing services, the gap between the two, and the detailed planning required to close that gap. That four-part structure is a reasonable baseline for any engagement. What distinguishes deeper practice is the rigor of the methods applied at each stage: how the current state is assessed through observation rather than self-report, how the gap is validated across stakeholder groups who may see it differently, and how the resulting plan is specific enough to guide budget decisions, procurement, and construction.

The best proposals also describe the deliverable architecture in detail. A building program is not a report about what the building should feel like. It is a technical specification: square footages, adjacency matrices, collection capacities, furniture and equipment standards, and technology infrastructure requirements. A digital library service plan carries the same standard of specificity: each service area, its user group, its content and knowledge base software requirements, its instructional support design, and its integration with the physical environment. When you review proposals from library consulting firms, ask yourself whether an architect could begin design work from this document, or whether a vendor could respond to it as a technical requirement. If the answer to both is no, the deliverable is a summary, not a program.

Services listed in the Library Consultants Directory span facilities design and planning, strategic planning, needs assessment, technology management, collection development, and stakeholder engagement. Those categories describe what consultants offer. They do not describe how they deliver. The proposal evaluation process must go below the category level to the method level, and doing so requires asking specific questions rather than reading proposals at face value.

A phased work plan with named deliverables at each stage and a described method for producing each one. The proposal should answer, before work begins, what the institution will hold at the end of every phase and how the firm produced it.

A diagnostic phase that includes structured behavioral observation, not just document review and stakeholder interviews. The Visual Scan methodology is the instrument that converts observable patron movement into an evidence base that defends every downstream recommendation.

A digital library component that addresses electronic resource management, knowledge base architecture, AI tool integration, and digital literacy instruction as a unified service design — not a separate technology section appended to the physical planning report.

What to do before you sign

Request case histories specific to your institution type and planning challenge, with details about what deliverable each produced and how the institution used it after the engagement ended. Generic institutional name lists are not case histories; a comparable case history names the planning challenge, describes the method applied, and identifies the deliverable and its institutional use.

Ask each firm to describe its diagnostic methodology by name and sequence before the proposal stage, not during the engagement. A firm that cannot do so before it is hired will not develop one after. This is the single question most likely to reveal the difference between methodological depth and accumulated professional opinion.

Verify that digital library development, digital literacy program planning, and electronic resource management are part of the firm's core practice, demonstrated by prior engagements with comparable institutions, not by listing digital services in a capabilities statement.

Ask to meet and speak directly with the project lead who will manage your engagement, not only the senior principals whose credentials appear in the proposal. The proposal is written by the firm's strongest communicators. The engagement is managed by the person assigned to it, and those may not be the same individuals.

What to avoid

• Selecting library consulting firms based on proposal length, graphic quality, or institutional name recognition alone.
• Accepting reference projects that are not comparable in institution type, planning challenge, or scale as evidence of relevant expertise.
• Hiring a firm that opens digital library planning discussions with platform selection rather than user and service needs assessment.
• Letting procurement timeline pressure compress the evaluation process enough to skip reference conversations with peer institution directors.
• Assuming that professional association membership, conference presence, or publication history substitutes for demonstrated methodological depth in comparable engagements.
• Treating the written proposal as the primary evaluation instrument: the interview, the sample deliverable, and the reference conversation are consistently more revealing.