How to Explain a Malfunctioning AC Part Without Boring Your Reader to Tears

I once watched a homeowner’s eyes glaze over three sentences into an explanation of why her air conditioner wouldn’t start. The technician was right. He was also reciting a service manual at a kitchen table. She nodded, signed the invoice, and probably could not have repeated a word of it a day later.

That gap, between being correct and being understood, is where most technical communication dies. You can describe the exact failure happening inside a machine and still lose the person in front of you. The fix isn’t dumbing anything down. It’s building the explanation around the reader’s experience instead of the part’s anatomy. And if you want the mechanics of one specific breakdown to follow along with, this breakdown of a faulty contactor hvac issue is a solid example of a symptom-first approach.

Here’s the framework I use, and I’ll show you how it works on a genuinely unglamorous piece of hardware: the contactor inside a central air unit.

Why does a correct explanation still fail?

Because accuracy and clarity are two different jobs, and most people only train for the first one.

An engineer describing a contactor failure wants to talk about pitted contacts, coil voltage, and continuity readings. All true. All invisible to the person standing in a 90 degree living room. When you lead with invisible internals, your reader has nothing to grab onto, so they stop grabbing.

The better move is to start where they already are. They’re hot. The thermostat says “cool.” Nothing happens. That’s the shared ground, and it’s where any good explanation begins.

I’ll go ahead and stake a claim here: the symptom is always the better opening than the mechanism. Lead with what the person noticed, and you’ve bought yourself the attention to explain why it happened.

The Symptom, the Analogy, the Stake

I call this the S.A.S. pass, and I’ve used it for everything from broken appliances to a badly designed slide deck. Three moves, in order. You’ll notice it works best when you resist the urge to add a fourth.

1. Name the symptom in their words

Not “the contactor failed to close.” Instead: “Your AC clicks, then nothing.” Or “It hums for a second and quits.” Those are phrases a real person would actually say, and hearing their own observation reflected back builds trust fast.

2. Give them one analogy, not three

A contactor is a switch. That’s it. It’s the thing that connects power to the machine when the thermostat asks for cold air, and it disconnects when the ask stops. You can compare it to a light switch and move on. Two analogies in one explanation means your reader now has to keep track of two imaginary objects while also learning about a real one.

Pick the switch. Drop the relay metaphor. Drop the gate metaphor. One mental picture, fully loaded.

3. Tell them what it costs to ignore it

Here’s where a lot of technical writers flinch. They lay out the problem and then get vague about consequences, worried it sounds like a sales pitch. I’d argue the opposite. Staying silent about stakes is what feels evasive.

In the contactor case, a switch that won’t close means the compressor never gets power, so the house keeps warming up while the fan might still run and fool you into thinking something’s happening. That detail, the fan running while the cooling doesn’t, is the kind of thing that makes a reader sit up. It’s also the sort of behavior that shows up across home electrical systems generally, which is why the Department of Energy spends so much effort teaching homeowners to read their own energy use instead of guessing.

What details earn their place, and which ones just show off?

This is the judgment call that separates a useful explanation from a lecture.

A detail earns its place when your reader can do something with it or notice it themselves. A buzzing noise that appears right before the unit quits? Earns its place, because now they can listen for it. The fact that the contacts inside are made of a specific silver alloy? Almost certainly does not, unless your reader is another technician.

Run every detail through one question: can the reader observe this, act on this, or repeat this to someone else? Two yeses and it stays. Zero and it goes.

I’d also push back on the instinct to front-load every caveat. You don’t need three sentences of “results may vary” before your first plain sentence. Say the clear thing first. Qualify it after the reader is already tracking with you.

A worked example you can borrow

Say a friend texts you because their AC quit overnight. Here’s the S.A.S. version in a few lines, and notice there’s no jargon until the very end, where it actually helps:

“Your thermostat’s calling for cold, but the unit outside never kicks on, right? It’s probably the switch inside the unit that hands power to the compressor. When that switch stops closing, the whole thing sits there dead even though the thermostat’s still asking. The fan might even run and make it look like everything’s fine. That switch is called a contactor, and it’s a common failure. Worth having someone check the power side before you assume the compressor itself is gone.”

That last sentence matters. It reframes the diagnosis as a checkable step rather than a verdict, which lowers the temperature of the conversation. People resist conclusions. They cooperate with next steps.

Where do numbers help, and where do they wreck the sentence?

Numbers are tricky. Used well, one number can carry a whole paragraph. Used badly, a page of figures reads like a spreadsheet with verbs.

The safe move is to reach for broadly established baselines rather than anything specific or recent, because a precise figure you can’t source is worse than no figure at all. When you do cite something technical, lean on standards bodies and independent labs that set the ground rules everyone else works from. The National Institute of Standards and Technology is a good example of a source that carries weight without selling anything, which matters when your reader is already primed to suspect a pitch.

Here’s my own rule. If a number doesn’t change what the reader does next, cut it. “It fails more often in summer” changes nothing. “It fails more often after the first real heat wave” at least tells them when to pay attention.

A quick checklist before you hit send

  • Does the first sentence describe something the reader has personally noticed?
  • Have you used exactly one analogy, and does it survive the whole explanation?
  • Could your reader repeat the gist to a neighbor without reading it again?
  • Did you name the actual part once, after the plain explanation, so they have a word to search later?
  • Is there a clear next step, or did you leave them with a diagnosis and no door out?

That fourth item is the one people skip, and it’s a small tragedy. Readers deserve the real name of the thing, tucked in at the end where it becomes useful instead of intimidating. Standards bodies like the IEEE exist precisely because shared names for parts make technical conversations possible in the first place, and your reader is now part of one.

Write for the person, not the schematic

Technical clarity isn’t a gift. It’s a set of choices, and the biggest one is deciding whose experience leads. The moment you start with the reader’s hot living room instead of the pitted contacts, everything downstream gets easier, including the analogy and the stakes.

So next time you have to explain a broken part, resist the schematic. Name the symptom. Pick one switch. Say what it costs to wait. Then, and only then, tell them what it’s called. Try it on the next thing that breaks in your own house, and see how differently people listen.

Leave a Reply

Your email address will not be published. Required fields are marked *

Shop for your perfect poster print or digital download at our online store!