It is a bit like banking and these "rogue traders" who spend a billion dollars. They are at fault certainly BUT more so it is the banks fault for having such lax measures that they had access to this much money.
It is a bit like banking and these "rogue traders" who spend a billion dollars. They are at fault certainly BUT more so it is the banks fault for having such lax measures that they had access to this much money.
No matter how you slice it, this is a management problem, and a cultural problem. It is not an individual responsibility to ensure quality. If it is left to an individual, then things like this happen out of sheer statistical probability. The only thing you can depend on is human fallibility, so your systems should be designed for it; they should expect it, more than anything.
We should all look at quality as a systems, management, and fundamentally cultural pursuit.
Sadly, the individual getting the brunt of all the blame here will only worsen the cultural and management factors that caused it in the first place. Future employees will fear individual retribution, and will make rash, illogical, uninformed decisions in the future out of fear. This, too, will not be their "fault" but the fault of the company, the management, and the systems around them.
Deming. Look him up. There's a reason this does not happen in Japanese car companies. There's a reason that when it does, individual employees are not blamed. The reason is critically important to the success of American manufacturing in the future.
I used to inspect amusement rides for safety when I was in college. Occasionally there would be a defect that would arise that would make me feel it was not as safe as I thought it could be. Managers and owners of course would not want their ride shut down on a busy summer day and would pressure me not to close it but I did not care. I knew if children were hurt or killed I would feel horrible, and be the guy taking the blame or criminal penalty for negligence.
So if you are an engineer for some safety critical system never bow in to management pressure as it will be viewed as 100% your fault when something goes wrong. It is not all this engineer's fault as people have pointed out, but when you put your name on the line approving something it is then your responsibility.
The process and company structure pretty much made it impossible for the the type of situation outlined in the article to occur.
Just as a 30,000 ft overview of the process... imagine a place where every little change required a minimum of 4 signatures, engineer, QA engineer, Head of QA/Reg, and CEO. This allows not only QA, but also the FDA to determine precisely who was responsible for each change. Imagine further that the signatures have to be on paper, and that giant mass of paper documentation has to be submitted to the FDA, along with mountains of other documentation as well as the software itself, for approval. (But everyone understands that it's also submitted so that the FDA knows who to throw in prison if serious bugs crop up.)
The situation outlined in the article should be STRUCTURALLY impossible as well. At the startup I worked at for instance, build engineering was under QA. This meant that a development engineer could not give the build team a build directive. Only the head of QA/Reg could do that. Also, the head of QA/Reg didn't report to the COO or CFO or Chief Counsel or anything like that, she reported directly to the CEO. As well, she was a frequent contributor at board meetings. There was just no way to pull an end around on her.
That's just a rudimentary outline of the controls we had in place at that startup. Believe me, it actually got a WHOLE lot more restrictive than what I've outlined, but the other stuff is not important to the point I'm trying to make.
And that point is this...
While I realize that for cars the safety standard is probably lower than it is for medical imaging and RTP packages, you would think GM would have those rudimentary controls in place at a minimum ???
Such motivation might come from the fear of losing your job.
But, really, isn't an "engineer", someone pretty LOW in the hierarchy ?
I mean, that's kind of the point, the better the structure and processes... the higher up you will need to go to subvert them. In the case of GM... the processes were so poor that you didn't need to go beyond the engineer level to subvert them. (Assuming the information in the article is to be believed.)
To anyone who read this article and thought what the GP thought, consider that the value of any "thought worker" is inherently tied to the amount of trust you're able to place in them. This is why as an engineer the more you get paid, the more accountability you have.
If you ever work for a place which suffers from institutionalized distrust for its employees you should run. Run very very quickly in the opposite direction.
according to the article, this blameless paragon of virtue deliberately hid his actions.