Reading the Symptom Correctly

"The motor won't start" could mean five completely different things. Watch one symptom fork into five real fault domains.

Interactive · One Symptom, Five Domains

Tap each branch — notice each one requires a genuinely different first check, even though the reported symptom is identical.

Every fault begins as words from someone who isn't you — an operator saying "the motor won't start," a report reading "level reading looks wrong," a shift log noting "vibration alarm again." These words are a compressed, lossy description of something physical happening in the real world, and the compression loses information you need. Reading the symptom correctly means decompressing it BEFORE you start testing.

The Discipline of Asking "What Would Each Cause Actually Look Like?"

For "motor won't start," five genuinely different root causes could produce that exact same operator-reported symptom — no power reaching the control circuit at all, an overload relay that tripped and latched, a safety interlock correctly blocking the start, a mechanical jam preventing the motor from turning even if electrically it's trying to, or a genuinely failed motor winding. Each of these has a fast, cheap, distinguishing first check — but only if you've paused to list them before diving in.

"The symptom tells you where to LOOK. It rarely tells you what you'll FIND. Confusing the two is how technicians end up testing the wrong thing confidently."

A Genuinely Useful Habit: The Two-Minute Symptom Breakdown

Before touching a single test lead, spend two minutes actually listing every plausible cause of the reported symptom — not exhaustively, just the 3-5 most likely domains. This costs almost nothing and pays for itself almost every time, because it prevents the single most common beginner trap: anchoring on the FIRST plausible cause that comes to mind and testing only that, while ignoring equally likely alternatives sitting right next to it.

Watch for Symptom Language That Hides Assumptions An operator saying "the sensor is broken" has already done some (possibly wrong) diagnosis for you — the actual observation might just be "the reading looks wrong," which could equally mean a genuinely broken sensor, a process condition the operator doesn't expect, a wiring fault, or a scaling error somewhere upstream in the control system. Always try to get back to the RAW observation, not someone else's interpretation of it.

Check Your Understanding

Take a vague symptom you've heard recently — "the feeder is acting up," "the loop is jumping around," anything similarly non-specific — and try listing four or five genuinely different root causes that could each produce that same vague description. This exercise, done consistently, is what separates technicians who test efficiently from technicians who test whatever comes to mind first.

CHAPTER RECAP

A reported symptom is a lossy compression of a real physical fault — multiple different causes can compress to the same words
Before testing, spend a couple of minutes listing several plausible causes, not just the first one that comes to mind
Try to get back to the raw observation, since operator/reporter language often already contains unverified assumptions
This habit prevents anchoring on the first plausible explanation while equally likely alternatives go unchecked

← Chapter 2 Book Home Chapter 4 →

Electrical Fundamentals for Beginners — 30-Lesson Animation-Driven Training Course

Industrial Instrumentation Fundamentals — 30-Lesson Practical Training Course

Intermediate/Advanced Electrical Theory — 31-Lesson Professional Training Course

LADDER LOGIC FOR PLANT TECHNICIANS

PLC Fundamentals for Plant Technicians

Fault Finder's Field Book — Practical Fault-Tracing Procedures & Real War Stories