framer
No thanks, it may be gratifying for you to liken it to your particular area of expertise but it is not really relavent (sic).
I find the use of the word "gratifying" somewhat offensive and comparing fiscal loss with the loss of human life doesn't deserve comment.
Whatever.
It doesn't, however, reduce the relevance of the parallels in the processes.
Do you think perhaps that with 30,000 odd hours of flight experience on the flight deck that day, that the concept of risk management wasn't completely new to them?
Risk management during normal operations in commercial aviation isn't left to the operating crew. It's integral to aircraft specification and defined in operating procedures.
I'd submit that - in performing tests only permitted between FL100 and FL140 at FL30 - the crew ventured into an area where (despite their 30k hours of flight experience) they weren't able to adequately assess the risk level of their actions.
Here's another one for you:
Software develoment has a "frozen zone" - a period in which product stability has been achieved and is not subjected to ANY change/risk.
Where's the parallel in your world? Approach phase, perhaps.