{"id":88,"date":"2026-04-24T17:17:09","date_gmt":"2026-04-24T21:17:09","guid":{"rendered":"https:\/\/laurenpressley.com\/library\/?p=88"},"modified":"2026-04-24T17:28:39","modified_gmt":"2026-04-24T21:28:39","slug":"epistemic-labor-at-scale-access-services-as-practitioners-of-precision-presence-and-partnership","status":"publish","type":"post","link":"https:\/\/laurenpressley.com\/library\/2026\/04\/24\/epistemic-labor-at-scale-access-services-as-practitioners-of-precision-presence-and-partnership\/","title":{"rendered":"Epistemic Labor at Scale: Access Services as Practitioners of Precision, Presence, and Partnership"},"content":{"rendered":"\n

I’ve been thinking about the individual experience of students who become scholars through repeated acts of recognition<\/a>, and the necessity of scale. I’ve had the good fortune to have the experience of working in places that can be very high touch and in institutions where you have to start with scale first and find ways to come back to individual relationships. My experience shows there are things we all can learn from organizations facing different approaches to the scale challenge. What is true at all of these institutions is that the answer is never exceptional staff members or individual priorities, but rather the architecture of our approach. The infrastructure of belonging is based in how public services is organized, trained, and philosophically oriented. When I spoke at the 2025 Access Services conference<\/a> my keynote was titled The Foundational Leadership of Access Services: How Service Builds Institutional Possibility<\/a> and we reframed the precision, presence, and partnership that public services offer as acts of leadership, and today I am also thinking of them as epistemic practices.<\/p>\n\n\n\n

The vocabulary problem: “support” obscures what’s actually happening<\/h4>\n\n\n\n

Public and Access Services work is often framed as support. As someone who started her career in this type of work, I don’t think most people were thinking of it as “supporting cast” but rather “critical support.” And yet I know that words matter and the work “support” is a word that can easily place these roles outside of the epistemic function they actually enable. Support can be seen as peripheral, supplementary, downstream. Infrastructure is load-bearing. The distinction matters institutionally because what you call something shapes what you’re willing to invest in, who you think can lead it, and how you measure its value. When I was thinking about the frame “warehouse versus infrastructure<\/a>,” this is the way it can show up when talking with people who don’t understand the role of libraries in 2026. They’re busy thinking of books, gate counts, and the library as a place that takes resources and stores things. Anyone actually working in a library knows we’re enabling the work of learning and knowledge production. Yes, that is done through collections and useful spaces, but it’s also the consultations, services, collaborative environments that we create and a cultural position of valuing and amplifying our institutions’ scholarly contributions. The work that contributes to these, as the work of access services, is not support but strategic infrastructure.<\/p>\n\n\n\n

Precision as epistemic practice<\/h4>\n\n\n\n

Precision in public services means knowing enough about what a patron actually needs (as distinct from what they asked for) to respond usefully. That’s not customer service; it’s a form of situated knowledge-making. The public services professional who anticipates the need behind the request, who knows the difference between a student who is lost in a database and a student who is lost in the institution, is doing interpretive work with real epistemic stakes. Library science programs teach the craft of the reference interview, a framework for understanding this interpretive work. Many access services staff have developed the same capacity through sustained attention to the people in front of them, arriving at the practice without the vocabulary for it. The work is the same; the paths to it are different. When this work happens in access services, staff document procedures, preserve institutional memory, and build systems that help others know what the answers are (and maybe even where they came from and why). This is Haraway’s situated knowledge in organizational form.<\/p>\n\n\n\n

Presence as epistemic practice<\/h4>\n\n\n\n

Presence is the capacity to actually see what’s in front of you, to read uncertainty in real people rather than in abstracted queries. AI performs retrieval and synthesis, and it can be very good at this. It cannot perform presence in the way the work requires. It cannot notice that someone is overwhelmed rather than confused, or that the real question is different from the stated question, or that this moment calls for de-escalation rather than information. What access services professionals do when they read the room, as they adapt, calibrate, and respond to what is actually happening in front of them, is precisely the thing AI cannot do and performs as though it can. AI’s performed epistemic humility<\/a> responds with certainty. Even when it expresses doubt, it does so in a way that is overconfident. I routinely find myself getting a reasonable answer but knowing it’s wrong, reporting that it is, and getting an answer that says something to the effect of “oh, of course! now that I think of it…” but I only had the certainty to push back because of decades of thinking about the topics we’re exploring. Students, in particular, don’t have that intellectual scaffolding in place quite yet, it’s part of why they’re there! The human that is present with them can see hesitancy and read the situation to adapt in a way that is genuinely useful for learning.<\/p>\n\n\n\n

Partnership as epistemic practice<\/h4>\n\n\n\n

Partnership is the long-term orientation. It’s the understanding that creating a knower isn’t transactional but relational, and it happens across time and repeated contact. Pugh’s connective labor<\/a> has become a really important framework for me. It’s the idea that there is important work in seeing another person in their specificity and forging emotional understanding with others. This is the work of building relationships through which inquiry becomes possible, and is what I’ve been talking about in the last few posts. In my broader epistemological frame, partnership also means something institutional: the library is a core partner in the university’s knowledge mission, not an auxiliary to it.<\/p>\n\n\n\n

Precision, presence, and partnership happen all the time, in public services work. In every interaction, in observed interactions, in just the physical presence of a caring staff member this work impacts all students who pass through and use the library. The architecture of these service experiences is how this epistemic practice and leadership scale well beyond what one might otherwise expect. This work scales because of what surrounds each interaction: the hiring that selects for people who can read a room, the training that treats interpretive work as a competency, the documentation that lets one staff member’s insight become another’s starting point, the shared orientation that makes precision and presence feel like the job rather than extras added onto it.<\/p>\n\n\n\n

If precision, presence, and partnership are epistemic practices, they require investment of a different kind than service competencies do. You don’t evaluate epistemic labor the same way you evaluate service provision. You don’t staff it the same way. The answer is hiring, training, culture, documentation, institutional memory, and shared philosophical orientation. And the shifts necessary to prioritize the epistemic frame may run counter to the efficiency answers that most institutions have been pushing toward over time. Every investment is an exercise in prioritization, and when determining how to support developing scholars and belonging, this should be an area to consider.<\/p>\n\n\n\n

In my last post I was really thinking through what it means to create a knower. Today I’ve been thinking about the institutional infrastructure through which that creation happens not once but thousands of times, distributed across a function that has rarely been named in these terms in institutional leadership conversations. When universities ask what libraries do, access services is usually the last thing they think to examine; in reality it should be among the first.<\/p>\n\n\n\n

\n\n\n\n

This is a post in an ongoing project exploring libraries, knowledge, and the epistemic stakes of artificial intelligence. I\u2019m drawing on social epistemology, feminist theory, and two decades of practice in academic libraries.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

I’ve been thinking about the individual experience of students who become scholars through repeated acts of recognition, and the necessity of scale. I’ve had the good fortune to have the experience of working in places that can be very high touch and in institutions where you have to start with scale first and find ways […]<\/p>\n<\/a>","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[5],"tags":[48,46,6,45,10,50,49,51,52],"class_list":{"0":"post-88","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-libraries-ai","7":"tag-access-services","8":"tag-allison-pugh","9":"tag-artificial-intelligence","10":"tag-connective-labor","11":"tag-donna-haraway","12":"tag-keynote","13":"tag-public-services","14":"tag-scale","15":"tag-service","16":"h-entry","17":"hentry"},"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/posts\/88","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/comments?post=88"}],"version-history":[{"count":3,"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/posts\/88\/revisions"}],"predecessor-version":[{"id":92,"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/posts\/88\/revisions\/92"}],"wp:attachment":[{"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/media?parent=88"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/categories?post=88"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/laurenpressley.com\/library\/wp-json\/wp\/v2\/tags?post=88"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}