3 ms·
This is a very common phenomena that as Quality Assurance you specifically have to work around when talking to regulators, and there are in fact, white collar c
by salawat 7y ago
This is a very common phenomena that as Quality Assurance you specifically have to work around when talking to regulators, and there are in fact, white collar cultural norms in place which shape the way most corporations I've worked at talk about potential regulatory risks.
For one thing, if you bring up any questions regarding an issue at all, the preferred medium of communicating it until a decision is made tends to be direct person to person with no electronic paper trail. (This insulates the company from getting caught out by E-Discovery in case of legal troubles).
Secondly, there's the practice I call anchoring. This is where you go to the regulator with a very narrow, refined question looking for an answer, explain why you think it's a good idea, and hope they don't think too much into it before saying yes you can do it. If it works, you have a document stating the regulator told you it was okay when you asked. To prevent this, you have to go to your regulator and give them a high and wide view.
A) What is the problem
B) What are the relevant regulations impacted
C) What additional risks are created with both answers
Businesses can be a bit squirmy when engineering folks start getting too chummy with compliance. I know I've found a good one when I don't get funny looks when asking if something questionable sounding has been run passed Compliance.
Everything I've read in this investigation reeks of anchoring toward the FAA. Especially given the whistleblower testimony as reported in the 60 Minutes Expose on the MAX.
[1]https://m.youtube.com/watch%3Fv%3DaO7_indbfME&ved=2ahUKEwje2sfB84njAhXULc0KHcwuCrUQwqsBMAB6BAgHEAU&usg=AOvVaw2APCLXMqKKxa5mxQOnsmvo https://m.youtube.com/watch%3Fv%3DaO7_indbfME&ved=2ahUKEwje2...