The Customer Who Left Out the Detail That Mattered
Why this matters
Half of the hard diagnoses are not hard because the fault is exotic. They are hard because you are working with two-thirds of the story. The customer knows something you need, and it never made it into the conversation. Maybe they forgot, maybe they did not think it mattered, maybe they would rather you did not know. Either way you burn an hour chasing a symptom that a single sentence would have explained. Learning to expect the missing piece, and to go get it, is one of the highest-leverage skills in the trade.
The detail is missing, not absent
Start from the right assumption: the fact exists. Someone in that building knows why the water heater started leaking the same week, or that the breaker was already tripping before you were called, or that the pool just stopped the day after a party. The information is real and available. It simply has not reached you yet. That framing changes how you work. You are not guessing in the dark, you are recovering a fact sitting in someone's memory.
The kinds of detail that get left out
Most withheld details fall into a handful of buckets. Knowing the buckets tells you what to go looking for.
| What gets left out | Example across trades | What it changes |
|---|---|---|
| A recent change or event | A remodel, a storm, a power blip, new equipment added | Points you at cause and effect you would never suspect |
| A prior attempt | They, a handyman, or another shop already worked on it | The system in front of you is not stock |
| How it is really used | Who runs it, how often, how hard, what they run through it | A "defective" unit is being operated outside its limits |
| History and recurrence | It has done this before, it is a repeat, it is seasonal | Turns a one-off into a pattern with a root cause |
| Something they think is unrelated | A smell, a spill, a noise elsewhere, a leak they mopped | The "unrelated" thing is usually the same fault upstream |
The last row costs the most. Customers filter the story down to what they believe is relevant, and they are not trained to know what is relevant. The mopped-up puddle they did not mention is the leak you are looking for.
Why the omission costs more than a bad reading
A wrong meter reading is one bad data point among many; you cross-check it and move on. A missing history rewrites the whole picture. If you do not know a system was worked on last month, every factory assumption you make is wrong, and you will trust wiring, settings, and parts that someone already changed. The omission does not just slow you down, it points you confidently in the wrong direction. That is worse than knowing you are stuck.
Build the habit: assume one detail is missing
Do not treat the intake story as complete. Treat it as the opening statement. Before you commit to a diagnosis, ask yourself what would have to be true off-screen for what you are seeing to make sense, then go find out whether it is. A tech who assumes the story is whole stops asking questions too early. A tech who assumes one detail is always missing keeps a door open, and that door is where the real cause usually walks in.
When you realize a detail was withheld
- Do not make it an accusation. "Good to know, that actually explains a lot" gets you the next detail; "why didn't you tell me that" shuts the customer down.
- Re-open the diagnosis, do not patch it onto the old one. New history can invalidate work you already did. See related: Re-Opening a Diagnosis When New Information Appears.
- Write the new fact down and note when it surfaced. If the job becomes a warranty or insurance matter, when-you-learned-what matters.
- If the withheld detail is a safety issue, a defeated safety device, a gas smell they downplayed, water near live electrical, stop and address the hazard before you continue diagnosing.
The reflex to build: the customer is not lying to you, they are summarizing, and the summary always drops something. Your job is to find the part they dropped.
References
- Trade-standard diagnostic practice: history-taking before component testing
- See related: Drawing Out the Information a Customer Forgot to Mention; Why Customers Withhold the Detail That Would Help You; The Story Doesn't Match What You Found (decision tree)