Telling a Design Flaw Apart From a Failure
Why this matters
A failure and a design flaw feel identical on the service call: the system does not work, the customer is unhappy, and something needs fixing. But they are opposites, and treating one like the other burns you. Repair a genuine failure and the system runs like it should. "Repair" a design flaw and you have a brand-new part on a system that still cannot do the job, a callback in a season or two, and a customer who thinks you did shoddy work. The skill is telling them apart before you quote.
The one question that splits them
Ask yourself, and the customer: was this system ever right? A failure is a part that was doing its job and stopped. A design flaw is a system that never could do the job as it was built. That single question routes most calls correctly.
- "It cooled fine for six years, then last week it stopped keeping up." That is a failure. Something changed. Find what changed.
- "It has never really kept the back bedrooms comfortable since the day it went in." That is a design flaw wearing a failure's clothes. Nothing failed. It was undersized, mislaid, or mismatched from the start.
A failure has a before. A design flaw does not.
Four tells that point to design, not failure
| Tell | What you see | Why it points to design |
|---|---|---|
| No triggering event | Nothing broke, nothing changed, yet it underperforms | A real failure has a cause you can find; design never met the target |
| Fails only under peak load | Fine in mild conditions, misses on the hottest day, the fullest tank, all fixtures open | Capacity was sized below the real demand |
| Repeats after a correct repair | Same part or same symptom returns despite good work | The design keeps stressing whatever you replace |
| "Always kind of did that" | Long-standing complaint the customer stopped mentioning | People normalize a flaw they have lived with for years |
Any one of these should slow you down before you write "replace the part."
Where the two overlap
A design flaw often finally causes a real failure, and that is the confusing case. An undersized breaker trips for years, then the conductor overheats and a lug fails. A too-small pump runs long every day, then the motor burns out early. You will fix the failure that is in front of you, but if you stop there you have only reset the clock. The part died because the design overworked it. Fix the part and name the design cause, or you will meet this system again.
What changes once you know
- On a failure: find the cause, repair or replace the failed part, verify, done. The system was right and will be right again.
- On a design flaw: the honest fix is a change to the system, not a part swap. Sometimes that is a resize, a reroute, an added component, or a correction to how it was installed. Say so plainly, and separate what a repair can buy (time) from what only a redesign fixes (the actual problem).
Never quote a part swap as a cure for a design flaw. It is the fastest way to own a problem you did not create.
References
- Trade-standard practice for load calculation and equipment sizing (cooling/heating load, water demand, electrical load, pump turnover)
- Manufacturer application and design data for correct system selection
- See related: The System Never Worked Right From Day One (decision tree); Reading the Design Intent to Know What Should Be Happening