Explaining How a System Works Without a Textbook
Why this matters
A customer who understands, in plain terms, how their own equipment works makes better decisions: they call earlier instead of waiting for a full failure, they approve the right repair instead of the cheapest-sounding one, and they stop assuming every noise means the whole system is dying. A tech who can only explain a system by reciting its parts list in order loses the customer in the first sentence. The skill is not knowing more, it is compressing what you know into a picture the customer can hold in their head.
Use an everyday analogy as the entry point
Every complex system has an everyday equivalent close enough to build a first mental model. A pressure system is like a garden hose with a kink. A thermostat is like a house's brain giving orders. A pump is like a heart pushing fluid through a body. The analogy does not need to be perfect, it needs to be close enough that the customer stops feeling lost and starts asking better questions. Once they have the analogy, you can correct the parts that do not quite fit.
- Pick an analogy from daily life, not from another trade they will not know either.
- State the analogy once, plainly, then move on. Do not over-explain the metaphor itself.
- If the analogy breaks down at some point in the explanation, say so directly ("it's not exactly like that here, because..."). A customer trusts an analogy more when you are honest about its limits.
Teach the flow, not the parts list
Customers do not need to know the name of every component. They need to understand the sequence: what happens first, what happens next, and where the chain breaks when something fails. "Power comes in here, gets sent to this control, which tells this part to turn on, which then does the actual work" is a story a customer can follow and repeat. A list of six component names in a row is not.
Once they have the flow, you can point to exactly where in that sequence today's failure happened. "Remember how I said power goes to the control first? That's the piece that failed. Everything downstream of it just never got the signal." This lands because you already gave them the map.
Give them one number or one sign to watch for
A customer cannot retain a full technical explanation, but they can retain one number or one symptom. Pick the single most useful thing for them to notice going forward: a sound, a smell, a reading, a light, a delay. "If you ever hear a clicking that doesn't stop after a few seconds, that's usually this part starting to go. Call before it fails completely." One memorable cue beats a full lecture on failure modes.
Match technical depth to what they will actually use
Not every customer needs the same depth of explanation, and giving everyone the deepest version wastes your time and theirs. A useful gauge:
| Depth | When to use it | What it sounds like |
|---|---|---|
| One sentence | Just-fix-it customer, or a routine repeat visit | "Same part that usually goes first, replaced it, you're good." |
| Analogy + flow | Curious customer, first-time customer, bigger-ticket repair | The garden-hose or brain analogy, plus the sequence of what failed |
| Full walkthrough | Customer making a decision between repair options, or teaching them a habit that prevents recurrence | Analogy, flow, the specific failure, and what to watch for going forward |
Draw it if words are not landing
A rough sketch on a work order pad, or pointing at the actual system while you talk, closes gaps that words alone cannot. Some customers are visual learners and a hand-drawn arrow showing "air comes in here, goes out here" does more in five seconds than another sentence would in thirty. See related: Teaching Through Demonstration, Not Just Telling.
What to avoid
- Do not lead with acronyms or model-specific terms before the customer has the plain-language picture. Define, then use the term. See related: Translating Jargon Without Sounding Condescending.
- Do not over-correct a slightly-wrong customer analogy mid-explanation unless it actually matters to the decision at hand. Being right about a metaphor is not the goal; the customer making a good decision is.
- Do not use the explanation as a stalling tactic or a soft upsell. If you catch yourself explaining longer because you are building toward a sale rather than building understanding, stop and separate the two conversations.
References
- See related: Teaching Through Demonstration, Not Just Telling
- See related: Translating Jargon Without Sounding Condescending
- See related: The Two Types of Customer, Curious vs Just Fix It
- Trade-standard practice for customer-facing technical communication