Explaining a Diagnosis So a Non-Technical Person Gets It

Why this matters

A correct diagnosis the customer does not understand does not close, does not build trust, and does not stop them from calling a second opinion or three other shops before they say yes. Most customers are not skeptical of your competence, they are skeptical of a sentence full of terms they cannot verify. Explain the same diagnosis in language they can actually follow, and the conversation changes from "prove it" to "okay, what do we do."

Step 1: Lead with what they will notice, not the part name

Start from the symptom the customer already experienced, not the component you found. "The reason it's been making that noise and running longer than it used to" connects to something they lived through. Opening instead with a part name and a failure mode they have never heard of forces them to trust you blind before you have said anything they can verify.

Step 2: Translate the term the moment you use it

Never use a technical term without immediately defining it in the same breath. Not "I'll get to that later," the same sentence.

• "The capacitor, that's a small part that gives the motor its initial push to start, is weak."
• "There's continuity, meaning electricity is flowing through it when it shouldn't be, on this wire."

If you catch yourself using a second undefined term while defining the first, stop and simplify further. Layering jargon on jargon is the single most common way this fails.

Step 3: Use an analogy from outside the trade

A good analogy borrows a mental model the customer already owns from daily life. A capacitor is like a battery that gives a motor a jump start. A clogged filter is like breathing through a straw, everything downstream has to work harder. A pressure imbalance is like a kinked garden hose. Pick analogies from cars, plumbing at home, breathing, or everyday mechanics, things most adults have direct experience with, not trade-to-trade comparisons that only make sense to another technician.

Test your analogy before you use it: if explaining the analogy itself requires another analogy, it is too complicated. Simpler is more convincing, not less.

Step 4: Show, don't just tell, when you can

If the part is visible and safe to point to, do it. "See this, see how it looks different from that one next to it, that's the wear I'm talking about" is more convincing than any verbal description, because the customer is now evaluating evidence instead of taking your word. A photo works nearly as well when the part is not accessible or you need to hand something over later.

Step 5: State the cause, the consequence, and the fix, in that order

Structure the explanation so the customer can follow the logic, not just the conclusion:

1. What's wrong (in plain terms, translated as above).
2. What happens if it's not addressed (concrete and honest, not exaggerated for effect).
3. What fixing it involves (what you'll do, roughly how long, and what changes once it's fixed).

Skipping straight to "here's what it'll take to fix" without the first two steps reads as a sales pitch, even when it is not. Walking the full sequence reads as a diagnosis, which is what builds trust.

Step 6: Check they got it before you move on

Do not assume a nod means understanding. Confirm the core point landed, using a neutral frame rather than "does that make sense." A quick teach-back on the one thing that matters most catches a missed step while you can still correct it.

Step 7: Match your pace to the person in front of you

Some customers want the short version and trust you to have the details right. Others want to understand every step before they will say yes. Read which one you have early, by watching whether they ask follow-up questions or start looking impatient, and adjust. Forcing a detailed explanation on someone who wants the short version reads as stalling; giving the short version to someone who wants detail reads as being brushed off.

Common mistakes to avoid

• Over-explaining to prove expertise. More jargon does not sound more credible, it sounds evasive to someone who cannot verify it.
• Under-explaining to save time. A rushed, vague diagnosis is what drives a customer to call a second opinion.
• Talking down. Simplifying the language is not simplifying the person. Keep the respect in your tone even when the vocabulary is basic.

References

• See related: The Teach-Back Method: Confirming They Actually Got It, Explaining a Problem Without Talking Down, Teaching the Customer What a Normal Sound or Smell Is