When is a problem a problem?

51! - This is the count of the word “problem” in the latest release of the Automotive SPICE? PAM v4.0. It seems to be important.

Hence the question is, when is a problem a problem?

Some characteristics of problems are specified in the PAM, such as submitter or critically. Anyhow, neither in the PAM nor in any dictionary, I could find an appropriate definition of the word “problem” and how it is differentiated from non-problematic things.

In ASPICE assessments typically defect handling is shown for problem management. Well, a defect is something unwanted. It might cause problems to the usability of a function. Anyhow the nature of processes, is to ensure that all regular activities become unproblematic! So, how can a regular thing such as defect correction, become the reference for problem resolution management?

Well, if you ever faced a showstopper defect a few days before SOP, I’m sure we would all consider this defect as a problem. While the malfunction itself is not the problematic element. It is the limitation of time, space or resources that makes the difference. And even further, the difference to all other defects is, the irregular element in this scenario.

In terms of time and cost, companies and projects would take a lot of benefit from a process and a training, that enables teams to handle irregular situations, sovereign and autonomous! Personally, I recommend to have a kind of a “plan B” in the drawer and to never need it, rather than to need it but not to have it?

Mind blowing reminder I found while I was writing this article: the Greek source of the word “próblēma” is the idea that a problem is easier to solve, if it is defined and described.

Stay tuned!