Librarian professional knowledge work produces outputs that serve two audiences: patrons who need research assistance and institutions that need professional services. An in-depth reference consultation produces knowledge about a patron's research question — but that knowledge can also become a research guide that serves future patrons with similar needs. A collection development analysis produces acquisition decisions — but documented with rationale, it becomes the institutional memory that makes collection development coherent over time.
The research-to-output workflow for librarians organizes around four output types: research guides and pathfinders (structured source guidance for specific research needs), collection development analyses (the documented research underlying acquisition decisions), instructional materials (guides, workshops, and tutorials for patron information literacy), and professional reports (the documented knowledge from reference and professional practice that informs institutional decision-making).
Output Type 1: Research Guides and Pathfinders
Research guides and pathfinders are structured compilations of source guidance for specific research needs. They convert the librarian's source expertise into a self-service resource that serves patrons without requiring a reference consultation.
The research guide development workflow:
The most effective research guides are built from actual reference interactions — cases where a librarian has worked through a research question and identified the most productive sources. A research guide developed from hypothetical knowledge of a research area is less reliable than one developed from actual patron interactions that revealed what sources work and what dead ends to avoid.
Research guide development structure:
RESEARCH GUIDE DEVELOPMENT
Guide topic: [The specific research topic or research type]
Development basis: [What reference experience or expertise underlies this guide]
Development date: [When created]
Last reviewed: [When last updated for currency]
AUDIENCE:
Who this guide serves: [Patron type + research level]
What they're typically trying to accomplish: [Research objective]
Their typical starting point: [What they usually know before consulting the guide]
GUIDE CONTENT:
Getting started: [First steps + orienting resources]
Primary sources: [Core resources with descriptions]
Secondary sources: [Supporting resources with descriptions]
Specialized resources: [For advanced needs]
When to ask a librarian: [What this guide can't do that human help can]
SOURCE VERIFICATION:
All URLs verified: [Date last link-checked]
Coverage information verified: [Date last checked]
Access confirmed: [Library still subscribes / resource still freely available]
MAINTENANCE TRIGGER:
What would make this guide outdated: [Specific sources that change would trigger a review]
Next scheduled review: [Date]
The "when to ask a librarian" section is the section most research guides omit. No research guide covers every scenario; the guide that honestly signals its limits — "for pre-1900 local history sources, the librarian can assist with specialized access that isn't documented here" — is more useful to patrons than the guide that implies completeness it doesn't have.
Source verification as required discipline:
Research guides that contain broken links or outdated coverage information are worse than no guide — they direct patrons to resources that don't exist or don't contain what's expected. A link verification check at creation and at each scheduled review is not optional; it's the quality discipline that makes the guide useful rather than misleading.
Output Type 2: Collection Development Analyses
Collection development analyses are the documented research underlying major acquisition decisions — new database subscriptions, significant print collection expansions, weeding projects, and subject area collection reviews.
The collection development analysis structure:
COLLECTION DEVELOPMENT ANALYSIS
Subject area / resource: [What's being evaluated]
Analysis type: [ ] New acquisition [ ] Renewal evaluation [ ] Weeding project
[ ] Subject area review
Date: [When this analysis was conducted]
Analyst: [Who conducted the analysis]
INSTITUTIONAL CONTEXT:
How this fits our collecting mission: [Alignment with library mission]
Patron population served: [Who would use this resource]
RESOURCE / AREA ASSESSMENT:
What it provides: [Coverage, content type, unique value]
Overlap with existing resources: [What we already have that this overlaps]
Gap it fills: [What need this addresses that isn't currently met]
EVIDENCE OF NEED:
Patron requests: [Data on patron demand — ILL requests, reference requests]
Usage data: [Existing usage statistics if relevant]
Curriculum / research program support: [Academic connections if applicable]
COST-BENEFIT:
Cost: [Acquisition or subscription cost]
Usage estimate: [Projected use based on evidence]
Cost per use estimate: [If comparable usage data is available]
ALTERNATIVES CONSIDERED:
What else was evaluated: [Other resources or approaches considered]
Why this option vs. alternatives: [The comparative judgment]
RECOMMENDATION:
Decision: [Acquire / Renew / Decline / Defer]
Reasoning: [Summary of the recommendation rationale]
CONDITIONS OR FOLLOW-UP:
What should be monitored: [What would indicate the decision was right or wrong]
Review date: [When to revisit]
The "evidence of need" section is what converts a collection development analysis from a professional opinion into a defensible institutional decision. Patron request records, interlibrary loan data, and documented research program needs are the evidence base that makes collection development decisions understandable and auditable.
Output Type 3: Instructional Materials
Instructional materials — library instruction sessions, workshops, online tutorials, and research skills guides — convert librarian expertise into reproducible education. The knowledge management challenge is maintaining the materials as sources and research environments evolve.
Instructional material development structure:
INSTRUCTIONAL MATERIAL
Title: [Name of the session, tutorial, or guide]
Type: [ ] In-person instruction [ ] Online tutorial [ ] Printed guide
[ ] Workshop [ ] Embedded instruction
Development date: [When created]
Last updated: [When last revised]
AUDIENCE AND LEARNING OBJECTIVES:
Who this is for: [Student level, prior knowledge assumed]
What participants will be able to do after: [Specific learning outcomes]
CONTENT STRUCTURE:
[Section 1]: [What it covers + materials needed]
[Section 2]: [...]
TEACHING NOTES:
Common misconceptions to address: [What learners typically get wrong]
Where learners typically struggle: [The hard parts]
What worked well: [Pedagogical choices that have been effective]
What didn't work: [Approaches that haven't been effective]
SOURCE AND TOOL CURRENCY:
Databases demonstrated: [With version or interface date]
Screenshots current as of: [Date]
Next review date: [When to check currency]
ASSESSMENT:
How effectiveness is measured: [Assessment approach]
What assessment has shown: [Results if available]
Teaching notes as institutional knowledge:
The teaching notes — what works, what doesn't, where learners struggle — are the institutional knowledge that makes instructional materials improve over time and that enables other librarians to teach the same material effectively. An instruction session delivered and not documented produces outcomes for that session; documented teaching notes produce outcomes for all future sessions on the same material.
Output Type 4: Professional Reports
Professional reports are the documented outputs of professional practice that inform institutional decision-making: annual reference statistics and trend analyses, collection usage reports, instruction program assessments, and special studies requested by library administration or governance.
Professional report structure:
PROFESSIONAL REPORT
Report title: [What this report is]
Report type: [ ] Annual statistics [ ] Trend analysis [ ] Program assessment
[ ] Special study [ ] Other
Period covered: [What time period]
Author(s): [Who produced the report]
Date: [When produced]
SUMMARY FINDING:
Key finding: [The most important thing this report shows]
Implication: [What it means for the institution]
DATA SOURCES:
What data was used: [Sources + collection period + any data quality notes]
Data limitations: [What the data doesn't capture]
METHODOLOGY:
How data was collected: [Collection method]
Analytical approach: [How it was analyzed]
Comparison period or benchmark: [What it's compared to, if applicable]
FINDINGS:
Finding: [Specific observation]
Evidence: [Data supporting this finding]
Interpretation: [What this means]
Finding: [...]
WHAT THIS DOESN'T TELL US:
[Limitations of this analysis + what additional data or research would address them]
RECOMMENDATIONS:
[If recommendations are appropriate: specific actions with rationale]
NEXT REPORT:
Next reporting period: [When next report covers]
Data to start collecting: [What should be tracked going forward]
The "what this doesn't tell us" section in professional reports is the intellectual honesty discipline that builds long-term credibility with library administration. The annual statistics report that acknowledges "gate count doesn't capture the growing proportion of electronic access" is more useful for institutional decision-making than the report that presents numbers without the context that makes them interpretable.
Key Takeaways
-
Research guides should be built from actual reference interactions, not hypothetical expertise. A guide developed from real reference cases documents what actually works and what dead ends to avoid, not what should work theoretically.
-
The "when to ask a librarian" section is the section most research guides omit and most need. Guides that honestly signal their limits are more useful to patrons than guides that imply completeness they don't have.
-
Source verification is required for research guides, not optional. A broken link or outdated coverage description is worse than no guide — it directs patrons to resources that disappoint. Verification at creation and at each review is the quality discipline.
-
Collection development analyses need an evidence section. Patron request records, ILL data, and documented research program needs convert collection development from professional opinion into defensible institutional decision.
-
Teaching notes are the institutional knowledge that makes instruction improve over time. What worked, what didn't, where learners struggled — documented once, this guides all future iterations of the same instruction and enables other librarians to teach it effectively.
Conclusion
The research-to-output workflow for librarians converts professional knowledge into four output types: research guides and pathfinders (built from actual reference experience, with source verification discipline and honest "when to ask a librarian" signals); collection development analyses (with evidence of need, alternatives considered, and review dates); instructional materials (with teaching notes capturing what worked and what didn't, and source currency review dates); and professional reports (with data source documentation, limitations disclosure, and specific recommendations). The documentation disciplines that make each output trustworthy — source verification, evidence-based recommendations, honest limitation disclosure, and teaching notes — are what convert individual professional outputs into institutional assets that improve service quality over time.
To go deeper, check out Best Web Clipper Extensions.