When Two Techs Disagree on the Cause: Decision Tree

Why this matters

When two capable techs look at the same fault and name different causes, the dangerous resolution is letting personality settle it: the louder one, the senior one, or the one who wants to stop arguing. A cause chosen by who pushed hardest instead of what the evidence shows leads to the wrong repair, a callback, and a customer who never sees the internal mess but feels the result. Disagreement is actually a healthy sign; it means someone is questioning a theory before parts get ordered. The goal of this tree is to convert two opinions into the one correct answer using the equipment as the referee, not to crown a winner.

Start here: state both theories as predictions

Before debating, make each tech commit their theory to a falsifiable prediction. A real diagnosis predicts something you can check. "It is component A" should become "if it is A, then this reading will be out of range and this one will be normal."

If a theory cannot be turned into a prediction you could test, it is a hunch, not a diagnosis, and it loses to one that can.

If both theories make testable predictions, you now have a clean path: find the test that separates them.

Ask: is there a test that distinguishes the two causes?

The fastest resolution is a single measurement or observation that confirms one theory and rules out the other. The equipment settles what the techs cannot.

If such a test exists and is cheap to run, run it. This is the whole ballgame. A definitive reading beats any amount of experience-based argument, regardless of who holds which theory.

If the test exists but is expensive or destructive, do not commit to it blindly. Eliminate the cheaper branches first so the expensive test is the last one standing, or look for an indirect check that is reversible.

If no clean distinguishing test exists, move to the cost-and-safety logic below.

Weigh safety before cost

If the two theories carry different safety implications, the safety question outranks everything, including who is more likely right.

If one theory implies a hazard (a gas, electrical, structural, or combustion risk), that theory must be ruled out before proceeding on any other, even if the other tech thinks it is unlikely. The conservative path wins until the hazard is cleared.

If neither theory raises a safety concern, decide on cost and reversibility.

Choose the cheaper, more reversible path first

When no test separates the theories and safety is neutral, pick the action that costs least and is easiest to undo. If it is wrong, you have lost little and learned something.

If one theory's repair is cheap and reversible and the other's is expensive and permanent, try the cheap reversible one first. A wrong cheap step is a free diagnostic; a wrong expensive step is a disaster you are committed to.

If both paths are comparably costly and irreversible, do not guess and do not split the difference into a fix that addresses neither cause. Escalate.

Escalate rather than replace both parts

The worst resolution to a genuine deadlock is installing both suspected parts to end the argument. That doubles the cost, hides the diagnostic failure inside the customer's invoice, and teaches both techs that disagreements never have to be resolved.

If the matter cannot be settled on site and both paths are costly, escalate to a third opinion, a senior diagnostician, or the manufacturer's technical line, and let that input break the tie. Bring both theories and the evidence; do not present it as "who is right."

If the system is down and the customer is waiting, the fair move is the cheapest reversible step now plus a clear plan to confirm, communicated as one company position.

The decision and the customer-facing rule

Resolve by test first, then by safety, then by cost and reversibility, then by escalation, in that order, and never by rank or volume. Whatever you decide, present the customer with one unified recommendation. The internal debate stays internal; a customer who hears two of your people contradict each other loses confidence in the whole company even when one of them is right. If you genuinely cannot settle it on site, the honest single message is "here is the reversible step we are taking now and here is how we will confirm," not two competing diagnoses.

What to document

Record both theories, the evidence behind each, and the test you ran or the cost-and-safety logic you applied. Note which theory the evidence ultimately supported, because that is the data that makes the next disagreement faster to settle and lets the tech whose theory was rejected calibrate. Handled this way, a disagreement becomes a training asset instead of a friction point, and the shop builds better diagnosticians than one where the senior person is always right by default.

References

• Occupational Safety and Health Administration, General Duty Clause, 29 U.S.C. 654(a)(1) (conservative-path obligation when a theory implies a recognized hazard).
• Electronics Technicians Association International (ETA), root-cause analysis and peer-review practice.
• See related: Parts Cannon vs Diagnosis: The Discipline; The Rare vs Common Cause Bet Decision Tree; The Obvious Cause Is Wrong Decision Tree.