Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Project Management in the Library Workplace

Project Management in the Library Workplace

Choose, coordinate, and sustain library projects without burying staff in extra work.
by Alice Daugherty 2018 368 pages
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Select projects by strategic value, capacity, and the work they displace.

The portfolio matters. Libraries face more worthy ideas than available staff, time, and money. Project management therefore begins before individual project plans: leaders must choose work that advances shared priorities, consider what it depends on, and weigh what will be delayed to make room. The book distinguishes managing projects well from choosing the right projects in the first place. A project that finishes on schedule can still waste resources if it does not serve the library's goals.

Make trade-offs visible. A shared project list and calendar help reveal clashing deadlines, overloaded teams, and work happening unnoticed in separate departments. A new project may deserve priority, but decision makers should understand the consequences for existing commitments before reallocating staff.

Analysis

What's striking is that prioritization is treated as a real management decision, not a spreadsheet exercise. A portfolio expresses what an institution is willing to stop doing, defer, or protect. That makes transparent choices valuable to staff as well as executives: a postponed project is less likely to feel like a personal rejection when the trade-off is explicit. Strategic alignment still needs scrutiny, since a plan can faithfully reflect leadership preferences while missing frontline or community needs. The strongest portfolio process makes room for both institutional direction and evidence about who benefits.

Test an idea before it becomes a promise of staff time.

Screen before launch. Pre-project planning is an early review that turns a promising idea into an informed proposal before the organization commits to full implementation. The proposed workflow asks the originating team to define the problem, assess feasibility, and prepare a prospectus for review. Feasibility means confronting actual staffing, skills, costs, infrastructure, deadlines, and long-term maintenance, rather than imagining an ideal organization with unlimited capacity.

Give ideas a fair route. A prospectus describes the project lead, intended users, resources, timeline, dependencies, success measures, risks, and work explicitly excluded. A supervisor or review team can approve it, send it to senior administrators, or close it with reasons documented. Recording why an idea is not feasible prevents repeated debate and preserves useful context when staff change.

Analysis

This screening stage turns saying no into an accountable act rather than a quiet stall. It also makes proposal development accessible beyond employees with strong personal networks, provided the process is clear and genuinely open. The practical challenge is keeping the filter proportionate: an elaborate prospectus can consume the very capacity it is meant to protect. The text's emphasis on tailoring the workflow to project size is important. Lightweight questions can be enough for a modest service improvement, while expensive, cross-unit work merits more examination.

Define the change, the finish line, and what ordinary work remains.

Separate project from routine. A project is temporary and creates a distinct product, service, or result. Processing books every day is routine; redesigning the processing workflow for a defined launch is a project. This distinction matters in service organizations, where a new service may become permanent even though the work to create it should end.

Start with the reason. The chapter uses a self-checkout service to show how a clear idea still needs explicit objectives, such as improving patron independence or privacy. Asking why repeatedly can expose whether the proposal solves a real need. Objectives connect the work to the library's mission, while outcomes make success assessable. A library's whiteboard survey produced interesting student comments, but without a stated purpose or next action, it generated activity rather than a useful result.

Analysis

A defined finish line protects both project teams and the services that inherit their work. The distinction between objectives and outcomes is especially useful: an institution may value privacy as a goal but need a practical proxy, such as patron feedback, to judge whether the service helped. Measures should not be mistaken for the underlying value. When a project concerns trust, learning, or access, counting outputs alone can reward completion while obscuring whether users are better served. Clear scope makes that gap discussable rather than invisible.

Borrow methods selectively; match structure to uncertainty and scale.

Choose tools for the work. Waterfall organizes work in sequential phases and supports projects with stable requirements, clear handoffs, and significant risk. Its detailed plans can make changes expensive and creativity harder. Agile methods work in shorter cycles with frequent feedback, making them useful when requirements are uncertain, but repeated change and user consultation can exhaust teams. Scrum provides a structured version of this iterative approach. Kanban makes work visible, while Six Sigma targets errors and variation in repeated processes.

Avoid method worship. The book's warning is practical: documentation and certification cannot rescue a bad project, the wrong team, or a plan detached from institutional priorities. A website redesign may benefit from iterative user feedback; a construction project may require more advance coordination. Libraries can adopt useful elements without importing an entire corporate system.

Analysis

The method is best understood as a response to the project's uncertainty, not as a badge of organizational sophistication. Sequential planning can reduce ambiguity where tasks truly depend on one another, while iterative work can expose mistaken assumptions early. Neither approach removes uncertainty; each manages it differently. A useful test is whether a tool improves decisions or merely produces paperwork. The book's examples also suggest that hybrid practices are often sensible, especially when a digital project combines predictable physical preparation with evolving software or user requirements.

Treat adoption as part of delivery, not an afterthought.

A launch is not acceptance. Project management organizes the work; change management addresses how people move from current practices to new ones. When a project changes systems or services, staff and users may need reasons to participate, opportunities to shape the result, and practical support to use it. The chapter's information-management project aligned its technical proposal with employees' everyday frustrations, tailored messages to different work groups, and invited teams to review the metadata they used.

Reinforce the new practice. Training, coaching, communication, and follow-up help new routines take hold. The team offered group sessions, one-to-one help, online guides, and later review of system use. Small completed improvements also showed participants that feedback could lead to action. A system can be technically complete while its intended organizational change remains unfinished.

Analysis

This distinction helps explain why a project can deliver its specified product yet fail to create its promised benefit. Adoption is not simply resistance to be overcome; it can reveal a poor fit between a designed solution and the work people actually do. Participation is most useful when feedback has a visible route into decisions. It also requires boundaries: endless consultation can delay action, while consultation without influence breeds cynicism. A good change effort says what is open to revision, what is fixed, and how concerns will be handled.

Give project leadership time, authority, and clearly bounded responsibility.

Do not add a second job invisibly. Project managers coordinate scope, people, time, communication, and risk. When those duties are appended to specialist roles without reducing other work, both the project and the employee's core responsibilities can suffer. Hesburgh Libraries responded by creating a virtual project management office, a cross-library function staffed by dedicated project managers who supported planning, communication, and shared practices without replacing the regular organizational structure.

Separate leadership from expertise. The University of Maryland's Severn storage project began with a broad working group, but two accidental project managers ended up driving much of the work. The move of 500,000 volumes succeeded, yet the project lacked formal leadership and early coordination. A doorway too small for the required equipment illustrated the cost of missing key expertise and dependencies during planning.

Analysis

Dedicated coordination can protect technical specialists' attention and give cross-unit work a neutral convenor. The Severn case shows, however, that merely naming a committee does not create leadership, authority, or expertise. Conversely, a project manager cannot be expected to make every substantive decision. Sponsors, subject experts, and operational owners need distinct responsibilities, with a clear path for resolving conflicts. The model should also acknowledge the labor involved: project work is not free simply because staff salaries already exist.

Use visible agreements to lead even when nobody reports to you.

Make coordination concrete. In many academic libraries, project managers cannot assign work through supervisory authority. They can still clarify who is affected, what each person needs to know, and who is responsible for each task. A stakeholder register records relevant people and their interests; a Responsibility Assignment Matrix links tasks to people. In a RACI chart, contributors are marked as responsible, accountable, consulted, or informed.

Keep changes legible. Shared plans, regular updates, and a documented process for reviewing change requests can prevent surprise work and expose the effects of added scope. These tools help a project manager coordinate peers and make the consequences of a request visible to sponsors. Sensitive assessments of individual stakeholders should remain restricted, while task ownership and approved project information can be shared with the team.

Analysis

The chapter's most useful insight here is that influence can come from reducing uncertainty, not only from formal power. A visible assignment makes commitments easier to discuss and gaps harder to overlook. But visibility has a limit: tracking can become surveillance if it records activity without clarifying purpose or supporting staff. The best project artifacts serve the people doing the work, not merely those overseeing them. Keeping the stakeholder analysis private while sharing agreed responsibilities is one way to balance candor with trust.

Use focused collaboration to prove the library's scholarly value.

Work alongside users. The University of Kansas Libraries piloted Research Sprints, matching three faculty members with library teams for an intensive week. The projects created digital research or teaching outputs, including an interactive historical map, an online science lab, and an adaptable course resource on gamification. Faculty reported that the week exceeded expectations and gave them a fuller view of library expertise.

Structure the intensity. Teams used project scopes, task plans, and daily logs, but not every participant used each tool. Project managers adapted the process to team preferences. The pilot involved 11 library participants and required an estimated 640 combined hours of preparation, delivery, and follow-up. Its promise was deeper partnership, not a low-cost service model, so project scope, staff availability, and longer-term tracking mattered.

Analysis

A concentrated collaboration can reveal expertise that a brief consultation cannot, because partners experience the library's contribution across a whole piece of work. That makes the Sprint model a relationship-building strategy as much as a production technique. Its high labor cost is also central evidence, not a footnote: a successful pilot for three faculty members does not establish a scalable service for everyone. The model is most persuasive when institutions identify which partnerships merit this depth and capture whether those collaborations remain useful after the intensive week ends.

Build digital collections as living services, not finished scans.

Plan across the full lifecycle. Digital projects involve collection selection, preparation, digitization, quality checks, metadata, access, archiving, and long-term preservation. At the University of Maryland, one team used sequential planning for digitization production, while another used iterative development for repositories and user interfaces. The methods differed because the work differed, and handoffs between them required steady communication.

Connect collections and teams. Digital content hubs bring materials that once sat in separate archival collections into shared online discovery environments. Cross-functional teams combine curatorial knowledge with metadata, preservation, and technical skills. The book also stresses maintenance: files need ongoing stewardship, and storage and preservation costs can outlast the funded digitization project. Making an item available online is a milestone, not proof that it will remain accessible.

Analysis

Digital access can make a collection appear complete at the moment of publication, while quietly creating continuing obligations for preservation, software, metadata, and rights. Treating that work as part of the service model changes project selection: the true cost is not just the scan or interface. The hub model also shifts professional boundaries, since discovery depends on cooperation among people who may previously have managed separate collections. Integration can increase reach, but it needs to preserve the context that makes archival materials intelligible.

Build project culture through habits, but read maturity data cautiously.

Practice before perfection. A five-level project management maturity model describes a path from improvised practices to organization-wide standards and continuous improvement. A survey of Big Ten Academic Alliance libraries found that respondents often perceived projects as successful despite limited formal processes. Among the participating libraries, 54% of respondents said projects were usually aligned with strategic plans, but only 21% reported a regular annual planning process. Clan-oriented cultures appeared more likely to use formal practices than strongly hierarchical ones, though the study was small.

Make good practice ordinary. The book recommends teaching project skills, writing down expectations, having leaders model them, measuring results, and recognizing completed work. Training and review sessions help turn project lessons into shared institutional knowledge instead of leaving them with whoever happened to manage the last project.

Analysis

Maturity is more than the presence of templates. A library may deliver useful work informally, while lacking the shared systems needed to coordinate a larger portfolio or learn consistently from experience. The survey's mismatch between perceived success and reported controls cautions against treating either self-assessment or a maturity score as definitive. Cultural findings are suggestive, not proof that one organizational style causes better project outcomes. The practical aim is not to make every library project bureaucratic, but to build enough common capability for complexity without extinguishing local initiative.

Analysis

This edited volume makes a case for project management in libraries, but not for importing a single universal system. Its chapters repeatedly return to three linked problems: how an institution selects work, how teams coordinate it, and how a completed project becomes a sustainable service. That sequence is more revealing than any single methodology. Project discipline begins with a decision about whether work deserves scarce attention, continues through role clarity and communication, and ends only when the organization can maintain what the project created.

The collection's strongest contribution is its translation of project methods into a service-oriented setting. A library's output is often not a finished object but a change in access, instruction, research support, or organizational practice. Such outcomes are harder to define and measure than a construction milestone or a software feature. The chapters respond by emphasizing purpose, user involvement, explicit scope, and lifecycle planning. They also make a persuasive case that people and organizational context are not peripheral risks. They are part of the work itself.

There is a productive tension between formalization and adaptation. Pre-project review, common templates, dedicated project managers, and offices can prevent hidden workloads and conflicting initiatives. Yet an oversized methodology can consume time, discourage experimentation, or create an illusion of control. The most convincing cases therefore tailor the degree of structure to scale, uncertainty, interdependence, and institutional capacity. The book's own evidence supports caution: survey respondents reported relatively strong project outcomes despite weak standardization, while the survey sample was too small to establish cultural causes.

The useful conclusion is not that every librarian should become a certified project manager. It is that institutions should stop treating project labor as invisible extra work. Define which initiatives merit formal management, resource the coordination they require, build in adoption and maintenance, and retain the authority to revise or stop work that no longer serves users. Project management is most valuable when it helps a library choose and sustain change, not merely document activity.

Summary in 30 Seconds
Libraries need to weigh each proposed project against strategic priorities, staff capacity, and the work it would delay. Early feasibility reviews clarify costs, dependencies, risks, and success measures before resources are committed. Match planning methods to a project's scale and uncertainty, and make responsibilities and changes visible. Adoption requires communication, training, and follow-up; digital collections also need ongoing preservation. In one survey, 54% reported usual strategic alignment, but only 21% had regular annual planning.
Contains spoilers

Last updated:

Report Issue
Want to read the full book?

Glossary

Pre-project planning

Screening before commitment

A structured stage for developing and evaluating a proposed project before formal authorization and full resource allocation. It typically clarifies the problem, assesses feasibility, prepares a prospectus, secures reviews, and positions approved work within the library's project portfolio. It can also document why an idea should be revised, delayed, or closed.

Organizational Project Management Maturity Model (OPM3)

Staged organizational capability

A model for describing how consistently an organization applies project management. The volume discusses a five-level progression from ad hoc practices, through emerging standards and organization-wide processes, to consistent management and continuous improvement. A maturity model can help identify areas for development, but a score alone does not establish that projects deliver meaningful benefits.

Waterfall

Sequential project planning

A project approach that organizes work into ordered phases, with later stages generally depending on earlier ones. It emphasizes defining requirements and planning before implementation, along with documentation and controls. This can suit work with stable requirements and important dependencies, but frequent changes may be difficult to absorb and upfront estimates can prove wrong.

Agile

Iterative, feedback-led work

A project philosophy that expects requirements to change and organizes delivery into shorter cycles with frequent collaboration and feedback. Rather than specifying every detail at the outset, teams deliver workable increments and use responses to guide subsequent work. The approach is useful amid uncertainty, but frequent revisions and stakeholder involvement can consume time and frustrate teams.

Scrum

Structured iterative teamwork

A framework associated with Agile that organizes work into short cycles called sprints. Teams select a bounded set of tasks, coordinate through brief recurring meetings, review completed work with stakeholders, and reflect on how their process could improve. The ScrumMaster facilitates the process and helps address obstacles, while a product owner represents priorities for the product or service.

Project management office (PMO)

Shared project support function

A function, staffed by an individual or team, that develops and supports project management practices across an organization. A PMO may help with intake, planning, communication, training, documentation, and coordination across projects. The Hesburgh Libraries case describes a virtual PMO, whose members remain connected to home units rather than forming a separate office on the organizational chart.

Stakeholder register

Map of project interests

A project manager's record of people or groups who affect, or are affected by, a project. It can note their roles, expectations, influence, and likely response to the work, helping the manager plan engagement and communication. Because such an assessment may contain sensitive judgments, the volume advises against sharing it indiscriminately.

Responsibility Assignment Matrix (RAM)

Tasks linked to people

A grid connecting project activities or work packages to the people assigned to them. A RACI chart is one version: it distinguishes who is responsible for doing work, who is accountable for its completion, who should be consulted, and who should be informed. The matrix clarifies expectations, exposes unassigned work, and can help teams coordinate without direct reporting authority.

Project portfolio management

Strategic project selection

The practice of evaluating a group of projects together to align work with organizational strategy and available resources. It considers the value and balance of initiatives, the number of projects teams can handle, dependencies, and opportunity costs. Unlike managing an individual project, portfolio management asks whether the organization is undertaking the right overall set of work.

Digital content hub

Shared digital collection access

A centralized digital environment, such as a digital archive or repository, that brings distinctive collections together for discovery and use. The concept shifts archives and special collections away from isolated service structures toward collaboration across curatorial, technical, metadata, and preservation teams. A hub must support not only publication and access, but also interoperability and continuing stewardship.

More Product, Less Process (MPLP)

Practical archival processing

An archival approach that adjusts the level of arrangement and description to a collection's needs and available resources. Rather than applying intensive processing uniformly, archivists aim for sufficient organization and description to make more materials usable and reduce backlogs. The approach encourages user-centered prioritization while retaining professional judgment about care, context, and access.

Download PDF

To save this Project Management in the Library Workplace summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.32 MB     Pages: 16

Download EPUB

To read this Project Management in the Library Workplace summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.38 MB     Pages: 21
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...