Three People Describe the Same Fault Three Different Ways

Why this matters

Ask three people in the same house or building what is wrong and you will often get three different answers, none of them false, all of them partial. The teenager says "it's broken." The parent says "it makes a weird noise sometimes." The grandparent says "it's been doing this for months." None of them lied. Each one noticed a different slice of the same underlying fault, filtered through what they personally experienced. A tech who treats one report as the whole picture chases the wrong lead. A tech who gathers all three and reconciles them finds the real fault faster and looks sharper doing it.

Why the accounts differ in the first place

People do not describe faults, they describe their experience of a fault, and that experience depends on what they were doing, what they noticed, and how long they have lived with it.

• Exposure differs. Whoever is home during the day sees a different failure window than whoever is only home at night. A fault that only shows up under a specific load or time of day gets reported by whoever happens to be present then, and dismissed by everyone else as "never happens to me."
• Sensitivity differs. One person notices a faint smell or a subtle noise; another does not register it until it is severe. Neither is wrong, they simply have different thresholds for what counts as "something."
• Memory compresses over time. Someone living with an intermittent problem for months often collapses "it happens sometimes" into "it's always broken," while someone who just noticed it yesterday reports it as sudden and new.
• Vocabulary differs. A "weird noise" from one person and a "grinding sound" from another may be the exact same sound described with different words and different confidence.

How to interview more than one person without wasting time

You rarely have the luxury of a group debrief. Use these habits to extract more signal without turning the visit into a committee meeting.

1. Ask the same short question of whoever is present, one at a time if needed: "When did you first notice this, and what were you doing?" A consistent phrasing across people makes their answers easier to compare.
2. Note who said what, even briefly in your head or in the job notes. If accounts conflict later, you want to know whose account you are reconciling, not just a blended memory of "someone said."
3. Ask for the most recent occurrence, not the general pattern, from each person. "Tell me about the last time it happened" produces more reliable, specific detail than "how often does it happen," which invites a rounded-off guess.
4. Do not correct one account with another out loud mid-interview. Let each person finish their version before you compare. Interrupting person B with "well person A said..." makes B defensive and edits their memory toward agreement instead of accuracy.

Reconciling conflicting accounts

Once you have more than one version, treat them as complementary data, not a contest to decide who is right.

• Look for the union, not the intersection. If one person reports a noise and another reports a smell, you likely have one fault producing two symptoms, not two separate faults. Combine the reports into a single symptom picture before you diagnose.
• Weight the most specific, most recent account higher, but do not discard the vaguer one. "It's been acting up for months" from the person who is rarely home still tells you the fault is long-standing, even if they cannot describe it precisely.
• If two accounts genuinely conflict (one says it only happens in the morning, another says only at night), do not assume one is wrong. Check whether the fault is tied to something that differs by time of day for each person: who is running what, what the ambient condition is, what load is present. The apparent contradiction is often two true observations of a fault that is condition-dependent, not person-dependent.
• A single sharp detail from any one person outweighs a vague consensus from the rest. If one report includes a specific number, a specific sound, or a specific sequence of events, chase that thread even if the other accounts are fuzzier.

What to do with the reconciled picture

Write down the combined symptom set before you start testing, in plain terms everyone would recognize: what happens, when, how often, and what if anything makes it better or worse. This composite description is what you diagnose against, not any single person's account. It also becomes the sentence you read back to the household at the end: "so what you're all describing is X happening under Y conditions, is that right?" Getting a nod from more than one person in the room is the cheapest confirmation you will get that you actually found the right fault.

References

• Trade-standard practice for customer intake and symptom documentation
• See related: Conflicting Symptom Descriptions From the Same Household (Decision Tree); Reading the Evidence of a Previous Repair Attempt