Teaching Through Analogy, What Works
Why this matters
A good analogy is the fastest way to make a technical concept stick with someone who has no background in your trade. A bad one confuses them more than saying nothing at all, or worse, leads them to a wrong mental model that causes bad decisions later, like a customer who thinks a pressure system works like a water balloon and now expects it to burst gradually instead of catastrophically. The skill of picking and testing a good analogy on the fly is teachable, and it is worth deliberately building because you will reach for one on every single customer-facing call for the rest of your career.
What makes an analogy work
Every analogy that lands shares three traits. Missing any one of them, it falls flat or misleads.
- The comparison object is something the customer has direct, physical experience with. Plumbing, garden hoses, electrical wiring in a house, a car engine, and the human body are the strongest universal reference points because nearly everyone has handled or experienced them directly. A comparison to another trade's specialized equipment fails because the customer has no direct experience with that either.
- The mechanism actually matches, not just the surface feel. "It's like a highway for electricity" sounds good but teaches nothing useful because a highway does not behave like a circuit. "It's like water pressure in your home's pipes, more resistance in the line means less flow at the far end" actually maps to how the underlying physics behaves, so the customer can reason forward from it.
- It answers the specific question asked, not a nearby one. An analogy for "why did it fail" and an analogy for "how does it normally work" are different explanations. Reusing the same analogy for both muddies the answer.
Reliable analogy families that hold up across trades
Use these as a starting toolkit, adapted to the specific system in front of you:
- Water and plumbing - pressure, flow, blockage, and pooling map cleanly onto electrical current, airflow, and drainage concepts. Almost every adult has direct experience with a hose, a faucet, or a clogged sink.
- The human body - a control system as a "brain," a sensor as a "nerve," a pump as a "heart," a filter as "lungs." Strong for explaining that one failed part can affect the whole system even when it seems unrelated to the visible symptom.
- A car - most adults understand that a car needs regular fluid changes, that a warning light means something specific, and that ignoring small noises leads to bigger repairs. This analogy family is especially strong for explaining the value of preventive maintenance, because the customer has already internalized that lesson from car ownership.
- A household budget - useful for explaining tradeoffs like efficiency versus upfront cost, or why a cheap fix now can cost more over time. Less useful for explaining physical mechanisms.
Where analogies break down, and how to catch it
Watch the customer's face and follow-up questions, not just your own explanation. Two signs an analogy is failing:
- They start asking questions about the analogy itself instead of the actual system ("wait, does it really have a heart?"). That means the comparison has become the thing they are trying to understand instead of a bridge to it. Drop it and restate plainly: "Sorry, bad comparison, let me say it straight instead."
- They nod but can't repeat back even the gist of it. A nod is not comprehension. If you ask "does that make sense" and get a flat "yeah," that is often politeness, not confirmation. A better check is to ask them to restate it in their own words on something that matters, like "so what would you watch for if that happened again" - if they can answer that, the analogy worked.
Don't let the analogy replace the real term
An analogy is a bridge to understanding, not a permanent substitute for the correct vocabulary. Use the comparison to build the mental model, then immediately attach the real term to it: "Think of it like your home's water pressure, that reading is what we call your line pressure." A customer who only ever hears the analogy never learns to describe their own system to the next tech, or to you on a future call. Naming the real term after the analogy respects the customer's ability to learn it, which is the whole point of this teaching craft.
When to skip the analogy entirely
Some customers process technical information better directly, especially anyone with adjacent technical experience (an engineer, a hobbyist, someone in a related trade). Watch for early signals: precise or jargon-adjacent questions, a request for the actual number instead of the general idea. For that customer, an analogy can feel condescending. Read the room in the first exchange and adjust, rather than running the same explanation style on everyone.
References
- See related: Teaching Through Analogy pairs with Translating Jargon Without Talking Down (internal cross-reference)
- See related: The Five-Minute System Walkthrough
- See related: Teaching the Difference Between Normal and a Problem
- Trade-standard practice for plain-language technical communication in residential field service