Back to publications

Quality Guide publication

Three practical tips to make PFMEA actually work

Three practical ideas for turning PFMEA from a formal file into a useful risk-management tool directly connected to the real process.

Three practical tips to make PFMEA actually work

There are two kinds of people:

1. Those who, before a trip, check:
- the fuel,
- the tire pressure,
- whether the jack is there,
- and whether the spare wheel has not turned into a shelf for random junk.

2. And those who say:
"It will be fine somehow."

Until something goes bang.

A spare wheel is not there because somebody had too much free time. It is there so that when something fails, you do not stand on the roadside improvising.

FMEA works exactly the same way:
it does not believe in fairy tales that the process "will always be OK";
it helps you understand what can realistically fail before it actually goes BOOM.

So what can you do as early as tomorrow to make PFMEA a real tool?

1) Do a "standing FMEA" directly at the process
Time: until your legs hurt.

Not in a meeting room. Not in Excel. At the process itself - observe, observe, observe.

Minimum team:
- operator
- maintenance
- quality
- process engineer

Effect:
you see things that are not in the paperwork, but are present in reality.

2) Analyze workarounds - that is where the process is calling for help
Do you know the sentence:
"It works here... you just have to handle it every day."

That means everyone knows where the problem is, but officially "nothing is happening."

How to collect it quickly?
Ask one question:
"What annoys you the most here and what extra things do you have to do just to make it work at all?"

Then:
- write down the 5 most common workarounds,
- add them to PFMEA,
- think about how to prevent them - not how to hide them better.

Effect:
you bring problems into the open that already exist, but no one wants to name.

3) After a complaint, make an Ishikawa... and transfer it to PFMEA
After a complaint, we often make an Ishikawa diagram, draw great conclusions... and then that wisdom lands in an 8D report and disappears into a folder.

Most often, only one selected cause ends up in PFMEA - the one that feels the most urgent today.

But the Ishikawa shows the whole map of risk for a given problem.

The best upgrade:
transfer the Ishikawa into PFMEA.
If you are already listing factors that can create chaos, then keep them under control before they return in the same complaint, only wearing a different costume.

Effect:
PFMEA becomes the memory of the organization, not just a completed file.

FMEA is not there to scare people. It is there to make sure the process arrives safely - even when "something goes wrong."

Summary:
Lack of PFMEA is a bit like driving without a spare wheel: at first everything feels "fine"... and then you pay for that attitude with real money.

Open the publication on LinkedIn Back to the homepage