The Assumption That Cost You an Hour

Why this matters

Most wasted hours in the field do not come from hard problems. They come from an unchecked assumption made in the first five minutes that sent you down the wrong road. You assumed the power was on, the part was good, the customer described it accurately, or the last tech's note was right, and you spent the next hour proving a theory built on a false premise. Catching assumptions early is the single biggest time-saver in diagnosis.

The assumption is the silent step

Every diagnosis rests on a chain of small beliefs: power is present, the supply is good, the part I just installed works, the reading I am trusting is accurate. Most of these are true most of the time, which is exactly why they are dangerous. You stop checking them. Then the one time the assumption is false, you do not even consider it, because in your head it is not a variable, it is a fact. The hour disappears chasing everything except the actual problem.

The assumptions that bite most often

• "It has power." You troubleshoot a dead system for thirty minutes before discovering it was never getting supply. Verify the input before you diagnose the output.
• "The new part is good." Parts fail out of the box. Replacing a part with another bad part and concluding "that was not it" sends you chasing ghosts. Confirm the replacement actually works.
• "The customer's description is accurate." Customers report what they noticed, not what is happening. "It makes a noise when it starts" might be a different event than you pictured. Confirm the symptom yourself.
• "The last note is right." A prior tech's diagnosis can be wrong or out of date. Use it as a lead, not a verdict.
• "I tested that already." Did you, on this visit, under these conditions? A test from last week or a test you meant to run is not a test you ran.

Verify the cheap things first

The cure for assumption-chasing is to confirm the foundations before you build on them, and the foundations are usually the fastest things to check. Confirm power and supply before diagnosing behavior. Confirm your test instrument is working before you trust its reading. Confirm the symptom with your own eyes before you theorize about its cause. Each check costs a minute. Each skipped check risks an hour. The math is not close.

Make the assumption visible, then test it

When a diagnosis is not adding up, the move is to ask: what am I taking for granted right now? Say the assumptions out loud, even to yourself. "I am assuming this has power. I am assuming this reading is accurate. I am assuming the customer described the right event." The instant you name an assumption, it stops being an invisible fact and becomes a testable claim. Half the time, naming it is enough to make you check it, and the check is the answer.

When you are stuck, go back to the start

A diagnosis that has stalled is almost always built on a bad premise somewhere upstream. Instead of pushing harder on the same theory, return to the first link in the chain and verify each step you skipped. The fault is rarely at the complicated end you are staring at. It is back at step one, in the thing you were so sure of you never looked.

Trust, but confirm

This is not a call to test everything to death. Experienced techs move fast precisely because their assumptions are usually right. The skill is knowing which assumption to check and when. The trigger is friction: when the evidence does not fit, when the test contradicts the theory, when you have been on it longer than it should take, that is the signal that a silent assumption is wrong. Stop, name it, confirm it. The hour you save is your own. See related: Confirmation Bias in Diagnosis; The Fault You Keep Missing.

References

• Trade-standard practice on systematic troubleshooting and signal-tracing.
• Manufacturer documentation on diagnostic sequence and verification steps.
• See related: Confirmation Bias in Diagnosis; The Fault You Keep Missing.