Good Engineering Means Designing Things to Fail Gracefully
Things break. Batteries run out, components wear down, sensors fail and consumables need replacing. That’s an unavoidable part of engineering.
But one thing going wrong shouldn’t mean the entire product stops working.
We call this failing gracefully, and it’s something we believe should be considered from the very beginning of the design process.
One Failure Shouldn’t Stop Everything
A printer that runs out of ink should still work as a scanner. A smart device that loses its internet connection should still perform its basic local functions. A product with a faulty sensor should continue operating safely wherever that sensor isn’t essential.
Yet too often, products are designed so that one minor problem disables everything.
From an engineering perspective, this is a design choice. Systems can be built with independent functions, fallback operating modes and the ability to keep working when non-essential components fail.
It requires more thought during development, but it can make an enormous difference to the product’s usefulness and lifespan.
Give People Time to Fix the Problem
Another frustration is how little warning products often provide before they stop working.
A device might tell you its battery is running low shortly before shutting down. But what happens if that battery isn’t readily available? You might need to identify the correct replacement, find a supplier, order it and wait for delivery.
Meanwhile, you have a perfectly functional product that you can’t use.
A low-battery warning should give users enough time to obtain a replacement, not merely enough time to watch the device switch itself off.
The same principle applies to filters, cartridges, wear components and scheduled maintenance. Wherever possible, products should monitor deterioration and warn users well before a failure becomes critical.
And if replacement parts are needed, they should be easy to identify, obtain and install.
When Bad Design Becomes Good Business
There’s an uncomfortable commercial aspect to this problem.
Some manufacturers benefit twice when products become unusable. First, by selling replacement consumables or proprietary parts, and second, when frustrated customers eventually replace the entire product.
A printer that refuses to scan without ink, or a device that becomes useless because a minor component can’t be replaced, can push customers towards purchases they wouldn’t otherwise need to make.
Not every failure is deliberate, of course. Sometimes these problems arise because graceful failure simply wasn’t considered during development.
But whether intentional or accidental, a business model built around making products unnecessarily difficult to maintain is a poor substitute for good engineering.
Design for What Happens When Things Go Wrong
In a small engineering and prototyping workshop, we spend a lot of time thinking about how products should work. But it’s equally important to consider what happens when they don’t.
Can essential functions continue independently? Will the user receive enough warning? Can they diagnose the problem themselves? Is the replacement part accessible and affordable?
These questions are much easier to address during the design stage than after a product reaches customers.
Good engineering isn’t about pretending things will never fail. It’s about anticipating failure and making sure the consequences are manageable.
A product should remain useful for as long as possible, even when everything isn’t working perfectly.
That’s what failing gracefully really means.
