Educational technology teams are often evaluated based on uptime, system reliability, ticket closure rates, and, of course, cybersecurity compliance. Those metrics matter. Schools and universities depend on secure, stable digital environments to support teaching, learning, and operations. Yet, many IT departments unintentionally overlook the most critical metric that directly shapes trust in technology services: customer experience and usability.
When faculty, staff, students, or families contact an IT help desk, they are not simply engaging with a technical system but interacting with people. They almost certainly have a problem and often feel frustrated or rushed for time because they need a piece of technology for a meeting or a class. The tone, responsiveness, empathy, and professionalism displayed during those interactions often determine whether users see the IT department as a collaborative partner or as a barrier to getting work done.
Technology support in education is ultimately a service profession. When I used to hire frontline IT staff, the customer service orientation was what I looked for, as technical skills can be taught. Developing customer service skills is much more difficult.
The Human Side of Technical Support
Educational institutions increasingly rely on technology for every operational and instructional function. Learning management and student information systems, classroom presentation tools, cloud storage, multifactor authentication, and digital assessment platforms have become foundational infrastructure.
At the same time, many educators and staff members are under significant pressure, so when systems fail or access becomes difficult, frustration escalates quickly. In those moments, customer service matters as much as technical expertise.
A help desk interaction may only last a few minutes, but it can influence a user’s perception of the entire institution. Small gestures of professionalism and courtesy make a measurable difference. For example, many institutions now require users to verify their identity through live video before account recovery or password reset procedures can occur.
Security concerns make these processes understandable and often necessary. However, if an IT staff member asks a user to turn on their camera and display identification, basic professionalism suggests the support staff member should activate their own video feed. The interaction should feel reciprocal and respectful.
Turning on a camera, introducing oneself, and explaining the process helps establish trust and transparency. Such actions are simple examples of customer-centered thinking.
Courtesy Is Not Optional
In many educational environments, IT departments unintentionally adopt cultures focused primarily on compliance and enforcement, rife with rigid policies, transactional processes, and impersonal communication. This can result in users avoiding support interactions, faculty members delaying the reporting of problems, students disengaging from required security processes, and staff members creating risky workarounds.
Effective IT support teams understand that professionalism includes patience, clarity, and empathy. Users do not always understand technical terminology, nor should they be expected to. An educator struggling with multifactor authentication during class preparation is not primarily concerned with the underlying architecture of identity management systems; they simply need to regain access quickly so they can teach.
Ultimately, support interactions should minimize stress rather than increase it.
Simple practices can significantly improve service quality:
- Introducing oneself to the customer.
- Explaining why a security procedure is necessary
- Using plain language rather than excessive technical jargon; however, don’t talk down to the user
- Providing realistic timelines for resolution
- Sending routine satisfaction surveys, as nothing is more frustrating than getting an email saying a ticket has been closed when the problem has not been resolved.
- Designing support procedures around user workflows rather than institutional convenience
Educational institutions often speak about relationship building in classrooms and student services. The same philosophy should apply to technology support.
Cybersecurity Must Support the Mission
Cybersecurity threats facing schools and universities are real. Ransomware attacks, phishing attempts, credential theft, and data breaches continue to affect educational institutions nationwide. IT leaders are correct to prioritize strong security controls.
However, institutions sometimes implement security practices that significantly impair usability without meaningfully improving protection. In 1755, Benjamin Franklin wrote, “Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety.”
IT leaders need to consider this concept when tightening security to the point that it is difficult to use the system being protected. Balance becomes essential. As my favorite university registrar has been known to say, he builds systems that address the needs of 90% of the students and faculty. One of the reasons he is my favorite is that he understands there needs to be enough flexibility in systems to address the needs of the remaining 10%.
If security measures or any institutional processes become excessively burdensome, users predictably seek ways around them. Faculty members may store passwords insecurely. Staff may rely on unofficial tools. Students may disengage from institutional systems altogether. Ironically, overly rigid environments can create additional vulnerabilities.
Edtech exists to support learning, communication, research, and organizational effectiveness. Functionality cannot become secondary to process or systems. This requires IT leaders to ask difficult but important questions:
- Does this security process genuinely reduce risk?
- Is the burden on users proportional to the threat?
- Have we designed this procedure from the perspective of the end user?
- Are we building trust or creating frustration?
- Would reasonable people view this process as respectful and transparent?
Strong IT organizations understand that security and usability are not opposing concepts. Effective security should integrate as seamlessly as possible into the user experience.
Leadership Sets the Tone
Leadership shapes customer service cultures; they do not emerge accidentally. If institutional leaders reward only ticket closure counts and compliance metrics, staff members naturally focus on speed and enforcement. If leaders instead emphasize professionalism, communication quality, and relationship building alongside technical competence, they support cultural change.
IT leaders should regularly review support practices through the lens of user experience. Mystery shopper exercises, satisfaction surveys, and direct feedback sessions with faculty and students can provide valuable insights into how support interactions are actually perceived.
Technical expertise alone does not automatically produce strong customer service skills. Help desk professionals should receive training in communication, conflict management, accessibility, and customer interaction strategies just as they receive technical training. In educational settings, especially, technology teams should remember that every interaction contributes to institutional culture. At the end of the day, users rarely remember the specific technical details of a support ticket but how they were treated.
As noted earlier, Benjamin Franklin famously warned against trading essential freedom for temporary security. The digital world presents a similar challenge. Educational institutions must protect systems and data while still preserving accessibility, usability, transparency, and trust. Technology support should help people accomplish their work, not create unnecessary obstacles to it.