The Fear of Reliability
MTBF is a symptom of a bigger problem. It is possibly a lack of interest in reliability. Which I doubt is the case. Or it is a bit of fear of reliability.
Many shy away from the statistics involved. Some simply do not want to know the currently unknown. It could be the fear of potential bad news that the design isn’t reliable enough. Some do not care to know about problems that will requiring solving.
What ever the source of the uneasiness, you may know one or more coworkers that would rather not deal with reliability in any direct manner.
Is ‘Reliaphobia’ a Thing?
Maybe not directly, yet the symptoms seem to be there. A set of avoidance concerning the topic. The lack of focus to understand or improve reliable. The dismissal of estimate or test results. The rush to ‘put right’ any life limiting problems.
The general desire to move on or away from detailed discussions concerning reliability is a clue. This may be difficult for reliability professionals to grasp as we tend to enjoy understanding failure mechanisms. We tend to work to estimate or analyze reliability performance. It is what we do.
Other than the math, does mechanical engineering engender such avoidance? For power electronics a bit of fear is good, as touching a live circuit could be fatal. Discussion a plan to improve reliability performance may require a bit of thinking, yet certainly isn’t dangerous.
Maybe there is a fear of reliability at work around us.
A Personal Fear
Maybe those we work with avoid little more than saying reliability is important and avoid understanding reliability because it may lead to more work or reflect poorly on their design.
If you have been part of a FMEA discussion, you may have noticed the uneasiness of the person responsible for the design. The group of people around the table one by one describe potential weaknesses or flaws with the design. We’re basically saying the design may be inadequate, which in a way is saying the designer is likewise inadequate.
Few enjoy such sediment from their peers.
Others may see the highlighting or understanding of a design’s reliability performance as just another way to add work to an already busy timeline. I did once work with a project manager that didn’t want to perform any testing to failure. One, failures is bad and we don’t want to have failures. Two, any weaknesses or flaws that would limit the life the product would require additional time to understand and solve. Time that just was not available.
The less he knew the better the development plan (fictitious that it was) appeared.
An Organizational Fear
We set up systems and processes within organizations to facilitate decision making. We attempt to provide just the right information at the right time to permit moving forward with a project.
At times we learn about field failures that may or may not lead to major warranty expenses. The ability to recognize, understand, and report the problem all too often relies on individual heroism. The organizational system tends provide a local focus and avoid spotting and dealing with reliability issues.
All too often the customer service team, dealing with product failures on a daily basis, does not delve into root cause analysis or time to failure tracking. They focus on helping the customer get working again or ship them a new product.
All too often the operations team focuses on yield improvement without paying attention to the latent defects they are shipping with each product.
Likewise the development team focuses on delivering new designs on time and within budget with little more than cursory review of the few field issues they have heard about at some point.
It is rare that an organization establishes the appropriate systems to encourage the identification, understanding, and systemic resolution of failures. Failures are bad and we don’t like to talk about bad things.
I do not think ‘reliaphobia’ is a condition that our medical community will offer remedy. It is up to us to identify and cure the condition.
Oh, on MTBF. I suspect it is that easy to use, no need to understand, metric that does a fine job hiding the problems and limiting understanding that supports the fear of reliability condition. If your organization uses MTBF, it may be a coping mechanisms that they are thus ‘doing’ reliability.
Setting up systems, reporting, education, and encouragement all seem to reduce the fear of reliability. A steady dose of solving problems and getting great results is another sure path to curing the condition.
Is the fear of reliability rampant in your organization? What steps are you taking to cure the local condition?
Raghu Kashyap says
Fear stems from the fact that Reliability is knowledge based. Acquisition of knowledge is through analysis of information , convert that structured data into knowledge through diligent application of “mind”. Application of mind is not a disorganized / random process. A cultured process is like/similar to devotion/ Bakthi which involves a structured learning based on professional learning & not (repeat not)subjective( application of physics is rare) hypothesis. Yet another likely reason is reliability is a predictive process & not one of certainty, Fred .
Thanks, Kate— thee made my day!
Biagio Agostinelli says
Your “Fear of Reliability” article cracked me up! Lol. Unfortunately, over the years, I have also experienced such unpleasant twilight zone experiences as you have described, although more subtle. To me, this is a demonstration that Reliability efforts must be blessed by company top leaders. If not, then every employee below the chain of command will acquire Reliaphobia because:
time has not been budgeted into their projects by upper management to account for the extra time needed to conduct reliability analysis.
Conclusion: reliaphobia is a contagious disease that can be spread by Top managers who do not believe in the benefits that reliability can bring to the table.
Fred Schenkelberg says
Hi Biagio, thanks for the note. Yes, reliability has to be part of the organization’s culture, including the executives and top managers/leaders. cheers, Fred