The reference desk has always fielded odd questions. Lately one has become routine: a nephew, a boss, or a doctor mentioned a chatbot, and now someone wants to know what it actually is. Public libraries have answered the way they usually answer unfamiliar technology — by putting a free class on the calendar and hoping people show up. They show up.
Why libraries ended up teaching this
Three forces converged. Libraries already run digital literacy programs: email basics, spreadsheets, video calls, spotting phone scams. Their staff are practiced at explaining technology to people who are nervous about it, and they are patient in a way that a YouTube tutorial is not. The room, the wifi, and the coffee are already paid for.
The alternatives are thin. Corporate training serves people whose employers cover it. Online courses often assume vocabulary the average person does not have yet. Paid workshops cost money, sometimes a lot of it, before you know whether the topic is even for you. A library class asks nothing but an hour of your time, and nobody is selling anything at the end.
One caveat worth stating up front: most instructors are librarians and volunteers, not researchers. Many learned alongside their patrons. For a first exposure, that is usually an advantage — they remember what it felt like not to know.
What a typical session covers
Most run 60 to 90 minutes with a mixed-age group, a projector, and a handful of loaner laptops. The good ones are hands-on within the first ten minutes. Recurring topics include:
- What these tools are and what they are not — pattern matching over enormous amounts of text, not thinking, not searching the live web unless told to
- Writing a request: give context, name the format you want, ask for a revision rather than starting over
- Everyday tasks: drafting a letter to a landlord, summarizing a dense form, planning meals from what is already in the fridge, cleaning up a paragraph before sending it
- Where the tools fail: confident wrong answers, outdated details, invented citations, and numbers that look precise and are not
- Privacy: what not to paste in — medical records, account numbers, other people's personal information
- Scams that now arrive in flawless English, and the old rule that still applies: verify through a phone number you looked up yourself
A workshop is not an endorsement. The better ones make that explicit, because a class that only demonstrates neat tricks leaves people unprepared for the first time the tool is wrong.
Finding a class near you
Searching the library homepage rarely works, since the class may not be on it. Try these in order:
- Open the events calendar, not the front page. Look under terms like "technology," "digital literacy," "computer class," or "intro to" — the naming varies by branch.
- Call the reference desk and ask a person: "Do you have anything on chatbots or these new writing tools?" Front-desk staff often know about sessions that never made it online.
- Check individual branches. Larger systems frequently pilot a program at one location before spreading it.
- Look at the building's neighbors. Community colleges, senior centers, workforce offices, and job-training nonprofits run similar sessions, often with library co-sponsorship.
- Ask about format. Drop-in sessions are forgiving; registered ones fill fast; a one-on-one appointment with a librarian can be better if you have a specific question.
If you belong to a group — a retirees' club, a church committee, a small business association — ask whether a librarian will come to you. Outreach is part of the job, and a scheduled audience is easier for them to say yes to.
Starting one at your own branch
If nothing exists locally, the gap is smaller than it looks. Approach the adult services or programming librarian with something concrete rather than a vague offer to help.
The pitch that tends to work
Propose a single 90-minute session for 10 to 20 people, bring your own device, no jargon. Hand over a one-page outline, two dates you are free, and a clear statement of what you will handle: the teaching, the setup, the take-home handout. Small and specific beats ambitious and hypothetical, because staff time is genuinely tight.
Keep it alive past the first meeting
Repeat it monthly rather than annually; momentum is easy to lose. Keep groups small enough that questions get answered. Pair a technically confident volunteer with a patient one, and let the patient one do most of the talking. Rotate topics so regulars have a reason to return, and end every session by asking what people want next time. Funding is rarely the obstacle — a Friends of the Library group, a community foundation mini-grant, or a local workforce board can cover printing and a few refurbished laptops, since the room and the internet are already there.
Where skepticism belongs
The most useful hour you can spend is not learning prompts. It is learning limits. A tool that cannot show you where a claim came from deserves to be treated as a first draft, not a final answer, and never as the only source for a decision that matters.
That applies with force to legal, medical, and financial questions. A model can summarize what a document says. It cannot tell you what to do about your situation, and it should not be trusted with a dosage, a deadline, or a contract term. Run anything consequential past a qualified professional — an accountant, a lawyer, a clinician — before you act on it.
Before you go: a short checklist
- Bring the device you actually use, plus the charger. Learning on unfamiliar hardware doubles the difficulty.
- Write down one real task you want help with before you arrive — a letter, a form, a recipe plan. Concrete beats hypothetical.
- Ask two questions out loud. Chances are three other people had the same one.
- Take the handout home and try one exercise within a week, while it is fresh.
- If the class was useful, tell the branch. Feedback like that is what keeps a program funded and on the calendar.
The classes are free, they are usually small, and nobody will ask you what you already know. That last part is the whole point. Check your branch's calendar this week — and if the answer is nothing yet, you now have everything you need to change it.
