The Customer Built a Workaround That Hides the Real Fault

Why this matters

Customers live with a problem far longer than you do, and most of them eventually invent a way to cope with it: a switch flipped a certain way, a valve left cracked, a breaker they reset every morning, a chair propped against a door that won't latch. By the time you arrive, the workaround has been running for weeks or months and has quietly become part of the system's normal operating state. If you diagnose the unit as it sits, with the workaround still in place, you are diagnosing a system that is not actually broken in the way the customer thinks, because the workaround is compensating for the real fault in real time. Miss it, and you either can't reproduce the complaint at all, or you fix the wrong thing and the workaround masks your failure until it lapses again.

How workarounds hide in plain sight

A workaround rarely gets announced. It gets discovered, usually by accident, because the customer stopped thinking of it as unusual a long time ago. Common patterns:

• A manual step replaced an automatic one. The customer resets a breaker every morning instead of you finding out why it trips. The automatic control failed; the manual habit became the fix.
• A setting was changed to avoid a symptom, not to solve it. A thermostat set five degrees off normal, a pressure regulator backed down, a timer shortened, because the equipment misbehaves at the correct setting.
• A physical prop, shim, or restraint compensates for something loose, warped, or misaligned. A wedge under a door, a bungee holding a lid, a brick on top of a vibrating unit.
• A sequence or timing habit avoids triggering the fault. "We just don't run the dishwasher and the shower at the same time," or "we wait ten minutes after starting it before we turn on the AC."
• A bypass or jumper defeats a safety or interlock that was tripping on a real condition, installed by the customer or a prior handyman fix, and now treated as normal.

None of these are stupid. They are rational responses to living with an unsolved problem, and the customer often doesn't volunteer them because they no longer register as remarkable, or because they worry admitting to a self-made fix will make them look responsible for the failure.

Ask for it directly, and ask the right way

Do not rely on the customer to mention the workaround unprompted. Ask a direct, non-judgmental question early in the visit: "Is there anything you've been doing to work around this, anything you've changed, propped, unplugged, or adjusted to keep it running?" Framing it as normal and expected, rather than as a confession, gets a far higher hit rate than a general "any other problems?" A customer who feels safe admitting the workaround gives you the single fastest lead to the real fault, because whatever they are compensating for IS the fault.

Walk the equipment yourself before you ask, and look specifically for anything that looks improvised: non-factory tape, wire, props, altered settings, a control set to an odd value, a switch labeled by hand. A visible workaround you spot yourself, and then confirm with the customer, is more reliable than one they self-report, because people forget to mention things that have become invisible to them.

Decide whether to test with it in place or removed

Once you find a workaround, you generally need to see the system both ways, because each view answers a different question.

• With the workaround in place, you see the system in the state the customer actually lives with, which may be the only state where the symptom is currently absent. This tells you the workaround is effective, at least partially, and gives you a clue about what it's compensating for.
• With the workaround removed, you see the raw fault the way it would present without human intervention, which is usually what you actually need to diagnose and confirm. See the related decision tree on removing the workaround versus diagnosing around it for how to sequence this safely.

Skipping the removed-state test is the single most common way a workaround causes a wasted visit: you diagnose the compensated system, find nothing conclusively wrong, and leave having confirmed the workaround works rather than having found the fault it is hiding.

The workaround as a diagnostic map, not just an obstacle

Once identified, treat the workaround as a clue rather than only a nuisance. What the customer had to do to keep the system running tells you almost exactly what failed:

• A breaker reset daily points at a control or load fault that trips protection under a specific, recurring condition, not a nuisance trip.
• A setting backed off from the intended value points at the system being unable to sustain the correct setting, which is a capacity, restriction, or component-wear problem, not a preference.
• A physical prop or shim points at a mechanical fault (loose, warped, misaligned, worn) at exactly the point being propped.
• A sequencing habit ("don't run both at once") points at a shared-resource limit, most often supply capacity, being exceeded when both loads run together.

Reading the workaround this way often gets you to the confirmed cause faster than starting diagnosis cold, because the customer has effectively already run a long-term field test and handed you the result.

Document it either way

Whether you remove the workaround as part of the fix or the customer needs to keep some version of it temporarily (parts on order, budget decision pending), write down exactly what the workaround was, what it was compensating for, and whether it is still needed. A workaround left undocumented gets rediscovered by the next tech, or by you a year from now, as a fresh mystery instead of a known, already-explained condition.

References

• Trade-standard practice for pre-diagnostic customer interview and equipment walk-through
• See related: Remove the Workaround Before Diagnosing, or Work Around It (decision tree); The Diagnostic Value of Asking What Changed Recently