It Only Fails When the Customer Operates It a Specific Way

Why this matters

You test the equipment using your own normal operating sequence and it works perfectly. The customer swears it fails constantly. Both of you are telling the truth, and the gap between you is usually that the fault only appears under a specific operating pattern the customer uses and you have not replicated. Finding that pattern turns an unreproducible, frustrating call into a straightforward diagnosis. Missing it produces a "no fault found" that damages trust, because from the customer's side, you tested wrong and declared their real problem imaginary.

Why operator-dependent faults are so easy to miss

Most diagnostic routines run equipment through a standard sequence: start it, let it reach steady state, check the readings, stop it. That sequence is built to catch the majority of faults efficiently, but it specifically will not catch a fault that only appears when the equipment is operated in an atypical order, at an atypical speed, in a specific combination of settings, or with an unusual pause or repetition somewhere in the sequence. If the customer's actual daily use includes any of those atypical elements, and you never ask what they specifically do, your standard test sequence and their real usage never intersect, and the fault stays hidden the entire visit.

What kinds of operating patterns commonly trigger a hidden fault

• Rapid cycling. Turning equipment off and back on again quickly, faster than the manufacturer's intended interval, can reveal a fault that a slow, deliberate test sequence never touches (a component that needs time to reset, discharge, or re-pressurize before a healthy restart).
• An unusual combination of settings or modes used together, especially ones not commonly paired, can expose an interaction the equipment was not well-tested against, even by the manufacturer.
• Operating at one extreme of an adjustable range (maximum setting, minimum setting, a specific intermediate point the customer happens to prefer) rather than the mid-range setting a standard test typically uses.
• A specific sequence order - turning on accessory functions before the main function, or in a particular order out of habit, that differs from how you would normally test it.
• Duration-dependent faults that only appear after extended continuous operation, well past the length of a typical diagnostic test run.
• Physical operator technique - how hard, how far, or how quickly a manual control is engaged, which a tech testing gently and deliberately will simply never reproduce.

How to find the actual pattern

1. Ask the customer to walk you through exactly what they do, in order, the way they would do it if you were not standing there. Not "how do you normally use it," which invites a summarized, cleaned-up answer, but "show me" or "tell me step by step, in the order you actually do it."
2. Watch for the details that would not occur to someone describing their own habitual actions. People rarely think to mention timing, sequence, or speed because it feels automatic to them; you often have to draw it out with specific questions ("how quickly do you move from this step to the next," "do you ever do these two things at the same time").
3. If possible, have the customer operate it themselves while you observe, rather than you operating it based on their description. A description filtered through their own account can lose details that are obvious once you watch them do it directly.
4. Reproduce their exact pattern, not your standard test sequence, once you understand it. If the fault appears under their pattern and not yours, you have found the actual trigger condition, and now you can isolate what about that specific pattern is causing the problem.
5. If the fault still will not reproduce even after matching their described pattern, consider whether there is an environmental or timing element they are not aware of themselves (time of day, a condition elsewhere in the space, something intermittent layered on top of the operating pattern). This becomes closer to a genuinely intermittent fault investigation at that point, rather than a simple pattern-matching exercise.

What this changes about your diagnosis

Once you can reliably reproduce the fault under the customer's actual pattern, you have real ground to diagnose from, current draw, pressure, timing, whatever your instruments show during the failure, rather than guessing at a cause you cannot observe. This is also the point where you can distinguish a genuine equipment fault from an operating pattern the equipment was never designed to tolerate; the fix in the first case is a repair, and the fix in the second case may be showing the customer a different way to operate it, which is a legitimate and sometimes the correct outcome. Do not assume it must be one or the other before you have actually reproduced and examined the failure under real conditions.

References

• Manufacturer documentation on intended operating sequences and duty-cycle limits
• Trade-standard practice for reproducing customer-reported intermittent symptoms
• See related: The Sound a Customer Describes Doesn't Match Any Known Fault (decision tree); What a Data Log Can Tell You That a Single Visit Can't