© Copyright 2026 Mastersinlibraryscience.org.
Practical steps for inclusive async facilitation, title picks, and librarian learning.
Librarian professional development often assumes that staff can gather at the same time, but a children's librarian working two evening programs and a Saturday rotation cannot easily join a Tuesday noon discussion. An asynchronous virtual book club treats that scheduling reality as the core design constraint, not a compromise. Platform accessibility, title mapping to library science specializations and DEI goals, threaded prompts, and continuing education documentation all need to function when participants respond at 6 a.m. or 11 p.m. The shift does more than fit calendars; it broadens whose voices shape the conversation. That is especially relevant in libraries where staff working different hours serve the same multilingual and neurodiverse community.
Asynchronous book clubs are the most practical professional development format for librarians in modern librarian roles because they treat staff schedules as a design constraint, not an afterthought.
A mandatory live virtual book club usually works for staff with predictable desk coverage, but it quietly excludes the colleagues who keep the building running. Frontline circulation staff, youth services librarians, school librarians, and part-time workers often cannot leave their posts for a fixed afternoon video call. The same is true for staff covering evenings and weekends, branches with lean staffing, and solo school librarians who spend most of the day with students. It is not a matter of interest; it is a matter of coverage. When attendance is the default measure of engagement, those employees are marked absent even when they are ready to read and reflect. An asynchronous model replaces that gatekeeping with a simple principle: participation should fit the schedule, not the other way around.
Librarian burnout is real, and time poverty is one of its main drivers. Staff who already balance desk hours, programming, instruction, collection maintenance, and committee work may experience another live meeting as a burden rather than a benefit. Asynchronous participation removes the commute to a video call, the pressure to look engaged on camera, and the scramble to arrange coverage. It also opens the door for caregivers, night and weekend staff, commuters, and colleagues in different time zones. Treating flexibility as an equity issue acknowledges that professional growth should not depend on who can get away from a service desk at noon or who has the energy for another scheduled event after an eight-hour shift.
The same asynchronous structure supports public, academic, and school library teams. Public library staff can discuss community engagement, censorship, and inclusive programming. Academic librarians can examine MLIS information literacy, open access, or scholarly communication. School librarians can explore collection development for diverse classrooms, reader's advisory, or digital citizenship. Because the conversation lives in writing, participants can bring examples from their own branches, campuses, or districts and return to earlier posts as their thinking develops. This creates a shared professional vocabulary without requiring everyone to be in the same room at the same time.
Asynchronous does not mean unstructured. A clear reading window, weekly discussion prompts, facilitator check-ins, and a closing synthesis post give the club shape. Without those scaffolds, participation fades silently. With them, the club becomes a low-pressure but serious professional learning space that respects both the group's goals and each person's time. Facilitation still matters, but it takes the form of thoughtful prompts and regular response rather than hosting a live event.
Not every collaboration tool is built with library values in mind. The platform you choose for an asynchronous book club shapes who can participate, how safe their data remains, and whether the experience meets institutional compliance requirements. The table below compares six commonly considered platforms across privacy fit, accessibility, and ideal use cases so you can match the right tool to your library context.
| Platform | Privacy and Policy Fit | Accessibility Features | Best Use Case |
|---|---|---|---|
| Discord | Consumer social platform, not designed for library compliance. Libraries should use private channels for sensitive programs, minimize patron data collection, and leverage the platform's safety center. Not inherently aligned with FERPA or patron confidentiality standards. | Offers user-level Data and Privacy settings and per-context media controls for direct messages, friend messages, and server channels. No formal WCAG 2.2 AA conformance claim identified. | Informal adult programming or community discussion groups where the library can manage moderation and privacy carefully. Not recommended for student or minor cohorts. |
| Slack (Enterprise Grid) | Enterprise Grid allows institutions to enforce organization-wide security and administrative policies while segmenting workspaces by department or program. Stronger institutional control than consumer-tier plans. | No published WCAG conformance statement identified in available documentation. Screen reader and keyboard navigation support may vary. | Institution-managed book clubs where centralized security, compliance oversight, and segmented workspaces matter more than public community discovery. |
| Microsoft Teams (Education) | Supports public or private group settings through Teams privacy controls and Microsoft 365 Groups. Education tier is accessed with school credentials, and administrators can disable student chat, private meeting scheduling, and other features to strengthen student safety. | School-managed platform with admin-controlled restrictions. No standalone WCAG 2.2 AA conformance statement identified in reviewed sources, though Microsoft publishes broader accessibility documentation elsewhere. | School or district book clubs that need admin-controlled chat, meeting, and app restrictions for student safety. Strong fit when FERPA compliance is required and the institution already uses Microsoft 365. |
| LibGuides | Content published through LibGuides falls under the institution's own accessibility and compliance obligations. Federally funded institutions must ensure electronic resources are accessible. Not a discussion platform, so patron interaction data is minimal. | Can host accessibility-focused pages and link to disability services or related supports. Accessibility of the content depends on the creator following best practices (alt text, heading structure, color contrast). | Best as a low-friction hub for book club schedules, reading lists, discussion prompts, and accessibility resource links. Pair with a separate discussion tool rather than using LibGuides alone. |
| Canvas (LMS) | Discussion content entered by students is treated as an education record under FERPA, meaning posts must be protected from unauthorized disclosure. Teachers should not post student work publicly without consent or an opt-out option. | States conformance with the W3C Web Accessibility Initiative and Section 508 standards, making it one of the stronger options for WCAG 2.2 AA alignment among the platforms listed here. | School-based asynchronous book clubs where FERPA-aware, authenticated discussion inside a learning management system is needed. Ideal when participation may count toward coursework or continuing education credit. |
| Moodle (LMS) | States that it does not sell user data and provides privacy-contact channels for institutional review. Offers deletion procedures for children's personal data when applicable. Supports institutional control over data handling. | No published WCAG 2.2 AA conformance claim identified in available documentation. Accessibility depends partly on the institution's theme and configuration choices. | School or library-hosted book clubs that follow a course-like workflow and prioritize privacy-oriented data handling. Good open-source alternative when Canvas licensing is not available. |
| Goodreads | Consumer reading-social platform with a standard privacy notice but no library-controlled environment. Libraries have limited oversight over user identities and social activity. Not suitable where patron confidentiality or FERPA protections apply. | No published WCAG conformance statement or accessibility feature documentation identified in reviewed sources. | Public-facing reading discovery and informal book discussion among adults. Not appropriate for privacy-sensitive library cohorts, student groups, or any setting where patron data protection is a priority. |
Choosing titles for a librarian book club is most effective when selections map to specific professional competencies rather than personal reading preferences. The framework below organizes real reading programs and title clusters by competency area, explains the professional growth connection, and identifies which library setting benefits most. Use it as a starting point to build a reading list that balances DEI, pedagogy, management, and community engagement across your team's development goals.
| Competency Area | Example Titles or Programs | Why It Works | Best Setting |
|---|---|---|---|
| DEI and Anti-Racism | Integrating DEI in Public Library Book Clubs (reading list model documented in the Journal of New Librarianship) | Public libraries have used anti-racist book clubs to address and discuss pressing issues of social and systemic inequity, making this a strong starting point for any staff equity initiative. | Public library staff professional development or community-facing discussion |
| Social Justice and Equity | Equity on the Ground: Promoting Social Justice in a Library Staff Reading Group (documented by Taylor and Francis Online) | The project aimed to increase library workers' awareness of barriers through discussion and actionable ideas for creating an inclusive environment for both staff and patrons. | Staff professional development in any library type |
| Inclusive Leadership and Management | Inclusive Leadership in Academic Libraries (American Library Association resource) | A diversity book club for staff and leaders can help explore different perspectives, build culturally humble practices, and raise staff awareness about inequalities in institutional structures. | Academic library staff development |
| Critical Practice and LIS Scholarship | Critical Practice Reading Group (Michigan State University Libraries) | The group discusses readings about power structures, privilege, and social dynamics in library work, connecting LIS scholarship directly to everyday professional decisions. | Academic library staff development |
| Community Engagement and Pedagogy | Staff Reads, Community Reads, and Recommended Reads for Equity (University of Washington Libraries) | These programs use shared reading to break down silos, discuss racism, ableism, mental health, and other equity issues, and connect discussion to actionable everyday practice. | Academic library community engagement programming |
| Anti-Oppression and Facilitation Skills | Anti-Oppression Book Club (Archer Library, University of Regina) | The club adjusts discussion ground rules to meet DEI needs and supports respectful exchange across diverse views, offering a practical model for facilitation in polarized contexts. | Academic library staff and campus community engagement |
| School Library Leadership, Literacy, and Cultural Responsiveness | Libraries Transform: School Librarian PSEL Competencies (American Library Association) | The school library competency framework emphasizes equity and cultural responsiveness, community of care, professional community, and literacy, which aligns well with professional reading groups focused on pedagogy. | School library staff professional development |
Structuring an asynchronous discussion means giving the conversation a predictable rhythm: a prompt opens each week, replies live in threads, and everyone knows the due-by time. A four-to-six week arc is long enough to build trust without dragging.
One common pattern is to post the week's prompt on Wednesday, ask for an initial response by Friday midday, and set two peer replies by Sunday evening. That leaves Monday and Tuesday for the facilitator to summarize and set up the next thread. Week 1 can focus on introductions and shared norms. Weeks 2 and 3 work through scenario-based prompts tied to real library operations, such as a patron interaction, an instruction issue, or a policy conflict. Two reliable prompt structures to rotate in are compare-and-justify (which approach holds up better?) and equity-and-access (who benefits, who is burdened, who is excluded?).1 Week 4 invites participants to compare two approaches and name the trade-offs. Week 5 or 6 closes with a synthesis prompt: what would you change in your own practice? Adjust the days to your team's schedule, but keep the same shape so people can plan around it.
A pair or small team prevents one librarian from carrying the whole book club. Rotate roles weekly or per title: one co-facilitator posts the prompt and writes the midweek summary, while the other watches threads, asks follow-ups, and redirects side conversations. If you are co-facilitating for the first time, train together before launch. Facilitation guides such as Techniques for Facilitating Online Asynchronous Learning Activities commonly suggest a preparatory call three to four weeks out and a platform walk-through one to two weeks out. Use that time to agree on tone, norms, and how quickly to step in when a thread becomes tense.
In text-based discussion, visible moderation keeps threads from sprawling. After a burst of replies, post a short summary of agreements and unresolved points, then restate the next prompt. Ask a follow-up that invites another participant to contribute rather than answering every question yourself. Early on, say plainly that reading without posting counts as participation.1 Some colleagues contribute best by observing, and that is legitimate. If a thread derails or turns personal, summarize the productive points, restate the boundaries, and move off-topic or emotional side conversations to a separate forum. Setting those expectations in week 1, with a short posted protocol, makes later moderation feel like a reminder rather than a reprimand.2
Inclusive facilitation succeeds only when the default rules make full participation safer for people with different roles, schedules, and access needs.
At the start, let the group name assumptions and set expectations before the first title is assigned. Ask members to agree on how to question an idea without attacking a person, and create an explicit path for circling back when harm occurs.1 A norm like "assume good intent, but own impact" is less useful than a concrete agreement: if a comment feels harmful, members can pause the thread, rephrase, or message a co-facilitator without being questioned in front of peers. Put these norms in plain text and in the platform where everyone can find them.
Treat chosen names, pronouns, and accessible reading formats as defaults, not accommodations. Invite members to share pronouns and display names in their profile or first post, but never require disclosure. For every reading or prompt, provide a version that works with screen readers: machine-readable text, tagged PDFs, captioned video with speaker identification, and alt text for meaningful images. Avoid images of text unless the same text appears in the post or an accessible version. Structure thread titles and replies with clear labels so screen readers can move through discussions. WCAG 2.2 AA is a useful baseline.2 Check color contrast, keyboard-only operation, and focus visibility before launch, especially if your platform uses sticky headers or drag-and-drop tools. If any live video option is offered, pair it with real-time captions.
In many libraries, credentialed librarians speak first and paraprofessionals, part-time staff, and non-MLS colleagues defer in library community roles. Facilitation should interrupt that pattern deliberately. Rotate who writes the opening prompt, ask direct questions to quieter staff members through multiple modes rather than putting anyone on the spot, and avoid treating the master of library science degree as the only source of valid interpretation. Small discussion threads can help, but only when moderators watch for dominant voices that might otherwise migrate into the smaller space.
Invite perspectives from staff and community members with lived experience, but do not appoint someone to speak for an entire group. Offer optional prompts such as "share a moment when the text changed your thinking" and let people self-select.3 When a pattern from an underrepresented group emerges, reflect it back with context rather than requiring an individual to explain. Facilitators can lift up patterns without naming who raised them, which reduces pressure on any single person. This keeps the conversation centered on information services to diverse populations without turning a colleague into an unpaid educator.
Inclusion is not a checklist you complete once. It is a practice you return to every week, in every prompt, every reply, and every silence you choose to notice.
Turning a professional book club into a recognized continuing education activity requires deliberate documentation, structured assessment, and a clear understanding of your state's rules. The guidance below will help you build a book club framework that can withstand the scrutiny of a certifying body.
Whether a structured reading group qualifies for CE credit depends entirely on where you hold certification. Requirements vary sharply from state to state, and no national standard exists. The American Library Association defines staff development broadly as job-related continuing education but does not maintain approval criteria specific to book clubs.2
A few examples illustrate the range:
Because some states flatly exclude book clubs while others may accept them with documentation, verify the current requirements with your state library association or certifying body before building a CE claim around your reading group.
If your state allows pre-approved professional reading activities, structure documentation the way you would for a formal workshop:
Note that some states use credit-by-time formulas. Nebraska, for instance, awards 0.5 credits for activities lasting 20 to 44 minutes and 1.0 credit for 45 to 89 minutes. Reading and summarizing an article earns 0.5 credits.1 If your state uses a similar model, align your discussion schedule to recognized time blocks and log hours accordingly.
Certifying bodies are more likely to recognize participation when you can show measurable outcomes. Consider pairing your book club with one or more of these approaches:
No single accepted assessment model exists across states, so frame your approach around the documentation standards your certifying body already uses. A well-structured book club that mirrors workshop-level rigor stands the best chance of earning credit where policies leave room for pre-approval.
How does the same asynchronous book club need to change when the participants are public, academic, or school librarians rather than one mixed reading group? The core structure stays stable, but platform fit, title focus, and facilitation rhythms shift with each work setting. Published examples are strongest for public and professional library groups; academic and school teams can apply the same design with the constraints below.
Public librarians often navigate desk shifts, nights, and weekends, so live attendance quickly becomes a barrier. Chicago Public Library's Humboldt Park Branch runs a virtual club where readers pick up a monthly selection and comment on Goodreads at their own pace.1 For staff, that same low-barrier setup works with curated monthly titles.2 - Typical setup: Goodreads or a private discussion board; monthly titles and asynchronous posting. - Pros: Low-cost, familiar to readers, easy to check during desk downtime. - Cons: Public visibility can blur patron-facing and internal staff discussion, so a private group is usually necessary. - Facilitation tweak: Where negotiated or union-supported professional time is available, offer an optional shared workday window; keep the thread open for evening and weekend staff.
Academic library staff follow semester rhythms, not weekly meeting habits. Library Journal's cloud-based model pairing unlimited-access ebook titles with virtual author conversations suggests a campus-friendly design: license a simultaneous-use title, then run asynchronous prompts ahead of an optional synchronous author event.2 - Typical setup: Campus learning management system, Teams, or Slack channel; a semester arc with short practical chapters. - Pros: Existing logins, privacy, and familiar tools; the async thread works around instruction and desk schedules. - Cons: Midterms, finals, and summer staffing can stall momentum if the timeline is not planned around the calendar. - Facilitation tweak: Anchor prompts to the semester and pause during finals; rotate prompt posters across liaison or functional teams.
Fully documented school-team case studies are thinner, but examples point toward practical professional reading. A School Library Connection asynchronous book club noted that brief chapters, reflection questions, charts, and resources suited the format because scheduling conflicts made weekly meetings impractical.4 AASL's 2026 Page to Practice Book Club is described as a flexible, asynchronous space and a relaxed "slow chat" on LinkedIn.3 - Typical setup: Private LinkedIn group or district collaboration tool; practical PD titles with chapter-based reflection. - Pros: Staff can read during planning periods or evenings, and short reflection prompts connect quickly to library practice. - Cons: Not every staff member wants to use LinkedIn for work, and school filters may block some platforms. - Facilitation tweak: Ask one volunteer to post a short "try this in the library" response per chapter, then invite others to add what worked or what they changed.
Across settings, the shared adjustment is to treat participation as ongoing contribution, not attendance at a single live event.
