2 ms·
The aviation industry is actually pretty notorious for tight lippedness given that it's a sector that has higher than normal cross-section with National Securit
by salawat 8y ago
The aviation industry is actually pretty notorious for tight lippedness given that it's a sector that has higher than normal cross-section with National Security concerns.
A lot of information that has come out has likely been lead to by the fact there are people who can tell others where to look, and what questions to ask who aren't bound by any sort of an NDA, or any concerns of getting blackballed by the industry.
That's my guess anyway. A little bit of knowledge, speaking the lingo, and an independent perspective goes a long way toward piercing through the veil of institutional secrecy. The truly arcane is very infrequently the root cause of a severe problem in my experience. Almost every high severity problem results from the seed of problems endemic to the culture that has been architected in a workplace.
If you have a culture that discourages costly non-value adds (and is daft enough to consider Quality/Safety Assurance a non-value add), you're going to have blind spots that will come back to haunt you. Engineers may not find it a naturally comfortable course of action to speak up and hold people accountable, right down to requiring a manager to deliver to you a signed piece of paper swearing that X or Y will not happen because reasons, and it is the decision of <insert manager's name here> that this path of inquiry is not productive enough to follow, for you to then pin your rebuttal to and send up formal chains of authorization; creating that dastardly paper trail that makes everyone squirm.
I don't even pull that one out unless it is something particularly egregious, and at that it would usually only be after getting the ball rolling to bring about a culture change to undo the myopia that has clearly set in already to allow things to degenerate to that point.
Nobody wants to be the bad guy, or think they are working for the bad guy, which makes it d difficult at times to assume the mantle of That Guy, but that's where your people who really do Quality thrive. It doesn't make you super popular or get you invited to fancy parties, but if you stick to it, you'll become one of the most positive forces for change wherever you are.
Until you run into the Liar up the chain of command of course. Then the politics commence, and victory/positive outcomes are not guaranteed.
And Quality people seldom have golden parachutes.
- bumby 8y agoI think it's important to institute a formal method to document these decisions. Too often there's a diffusion of responsibility/accountability. If there are specific processes being deviated from, they get documented along with the associated risks/mitigation and the approach gets accepted by the appropriate authority. If there's risk-documenting process in place, nobody has to feel like a bad guy for forcing someone to put their name on the dotted line. In my experience, this tends to force people to really think about the risks they are taking and, at the very least, make a more informed decision. Of course, this requires requirements to be there in the first place to deviate from; it requires a managed process. For example, if Boeing categorized MCAS software as 'critical' they may have a process that says any critical software requires redundant inputs. If a business decision was made to avoid redundant inputs on base models, a manager should be signing off on this documenting the associated deviation/risks and why they are acceptable. Woe be the manager who signs off saying they will accept a risk of a plane crash to up-sell a redundant sensor.