What libraries are doing
Public libraries across the country are quietly running workshops that teach people how to disable or avoid AI features in everyday devices and services. These sessions — practical, hands-on, low-cost — are spreading online and drawing attention not because they're flashy, but because they meet a real need: users want control. For more detail on the phenomenon, see the original coverage: TLDR Tech.
Why this matters
This isn't just a quaint local reaction to technology. It's a grassroots signal that default-on AI, framed as convenience, is colliding with people’s expectations about agency, privacy, and transparency. Libraries are trusted local information hubs; when librarians step in to help patrons opt out, it says something loud and clear about where trust currently sits.
My take — agencies over autopilot
I find the popularity of these workshops to be a clear, actionable message for product teams: many users want agency, not autopilot. Companies keep shipping AI as a presumed upgrade and tucking it behind vaguely worded consent screens or hard-to-find settings. That pattern treats AI adoption like a fait accompli instead of a choice. Forcing features risks eroding trust — especially among communities that rely on libraries for neutral, accessible tech assistance.
What product teams should actually do
If you build consumer-facing AI, stop assuming users will happily accept defaults. Ship clear, discoverable opt-outs. Provide simple, honest explanations of what the AI does, what data it uses, and how to reverse it. Invest in consent-first controls and user education — not just glossed-over privacy policies or buried toggles that only savvy users can find. The reputational calculus matters: a frustrated community of non-experts will influence broader perception far more effectively than a targeted marketing campaign.
Beyond the UX: a reputational and civic angle
Libraries offering these workshops is emblematic of something wider: when institutions trusted by communities step into the gap left by product teams, the company loses narrative control. That's not merely a design failure; it's a civic one. Companies that want broad, durable adoption need to earn it through transparency and consent, or risk being sidelined by community-driven alternatives and grassroots tech literacy efforts.
Closing thought
The spread of these library sessions is not a footnote — it's a roadmap. It tells product builders where to focus: clearer opt-outs, better explanations, and real investment in user agency. Do that, and adoption will follow on its own terms. Ignore it, and you should expect more people to seek help turning your features off — and to tell their neighbors about how they did it.