Failure modes and effects — Engineering, 14–17 years
A structured way to ask how a part could fail, what would happen, and what deserves attention first.
Think before it fails
For each part of a system, engineers ask three questions: how could it fail, what effect would that have, and how might we notice it? This turns a vague worry into a list that can be examined. The method is often called FMEA, short for Failure Modes and Effects Analysis.
Why make the list
A system can look safe when each part is considered separately, yet one small failure may create a serious chain of events. FMEA came from the need to find weak points early, when changes are still possible and cheap. It gives a team a shared way to discuss risk instead of waiting for an accident.
A bicycle light
Consider a rear bicycle light. Failure mode: its batteries go flat. Effect: the rider is harder to see at night. Detection: the light becomes dim, so a low-battery indicator could help. Action: use a battery warning and make replacement easy. The list links a physical fault to a useful design response.
Only listing broken parts
A beginner may list “battery failure” and stop there, because the battery is the visible problem. That is a reasonable first step, but the important question is what the failure causes in the whole system. A flat battery in a toy and one in an emergency beacon do not have the same effect.
Finding priorities
FMEA is used for medical devices, cars, software services, food equipment and spacecraft. Teams can mark failures that are severe, likely or hard to detect, then work on the most concerning combinations first. It is most useful as a disciplined conversation supported by evidence, not as a guarantee that every failure was imagined.
Keep exploring
Other languages
Loading MyLeoNes™…