The Junior Tech's Diagnosis Conflicts With the Senior Tech's: Decision Tree
Why this matters
A junior tech's diagnosis conflicting with a senior tech's is one of the most common disagreements a shop has, and it is also the one most likely to get resolved by rank instead of by evidence, because the instinct is to trust experience. That instinct is usually right, but "usually" is doing a lot of work in that sentence. A junior tech is sometimes seeing something real that pattern-matching experience has learned to overlook, and a shop that always defaults to seniority loses those catches and teaches its newer people that speaking up doesn't matter.
Start here: has the junior tech's finding actually been heard, or just outranked
Before anything else, confirm the junior tech's specific evidence has been stated and understood, not just noted and dismissed. Ask them directly: "what did you find, specifically, that points you there?" If the answer is a hunch with no reading or observation behind it, that changes the next step. If the answer is a specific measurement, a visual finding, or something the senior tech had not accounted for, treat it as evidence that needs to be reconciled, not overruled.
If the junior tech has a specific, confirmed finding
- Have the senior tech address that specific finding directly, not the junior tech's overall conclusion. "Here's what I found and here's why I don't think it points where you think it does" is a real answer. "I've seen a hundred of these, trust me" is not, even from someone with the standing to say it.
- If the senior tech's explanation accounts for the junior tech's finding, the disagreement is likely resolved, and this is a genuine teaching moment: the junior tech learns why that finding does not mean what they thought it meant.
- If the senior tech's explanation does not fully account for it, run the one test that would settle it, even if the senior tech is confident. A five-minute test is cheap insurance against a repeat visit; an unaddressed confirmed finding does not go away because it was outranked.
If the junior tech's case is a hunch, not a finding
| Situation | What to do |
|---|---|
| Junior tech has a gut feeling but no specific evidence | Ask what would confirm or rule it out, and if it's quick, check it. If it's not quick, defer to the senior tech's confirmed diagnosis and move forward |
| Junior tech is pattern-matching from a different, similar-looking fault they've seen before | Explain the distinguishing feature between this fault and that one; this is a direct, valuable teaching moment |
| Junior tech is uncertain and second-guessing a correct senior diagnosis | Reassure and explain the reasoning; do not let uncertainty alone stall a confirmed diagnosis |
A hunch deserves a hearing, not automatic deference to rank, and not automatic equal weight against confirmed evidence either. The right response depends on which one it actually is.
If the roles were reversed and it's the senior tech who might be wrong
The hardest version of this disagreement is when the junior tech's confirmed finding directly contradicts the senior tech's confirmed diagnosis, and the senior tech is reluctant to revisit it. Handle this the same way you would want a junior tech's mistake handled: focus on the evidence, not on who said it. "Here's a specific reading that doesn't fit; can we walk through it together" is a way to raise this without it reading as a challenge to standing. A senior tech who is actually wrong on a specific point and corrects it in front of the junior tech is a better outcome for the shop, and for that junior tech's development, than a wrong diagnosis protected by seniority.
Recap
Confirm the junior tech's finding is specific evidence, not just a hunch, before deciding how to weigh it. If it's confirmed evidence, have the senior tech address it directly and run the deciding test if the explanation doesn't fully account for it. If it's a hunch, check it quickly if that's cheap, otherwise defer while explaining the reasoning. Never let rank alone silence a specific, confirmed finding, in either direction.
References
- Internal quality-control practice: structured mentorship and evidence-based dispute resolution
- Trade-standard practice for pairing junior and senior technicians on ambiguous calls
- See related: When Two Technicians Genuinely Disagree; The Team Debrief After a Diagnostic Disagreement That Mattered