There was a time when “technology help” in a library meant showing someone how to use a computer mouse, helping a patron access their email, or walking someone through printing a document.
That time is long gone.
Today, technology touches nearly every aspect of library service, extending well beyond the technology department. Staff across the library are expected to troubleshoot devices, navigate apps, assist with printing and scanning, support digital services, and answer questions about AI, all while keeping up with existing technology and adapting to whatever comes next.
The result? Whether we signed up for it or not, nearly everyone working in a library today has become a “tech person” to some degree. Expanding technology skills across library staff is a good thing, but there’s a significant difference between “everyone can help with technology” and “everyone is expected to know everything.”
Technology Confidence Is Not the Same as Knowing Everything
I’m a big believer in building technology confidence among library staff. Staff should feel comfortable trying unfamiliar things, troubleshooting basic problems, and helping patrons without immediately assuming that every technology question belongs to someone “more qualified” to handle it. But confidence doesn’t mean having every answer. It means being willing to find one.
And that distinction matters. When we tell staff they need to become more comfortable with technology, the goal shouldn’t be to turn every employee into an IT specialist. That’s impossible. The goal should be to give them enough knowledge, practice, and support to approach unfamiliar problems with confidence, rather than immediately shutting down or assuming someone else needs to handle them.
At the same time, being comfortable with technology means recognizing your own limitations. There will always be questions that require more specialized knowledge. Knowing when you’ve reached that point and when to ask for help is a technology skill in itself. Confidence isn’t always “I can solve everything.” Sometimes, it’s “I can try, and I know when to ask for help.”
Where Technology Burnout Starts
Technology burnout doesn’t usually come from learning one new system or answering one difficult question. It builds over time. A new database launches that staff need to learn. A familiar interface gets completely redesigned overnight. A printer that worked yesterday suddenly refuses to connect. A patron walks in with a device no one on staff has ever seen before. A software update moves every setting you knew how to find. A new app requires another login, another verification process, and another set of instructions.
Individually, none of these things may seem overwhelming. Together, though, they add up.
The pressure can be especially intense for staff members who become known as the “tech people.” Once someone demonstrates that they’re comfortable with technology, questions have a way of finding them. They become the person coworkers turn to when something stops working, the person patrons are referred to when a technology question gets too complicated for anyone else, and sometimes the person expected to figure out a device or system they’ve never even encountered before.
Over time, being everyone’s default troubleshooter can turn a strength into a source of frustration, especially when constant interruptions begin competing with their own daily responsibilities.
That creates a challenge for libraries. We want technology knowledge to be shared across staff, but we also need to recognize when the responsibility for solving technology problems starts falling on the same handful of people simply because they’ve demonstrated they can handle it in the past.
Building a Healthier Technology Culture
The answer isn’t to lower expectations around technology. Libraries need staff who are willing to learn, adapt, and help patrons navigate an increasingly digital world. But those expectations need to be matched with the time, training, and support necessary to meet them.
That means giving staff opportunities to practice new technologies before they’re expected to support them, creating documentation that people can actually use, encouraging coworkers to share what they know, and making it acceptable to say, “I don’t know, but let’s see if we can figure it out together.” It also means recognizing that consistently handing problems off to the most technologically confident person, without giving others opportunities to learn, does little to build confidence among library staff.
Managers and technology staff have a role to play here too. Sometimes the most helpful thing we can do is resist the urge to immediately jump in and take over. Walking someone through a problem may take longer than simply fixing it ourselves, but that extra time can pay off. The next time that same problem comes up, they may be able to handle it on their own, or even guide a patron or fellow coworker through it.
It’s Okay to Have Boundaries
Not every technology problem is something library staff should be expected to solve, however. And even when a question is appropriate for library assistance, there are still limits to how far that help should go. A patron might ask you to reset their online banking password, hand you a credit card to make a purchase, complete an online medical or legal form for them, or enter sensitive personal information on their behalf. Even something as simple as taking control of a patron’s phone or computer can become complicated when private messages, saved passwords, financial information, or other personal data are involved.
Boundaries also matter internally. When one employee becomes the default person for every technology question, their own responsibilities can quickly take a back seat to everyone else’s problems. That isn’t a sustainable approach to technology support. Libraries need clear expectations about what staff should be able to handle independently, when it’s appropriate to ask for help, and when a problem requires more specialized knowledge.
Everyone Can Be a Tech Person. No One Has to Know Everything.
Technology is going to keep changing, and the role it plays in libraries is only going to continue to grow. That’s something we need to embrace. But a healthy technology culture isn’t built on the expectation that everyone becomes an expert. It’s built on giving people the confidence to try, the support to keep learning, and the judgment to know when it’s time to ask for help.
When Everyone Becomes the Tech Librarian

Leave a Reply