How to explain something technical to somebody who is not

You're standing in somebody's kitchen explaining why the whole circuit needs doing rather than just the one socket. You can see it happening in real time: their eyes glaze, they nod in the way people nod when they've stopped following, and then they say "so what does that mean for me?"

That question is the whole job, and most of us answer it last if at all. We explain the mechanism and hope the meaning is obvious, because to us it is.

Simplifying isn't the goal

The usual advice is to use simpler words. It's not wrong, and it's not the main thing.

You can explain something in perfectly simple language and still lose people completely, because what makes an explanation hard isn't vocabulary. It's that the listener doesn't know why they're being told any of it.

What they want is a decision. Should I do this, what will it cost me, what happens if I don't. Everything you say should be on the way to one of those, and anything that isn't is where their attention goes.

Lead with what it means for them

Reverse the order you'd naturally use. Start with the consequence, then give as much of the mechanism as they actually want.

Instead of: "the consumer unit's an old rewireable type and there's no residual current protection on the lighting circuit, so…"

Try: "This needs replacing, it's about £450, and it's the sort of thing that'll come up when you sell the house. I can explain why if you want, but that's the short version."

You've given the decision, the cost and the timing in one breath. Then — and this is the part people skip — genuinely offer the detail. Some customers want it, and letting them ask for it feels completely different from having it delivered at them.

One comparison, not three

A good comparison does more than a paragraph of explanation. A bad one does damage, and three of them in a row make you sound like you're performing.

The rule is that it has to come from their world, not yours. Comparing a heating system to another heating system helps nobody.

"It's like a fuse box, but the old kind that doesn't cut out fast enough if something goes wrong." "Think of it as the tyres on a car — they're fine until they're not, and you don't wait for the blowout."

Use one, then stop and check it landed. The most common mistake is stacking analogies on top of each other until the original point is buried under them.

Give the numbers they can act on

Vagueness feels safer and is the thing that makes people uneasy. "It could be quite expensive" is much worse than "somewhere between four and six hundred."

Same with time. "It'll take a while" leaves them imagining the worst. "Most of a day, and you'll have no power between about ten and two" is something they can plan around.

And if the honest answer is that you don't know yet, say what would tell you and when. "I won't know until I've had the board off, which is ten minutes — I'll tell you before I do anything else."

Say what happens if they do nothing

This is the question every customer is silently asking and almost nobody asks aloud, because it sounds like they're trying to avoid spending money.

Answer it unprompted, and answer it honestly, including when the answer is "probably nothing for a few years."

If you leave it, it'll most likely be fine day to day. The two things that'll force it are selling the house, or if you ever want to add anything to the circuit.

That does something no amount of explaining can. It shows you're not inventing urgency, which is the single biggest fear people have about trades they don't understand — and the honesty makes everything else you've said more believable.

Watch for the nod

There's a specific nod that means somebody has stopped following and doesn't want to say so. Once you know it, you can't miss it.

When you see it, don't repeat yourself more slowly. Change the question instead. "Sorry, I've gone into detail there — what's the bit you actually need to decide?" puts them back in control without making them admit they were lost.

And never say "does that make sense?" It's a question people answer yes to regardless, because saying no feels like admitting something. "What would be useful to know?" gets a real answer.

Write it down before you leave

Whatever you've explained, they'll be repeating it to somebody else this evening — a partner, a landlord, a parent — and they'll be repeating your explanation badly, because they only heard it once and they don't know the words.

Leave two lines in writing. What's wrong, what it costs, what happens if it's left. That's the version that gets forwarded, and it's the version that makes the decision.

It's also the version that protects you, because half the disputes in this trade come from two people remembering a kitchen conversation differently.

The same explanation, forty times a year

Here's what's worth noticing. You explain the same five or six things over and over, to different people, in slightly different words depending on how tired you are.

Those explanations are genuinely valuable, and they exist nowhere except in your own head. Everybody who wasn't standing in the kitchen — including the people deciding at eleven at night whether to ring you at all — gets nothing.

That's the gap hailera was built for: you write those explanations down once, in your own words, check them yourself, and publish them as an agent, so your website and the AI apps people now ask can give the same clear answer instead of whatever they can piece together. A page on your own site headed "what this actually means" does much of the same for nothing, though, so write the two or three you give most often and put them up.

The test

Here's how you know an explanation worked. Not whether they nodded — whether they could repeat it.

If a customer can tell their partner, in their own words, what's wrong and what it costs, you've done the job. If they can only say "he said something about the circuit", you explained it to yourself.

Today: take the thing you most often have to explain and write it in three sentences — what it is, what it means for them, what happens if they leave it. Use it next time instead of starting from scratch.

Written by the team at hailera — we help small businesses answer customer questions without being there.