How IT Teams Can De-Escalate Moments Like the Judge Milliron Meltdown

A few days ago, a short courtroom video from Harris County, Texas, exploded across social media. During a remote hearing, Judge Nathan J. Milliron of the 215th Civil District Court experienced an audio sync issue. He called an IT technician to the bench to fix it on the spot. 

The tech quickly resolved the glitch, then, in a light-hearted moment, joked that it had been a “false alarm.” 

What happened next was captured on the still-live feed: the judge sharply told the worker not to joke around, ordered him to “get out of my courtroom,” demanded to speak to his supervisor, and was heard muttering, “I’m sick and tired of this xxx today.” 

The clip went viral for all the wrong reasons. Commenters called the judge rude, entitled, or lacking judicial temperament. Others defended him, saying he was simply stressed in a high-pressure public role. The IT technician stayed calm and professional throughout. 

Instead of joining the pile-on, I want to use this as a teaching moment. Because I’ve been on both sides of similar interactions (I’ve definitely delivered my share of ill-timed jokes), I’ve built a simple approach to help IT teams handle these situations better: Empathy First, Diagnosis Later. 

Why High-Pressure Moments Feel Different for Leaders

Let’s start by giving the judge (and anyone in a visible leadership role) some grace. When you’re the one “in charge”—whether you’re a sitting judge on the bench, a CEO on an investor call, or a manager running a client demo—technical problems are a lot more stressful. You’re supposed to project control, competence, and authority. Even a minor audio glitch can seem like it undermines all your credibility in front of an audience, a live record, or stakeholders who expect things to run smoothly. 

In a courtroom, the stakes are especially high. Time is precious, justice is on the line, and the entire proceeding is often being recorded. A 30-second disruption isn’t just annoying; it can feel like a threat to your credibility. While this pressure doesn’t excuse harsh words, it does explain why emotions can flare quickly. 

I get it. When you’re the person everyone looks to for direction, the last thing you want is technology making you look unprepared. 

The IT Side: Humor as a Coping Tool (and Why Timing Matters) 

Now let’s talk about the technician’s perspective, because I see myself in that moment. 

I use humor with my IT problems all the time to lighten the mood, help me stay sane when I’m troubleshooting the same “simple” issues repeatedly, and build rapport. Many of us in tech default to a casual joke after a quick fix because, from our side, it was straightforward. We just want to signal “no big deal, we got this.” 

But that joke landed at exactly the wrong time. The judge was already frustrated and operating under public scrutiny. What felt like harmless banter to the tech may have come across as minimizing the problem or even poking fun at the situation. 

I’ve made that same mistake myself: dropping a light comment when the other person was still wound up. Such blunders remind us that our intent doesn’t always match the impact. 

The Caller-at-Their-Worst Principle 

This brings me to one of the most important things I teach every team I lead: 

When people call IT (or any support role), they are often at their absolute worst. 

They’re stressed. Frustrated. Behind schedule. Sometimes they feel embarrassed or incompetent because the technology that’s supposed to make their job easier is instead making them look bad. In the judge’s case, the pressure was amplified by the public setting and the weight of his role. 

What they need in that first 30–60 seconds is not a root-cause lecture, a joke, or even an immediate “it was nothing.” They need to feel heard, respected, and confident that the problem is being taken seriously. 

A calm, empathetic response de-escalates. Jumping straight to humor or minimization can escalate, especially when a microphone is still hot or others are watching. 

The Practical Framework: Empathy First, Diagnosis Later 

So how should you actually handle these moments without letting them spiral into a viral clip? 

Here’s the simple framework I recommend: 

1. Fix it fast and acknowledge the frustration. 
   “I see how disruptive this is. Let’s get you back up and running.” 
   Show that you understand the impact before saying anything else. 
2. Hold the diagnosis for later: the “Back-Door” Strategy. 
   Once the immediate issue is resolved, resist the urge to explain or joke right then and there. Instead, use a calm, professional deferral: 
   “There are a few things that could have caused this. I’d like to come back later once I’ve had a chance to look a little deeper and give you a clear picture of what happened and how we can prevent it.” 
   This statement does several things at once: 
   1. Respects the other person’s stress by not forcing a conversation while emotions are high.
   2. Removes the “live audience” (or live microphone) factor.
   3. Turns a potential confrontation into a productive, private follow-up.
   4. Gives you time to investigate properly and prepare a thoughtful prevention plan.
3. Follow up promptly.
   Reach out the same day or first thing the next morning. Share what you found, own any systemic issues on the tech side, and turn the incident into training or process improvement. No one feels blindsided, and you build trust instead of resentment. Use this approach to prevent the exact “live fire debate” that was recorded in the courtroom. There’s time for emotions to cool down. The discussion takes place in a calmer setting. And the focus shifts from blame to solutions.

What Leaders Can Do Too

While this guide is aimed primarily at IT and support teams, the responsibility isn’t one-sided. Leaders who regularly work with tech staff can help by: 

• Acknowledging the support team publicly when things go right. 
• Practicing a bit of grace in the heat of the moment (we’re all human). 
• Setting clear expectations in advance about how tech issues should be handled during high-stakes meetings. 

Small Habits Prevent Big Headlines 

The Judge Milliron video will eventually fade from the news cycle. What doesn’t have to fade is the lesson: technical problems are inevitable, but how we respond to them is a choice.

If your IT team leads with empathy, saves the diagnosis and deeper conversation for a calmer moment, and uses that “back-door” script, they can de-escalate tension, protect everyone’s dignity, and turn stressful glitches into opportunities to strengthen partnerships.

I’ve seen this approach work countless times with my own teams, reducing drama, improving relationships, and helping everyone get back to their real work faster.

Have you ever been on either side of a situation like this? Drop your story in the comments; I’d love to hear how you handled it (or wish you had). If your team could use training on de-escalation, communication under pressure, or building better tech-support partnerships, feel free to reach out.

Let’s make sure the next tech glitch stays a glitch, not a headline.