Community First, Institution Later

This post is part of a series that reclaims community-centered librarianship from its institutional distortions, returning it to its roots in struggle, mutual aid, and collective survival. It treats libraries not as neutral services but as contested infrastructures shaped by power, resistance, and memory, and explores librarianship as solidarity work grounded in real communities, real conflicts, and the ongoing tension between institutional control and collective autonomy. Check all the posts in this section's index.

The Limits of Community Input

In contemporary library discourse, community participation is often presented as evidence of institutional openness. Libraries consult residents, organize surveys, invite feedback, create advisory groups, and adjust programs according to expressed needs. These practices may be useful. They can correct assumptions, reveal unmet demands, and prevent some forms of institutional blindness.

But community input is not the same as community authority.

Input allows communities to speak within a structure already defined by the institution. Authority allows communities to shape the structure itself. The difference is not rhetorical. It determines where power is located, how decisions are made, which forms of knowledge become operational, and who has the capacity to define the purpose of the library.

A library may collect opinions from the community while retaining full control over budgets, priorities, access rules, descriptive practices, staffing models, evaluation criteria, and public representation. In such cases, participation functions as consultation. It may modify decisions, but it does not transform the conditions under which decisions are produced.

Community-centered librarianship requires a different starting point. The central question is not how institutions can incorporate community voices into existing workflows, but how library work changes when community-defined priorities become the first source of legitimacy.

From Institutional Design to Community Mandate

Most libraries are designed institutionally before they are opened socially. Their legal status, administrative structure, funding lines, service categories, professional roles, spatial arrangements, cataloging procedures, and evaluation requirements are usually defined before sustained community participation begins.

Communities are then invited to use, respond to, or help improve a system whose basic assumptions have already been established.

Community-first librarianship reverses this order. It begins from a community mandate.

A community mandate is not a vague expression of local preference. It is the set of collectively defined purposes, limits, responsibilities, and authorizations that guide what the library is allowed to do in relation to the people it serves. It concerns not only services, but also authority, risk, memory, language, representation, and accountability.

Such a mandate may define what the library should protect, what it should circulate, what it should refuse to document, what forms of naming it should use, what materials require restricted access, what kinds of institutional partnership are acceptable, and what forms of public visibility may place the community at risk.

This shifts the role of the institution. It no longer appears as the origin of the project, with the community added later as participant or beneficiary. Instead, the institution becomes a secondary structure: a provider of resources, technical capacity, legal support, infrastructure, and continuity. Its function is to sustain the mandate, not to replace it.

Governance Is Not a Meeting

The language of community governance can be misleading. Assemblies, councils, committees, advisory boards, and working groups do not automatically produce community authority. Their political significance depends on what they can actually decide.

A resident council without control over priorities is consultation. An assembly without influence over budgets is symbolic. A committee that can recommend but not determine workflows remains subordinate to the institution. A participatory structure that can be ignored when inconvenient is not governance. It is procedural decoration.

Governance exists where binding decisions are made.

In a community-centered library, governance must therefore be examined through concrete questions. Who decides what enters the collection? Who determines how materials are described? Who defines sensitive information? Who decides when access should be open, restricted, delayed, or refused? Who evaluates whether the library is fulfilling its purpose? Who can challenge staff decisions? Who can revise policies? Who can say no?

Without authority over these questions, community participation remains limited to the surface of library work.

This does not mean that every decision must be made by a general assembly, or that every operational task must be collectively debated. Governance requires structure. It may involve delegated responsibilities, rotating roles, technical committees, thematic groups, or forms of representation. But those structures must remain accountable to the community mandate. Otherwise, they reproduce the same hierarchy under participatory language.

Community-Defined Workflows

If community authority is taken seriously, it cannot remain confined to mission statements or advisory processes. It must enter the ordinary workflows through which libraries operate.

Collection development is one example. In institutional models, selection often follows professional criteria such as relevance, balance, demand, quality, preservation value, or alignment with policy. In community-first practice, these criteria cannot be assumed in advance. The community may define relevance differently. It may prioritize materials connected to local struggles, practical survival, language recovery, territorial memory, legal defense, cultural continuity, or intergenerational transmission.

The same applies to description. Community-defined cataloging is not simply the addition of local terms to an existing vocabulary. It involves asking which names, categories, relations, and silences should structure access. Some materials may need to be described through local concepts rather than professional taxonomies. Some may require multiple names, contested names, historical names, or names that change according to context. Some may require description that records uncertainty rather than forcing standardization.

Access also changes. The institutional preference for openness cannot be treated as an absolute principle. Communities may have reasons to restrict certain materials, delay their circulation, protect names, limit reproduction, or prevent extraction. Open access is not automatically just access. In some situations, unrestricted visibility can expose people, practices, territories, or memories to harm.

Programming must also be rethought. A community-first library does not begin by asking what activities will attract users, increase attendance, or satisfy funders. It asks what forms of collective work are needed. This may include reading groups, legal information sessions, language circles, documentation workshops, labor rights meetings, memory projects, tenant organizing, digital literacy, environmental monitoring, or quiet forms of mutual support. The value of these activities cannot be measured only through attendance or visibility.

Evaluation is equally affected. Institutional metrics tend to count circulation, visits, participants, events, partnerships, digital engagement, and user satisfaction. These measures may provide useful information, but they cannot determine the meaning of community-centered work. A library may be successful because it protected a vulnerable archive, helped a group understand a legal process, preserved a language practice, created a safe channel for testimony, or refused an extractive partnership. Some of its most important effects may be difficult to count.

Community-defined workflows require libraries to move from service logic to responsibility logic. The issue is not only what the library provides, but to whom it is accountable for the consequences of its work.

Professional Expertise After Community Authority

Putting community first does not mean eliminating professional expertise. It means changing its position.

Librarians, archivists, and information workers possess technical knowledge that can be indispensable. They understand systems of description, preservation, access, metadata, privacy, documentation, collection management, copyright, institutional procedure, digital infrastructure, and public service. These capacities matter.

The problem begins when professional expertise becomes the highest authority.

In community-first practice, professional knowledge should clarify possibilities, risks, and constraints. It should not determine the community's priorities in its place. The librarian can explain the consequences of different cataloging choices, the risks of public access, the limits of a preservation format, the implications of a partnership, or the vulnerabilities of a digital platform. But the final orientation of the work must remain accountable to the community mandate.

This repositioning also protects librarianship from false neutrality. The librarian is not a passive technician applying universal standards. Nor is the librarian a heroic substitute for collective decision-making. The librarian becomes a situated professional whose task is to support the community's capacity to govern its own knowledge infrastructures.

This role requires honesty. Librarians must be able to say what institutions can and cannot do. They must explain constraints without turning those constraints into unquestionable laws. They must distinguish between legal requirements, institutional habits, professional preferences, and genuine risks. They must also be prepared to recognize when professional norms conflict with community priorities.

Expertise, in this context, becomes a form of service to collective authority, not a claim to govern it.

The Community Is Not a Single Voice

A serious community-first approach cannot romanticize the community.

Communities are not homogeneous moral subjects. They contain conflicts, inequalities, histories of exclusion, internal hierarchies, generational tensions, gendered violence, political divisions, religious authority, local elites, recent arrivals, displaced people, and people whose presence may be tolerated but not fully recognized. Some voices are louder because they already hold authority. Some forms of silence are produced by fear.

For that reason, "community-led" cannot simply mean following whoever speaks most publicly in the name of the community. The question of representation must remain open and contested.

Who is recognized as a legitimate speaker? Who is absent from meetings? Who cannot attend because of work, caregiving, mobility, documentation status, language, disability, fear, or mistrust? Who benefits from being treated as representative? Who is placed at risk when materials become visible? Who has the power to define tradition, memory, or identity? Who is expected to forgive, forget, or remain silent for the sake of collective unity?

A community-centered library must create mechanisms for dealing with these tensions. This may involve multiple forms of consultation, protected channels for dissent, separate spaces for vulnerable groups, rotating representation, transparent decision records, conflict protocols, and periodic revision of mandates. It may also require recognizing that some decisions cannot be made quickly or publicly.

Community first does not mean majority rule without safeguards. It means building forms of authority capable of recognizing internal difference, unequal risk, and contested memory.

Institution Later Does Not Mean Institution Never

To say "community first, institution later" is not to deny the importance of institutions. Libraries require material conditions. Buildings must be maintained. Workers must be paid. Collections must be preserved. Digital systems must function. Legal obligations must be understood. Public resources must be administered. Long-term continuity often depends on structures that exceed voluntary labor.

The issue is not whether institutions should exist. The issue is where legitimacy begins.

An institution can support a community-centered library by providing infrastructure without monopolizing authority. It can offer funding without defining the agenda. It can provide professional staff without replacing community decision-making. It can help preserve materials without claiming ownership over memory. It can create access systems without forcing all knowledge into institutional categories. It can negotiate with external actors while remaining accountable to those whose knowledge, labor, and histories are at stake.

This requires restraint. Institutions are accustomed to converting support into control. They often translate community projects into strategic objectives, measurable outputs, branding opportunities, grant language, or evidence of inclusion. Even when well-intentioned, this translation can alter the meaning of the work.

Community-first librarianship therefore requires institutional self-limitation. The institution must learn to act as a secondary structure. It must sustain conditions rather than occupy the center. It must accept that some decisions will not be optimized for administrative convenience, visibility, or external recognition.

A Different Order of Design

The transformation proposed here is not cosmetic. It does not consist of adding participatory language to existing models, nor of inviting communities into institutional processes after the central decisions have already been made.

It requires a different order of design. First, the community mandate. Then, governance structures accountable to that mandate. Then, workflows built from community-defined priorities. Then, professional expertise positioned in support of collective authority. Then, institutional resources organized around those decisions.

This order matters because power often hides in sequence. Whoever defines the first terms usually shapes what becomes possible later. If the institution begins by establishing categories, policies, services, metrics, and roles, community participation will occur inside that frame. If the community begins by defining purpose, risk, authority, and accountability, the institution enters a different field of responsibility.

Community-centered librarianship, in this sense, is not simply a more responsive form of library service. It is a reorganization of legitimacy. It asks libraries to stop treating communities as users of institutional generosity and to recognize them as authors of their own knowledge infrastructures.

The institution may still matter. It may be necessary. It may provide tools, protection, continuity, and resources.

But it should arrive later. Not as owner of the frame, but as one element within a structure whose authority begins elsewhere.