
220: On Customer Service and IT
An AI-created episode based on a human-composed blog post: On Customer Service and IT
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

An AI-created episode based on a human-composed blog post: On Customer Service and IT
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Picture this. You are staring at your computer screen. It is 4 .45 p .m. Oh, the absolute worst time for anything to happen. Literally the worst. You have a massive, I mean, potentially career defining presentation due to your boss at five. I can already feel my blood pressure spiking. Right. So you move the mouse to hit save and nothing. the cursor turns into that little spinning wheel of doom. The dreaded spinning wheel. Exactly. The screen just freezes completely. You can actually
feel the adrenaline dump into your bloodstream, like that cold panic starting to rise in your chest. Oh, hell yeah. You mash the keyboard, still nothing. You restart the monitor, hoping it's just a visual glitch. But deep down, reality's setting in. You realize exactly what you have to do next. You have to make the call. You have to make the dreaded call to IT. Yeah, that universal spike in cortisol. I mean, your body is reacting as if a tiger just walked into the room. But the threat is a frozen spreadsheet. It's so true. It is a very specific type of modern dread. You
are staring down the barrel of a blown deadline, and now you have to dial a number, sit on hold, and, well, prepare for an interaction that historically just feels fraught with friction. And that's the crazy part, isn't it? The person picking up that phone is literally employed. to fix your exact problem. That's their whole job. Right. Their entire job description is to rescue you in this moment, yet they often feel like the absolute most difficult people to talk to when things go wrong. Yeah, they do. Why is it that
the very people holding the key to your salvation suddenly feel like adversaries? Well, it is a fascinating psychological clash, honestly, and it is rarely about the actual hardware of the software. Really? Yeah. The friction you are feeling is an entirely human phenomenon. There is a brilliant breakdown of this exact dynamic by Dr. Gary Ackerman. Right. The educator. Exactly. He is an author and educator who looks at this through the lens of school IT departments on his site, Hack Science. He wrote this 2022 piece
called On Customer Service and IT. And it's fantastic. It really gets right to the biological and psychological roots of why these interactions fail. And the insights there are totally universal. I mean, whether the setting is a middle school where a teacher's smart board just died or a Fortune 500 corporate office where the server crashed during an earnings call. The stakes feel the same to the user. Exactly. The underlying human psychology is identical. So we are doing a deep dive into the anatomy of that friction today. Not the technical stuff, right? Right. Not the
technical side of resetting passwords or configuring local area networks. We're looking at the behavioral science of why interactions between technical experts and stressed out novices go completely off the rails. Which happens constantly. Constantly. And more importantly, how mastering three specific behavioral traits can completely rewrite that dynamic. So to understand the solution, I think we have to dissect the anatomy of the crash itself. Let's do it. When you make that call at 4, 4, 5 PM, you and the technician are occupying two
completely different emotional universes. That's a great way to put it. From your perspective, the house is on fire. Your career feels like it's on the line. Yeah. But from the IT professional's perspective, it is Tuesday afternoon, and they currently have like 30 other houses on fire. Wow. Yeah. And some of those are structurally more critical to the entire organization than your specific computer. So the mismatch in urgency is just huge. Massive. To the user, IT feels
like an obstacle. You are panicking, and the person on the other end of the phone is asking you calmly for your employee ID number. or whether you check the power cable. Which is infuriating when you're stressed. It really is. It feels like they are actively interfering with your ability to do your work, or worse, that they are completely ignoring your priorities. And Dr. Ackerman points out something critical about the technician side of the equation here. What's that? IT professionals actively, though unconsciously, contribute to these difficulties because they
project their own level of technological familiarity onto the users. Oh, I see. Like, when you do something eight hours a day for 10 years, your brain literally prunes the neural pathways that represent the struggle of learning it. You develop cognitive blind spots. Oh, it's the curse of knowledge. Yes, exactly. It's like a world -class Michelin star chef watching a customer try to perfectly dice an onion. Oh, that's a perfect analogy. Right. And the chef gets visibly frustrated when the customer mangles it. To the chef, holding
a knife with a claw grip is muscle memory. It is as natural as breathing. They don't even think about it. Right. They literally cannot remember what it feels like to not know how to hold the blade. Yeah. But to the customer, it is a complex, terrifying mechanical skill where they might lose a finger. They're terrified. Exactly. Dr. Ackerman is saying IT professionals fall into the exact same trap. They project their baseline of comfort onto someone who is currently spiraling in a state of technological panic. And the way Dr. Ackerman frames the responsibility for bridging
that gap is really fascinating. He specifically writes, referring to the mindset of an IT technician, he says, things we find easy, they find difficult, and that is your problem, not theirs. Wait. That is your problem, not theirs. That places the burden of translation entirely on the expert. It does. It forces the expert to own the communication gap. Wow. Because when an IT professional fails to adopt that mindset, when they forget that the user's lack of knowledge is the exact reason the IT department exists well, things break down.
Right. Because if everyone knew how to fix it... IT wouldn't have jobs. Exactly. The technician fails to ask the right diagnostic questions, the user gets defensive because they feel stupid, and the technician defaults to blaming the user for breaking the machine. Which is the worst thing you can do. The absolute worst, because the moment blame enters the equation, the psychological safety of the interaction just evaporates. Okay, so if the root of the problem is this massive gap in mutual understanding, the logical first step to fixing it has to be empathy, right? You
would think so, yes. But reading through the source, Ackerman introduces his first trait of a customer service -oriented IT professional with a massive caveat. He really does. He warns that doing empathy the wrong way can actually make the situation worse. And I have to say, wait, hold on. Yeah. We are taught from childhood to apologize when things go wrong. How is saying, I'm sorry this happened? A bad move. It comes down to how the human brain processes sincerity during a state of high stress. OK. Dr. Ackman
doesn't just say the goal is empathy. He explicitly defines it as empathy without being patronizing. Ah, patronizing. Right. When a user calls in a blind panic about a lost presentation, their bullshit detector is dialed up to 11. Oh, for sure. They are hypervigilant. So if they hear an over -scripted robotic phrase like, I'm sorry that happened to you, it doesn't convey human understand. it conveys a corporate script. It sounds like you're talking to a laminated card. Yes. Like, insert empathy phrase here. Exactly. It signals that the technician is managing you,
not actually helping you. Precisely. Ackerman notes that these scripted apologies actively interfere with the user's perception of good customer service. The user thinks, you aren't sorry. You are just reading from a manual to get me to calm down. Which makes you even angrier. Right. It creates massive psychological distance. Authentic empathy in a technical crisis isn't about reciting an apology. It is about validating the urgency of the user's situation. So what does that look like? Well, a phrase like, I see
you have a hard deadline in 15 minutes. Let's look at this immediately. Does infinitely more to calm a user than a hollow apology. Because you are acknowledging their reality. Exactly. You're in the trenches with them. OK. So the first step is authentic empathy, dodging the patronizing scripts and validating the stakes. But let's be real about the reality of the job for a second. OK. Even if the IT professional is perfectly empathetic and validates the urgency, They still have to deal with the raw, unfiltered anger of someone whose technology is failing.
I mean, the user might literally be shouting. How is a technician supposed to handle a user who is losing their mind over a crashed hard drive? without absorbing all that toxicity. Well, this requires acting completely against our basic biological instincts. Because we want to fight back. Right. When someone yells at us, our fight or flight system engages. But Ackerman defines the second crucial trait as the ability to not take criticism personally. he calls for a highly
developed sense of emotional armor. It's psychological displacement. Yes. It reminds me of being a lightning rod. Yeah. You can't scream at a corrupted silicon chip. You can't throw a punch at a malfunctioning cloud server. I mean, you could try, but it wouldn't help. Exactly. The human brain needs a social target to process its frustration. When the tech fails, the user has all this chaotic energy, so they displace it onto the nearest grounded object. Which is usually the IT professional who just walked into the room. And the source makes it clear that encountering these users
is an absolute inevitability of the job. The user is going to direct completely unwarranted criticism at the technician, blaming them for the software update, the sluggish internet, the fact that their mouse battery died. Blaming them for literally everything. Everything. The most effective IT professionals have the situational awareness to recognize displacement for what it is. They realize the anger is entirely situational. Exactly. They let the lightning hit the rod and go straight into the ground. They do not internalize the strike. But wait, does this mean IT professionals
just have to sit there and absorb endless abuse from people? No, absolutely not. Because I was going to say, are they just supposed to act as emotional punching bags for the entire office every time the Wi -Fi drops? No, and the source draws a very sharp boundary there. Overlooking a momentary panic -driven outburst is a component of good customer service, but... tolerating systemic abuse. That is a failure of leadership. Oh, that makes sense. Dr. Ackerman explicitly distinguishes between acute frustration and what he calls workplace
bullies. So there is a difference between someone having the worst Tuesday of their year and someone who habitually uses tech issues as an excuse to demean the support staff. Exactly. And here is the crucial shift in responsibility. It is not solely on the IT professional to endure those bullies. Thank goodness. Ackerman states that it is the direct responsibility of organizational leaders to recognize these bullying individuals and address them long before drastic human resource interventions become necessary. So management
has to step in. Management has to step in. The emotional armor protects the technician from the daily friction of the job, but leadership must protect the technician from chronic toxicity. It is a dual shield system. That's a great way to look at it. OK, so the temperature in the room is finally down. The tech hasn't patronized the user with fake apologies, and they haven't escalated the conflict by taking the user's panic personally. Right, the groundwork is laid. But at the end of the day, the screen is still frozen. The spreadsheet is still stuck. The actual technical
problem still needs to be solved. What is the psychological off ramp here? How does the technician actually fix the machine without triggering the user again? Well, this brings us to the final pillar, which relies on clear and professional communication. But the mechanism behind it is entirely counterintuitive. How so? It revolves around active listening, asking questions, seeking visual cues, gathering details about the symptoms. I want to highlight a total paradox from the text here. Yeah, go ahead. We usually think of
a technician asking questions simply to gather data, right? They ask, what were your last three keystrokes to diagnose the machine? Sure. But Ackerman points out that when IT professionals use active listening, it actually increases the user's sense of empathy for the technician. Yeah, it's wild. The empathy flows in reverse. Why does asking diagnostic questions calm the user down? Because it is a brilliant biological hack. Tell me more. When you ask a user a specific concrete question about the sequence of events
leading to the crash, you are forcing their brain to switch gears. To answer you, they have to move out of their amygdala. the primitive emotional center of the brain driving their panic. Exactly. Out of the amygdala and engage the prefrontal cortex, which handles logic and episodic memory retrieval. Oh, wow. They physically cannot maintain a state of peak emotional hijack while simultaneously trying to remember if they clicked save as or export. That is fascinating. By asking the right
questions, you are literally pulling them out of their panic state. You're forcing them to think logically. You are bringing the user into the process as a collaborator. They stop seeing the technician as a gatekeeper withholding a magical fix and start seeing them as a human being actively trying to solve a puzzle with them. Precisely. And once the data is gathered and the technician knows the solution, they have to communicate it. This is where the translation matrix happens. The translation matrix. Right. According to Dr. Ackerman, users need exactly three things delivered to them to feel secure.
OK, what are they? The problem is how the technician intends to fix it. and the timeline for resolution. What? How and when? Yep. But the delivery of those three things must be ruthlessly curated. Ackerman notes quite bluntly that most IT users absolutely do not care to hear all the details of the problem and the solutions. Right. They do not want a master class on computer architecture. They really don't. They do not care about the motherboard's voltage or the specific line of corrupted code or the intricacies of the DNS
server cache. Yeah. My eyes are glazing over just hearing that. Exactly. Especially if those details are delivered using heavy jargon. Which brings up a good question. Why do experts fall back on jargon so often? It almost feels like a defense mechanism. It absolutely is a psychological shield. Think about it. In a tense situation, the expert feels the pressure of the user's frustration. To establish authority and protect themselves, the expert retreats into their domain of power, their specialized vocabulary. Oh, because it proves they are the smartest person in the room
regarding this specific machine. Exactly. But to the user... Jargon is alienating. It reinforces that feeling from the beginning of our discussion. that the IT person is an obstacle speaking a foreign language. So instead of saying we have a catastrophic failure of the primary solid state drive requiring a full sector by sector data recovery protocol, you just say your hard drive crashed. Keep it simple. I am running a program to recover your files and we will know if it worked by tomorrow morning. Clear, simple, professional. What is wrong? How are you fixing it? When will
I have my machine back? You know, if you were listening to this and you have ever had to explain a complex tax penalty to a panicked client or, I don't know, a catastrophic engine failure to a stranded driver. Oh yeah. This applies to you just as much as it does to an IT technician. Anytime you possess specialized knowledge and have to deal with a frustrated novice, these three pillars are your blueprint. Absolutely. Offer authentic empathy by validating their urgency rather than patronizing them with scripts. Wear your emotional armor and recognize displacement
for what it is, allowing leadership to handle true toxicity. Right. And use jargon -free active listening to pull them out of their emotional brain, delivering a clear what, how, and when. The psychology is universally applicable because, well, human nature doesn't change based on the industry. No, it doesn't. It is an incredibly powerful framework for navigating conflict. And it leaves me with one final thought to mull over. What's that? While looking at Dr. Ackerman's site, hackscience .education, I noticed he also
hosts a podcast called Fruit Coral Plus Classroom. Oh, right. And looking through the episode list, there are discussions on Everett Rogers' diffusion of innovations theory. Oh, that's a fascinating theory. That theory explores how, why, and at what rate new ideas and technologies spread through a culture or an organization. Right. It maps out the adopters versus the laggards. Yes. And considering everything we just discussed about friction, empathy, and communication, it makes you wonder. Think about massive organizational failures to adopt new innovative technology.
Like a company rolls out a multi -million dollar software system and the staff completely rejects it. Which happens all the time. Exactly. How many of those failures aren't actually failures of the technology itself? How often does a brilliant workflow die simply because of a failure of human -to -human customer service when bridging the gap between the builders and the users? Oh, that's a brilliant point. If the bridge of communication is broken, the innovation never reaches the other side. Yeah. The sophistication of the technology
is totally irrelevant if the human interaction surrounding it fails. It all comes down to the translation. It really does. So the next time you find yourself staring at a frozen screen, you're pulse racing as the deadline approaches. Remember the human on the other end of the phone. And if you are the one picking up that call, remember that sometimes the most important tool in your entire technical toolkit isn't your administrative access. No, it's not. It's your ability to speak human.
Nobody is credited on this episode yet.
An AI-created episode based on a human-composed blog post: Changing Vision of Technology Literacy
An AI-generated episode based on an AI-generated blog posts based on an old microblogging post: The Inquiring Technologist: Why Great Solution Design Begins with "Too Many" Questions
A brief AI-generated episode based on a human-composed blog post: Gathering Organizational Intelligence for Network Security
An AI-generated episode based on a human-composed blog post: Models of Technology-Rich Teaching
An AI-generated episode based on a blog post designed for students in a community college course. Concepts of Operating Systems