"... and speak to the aviation industry..." I'm not too sure about that.
On Quantas flight 32 the automated problem system "ECAM" generated errors in 100 checklists (out of a total number of checklists of over 1200), which had to be dealt with sequentially. Apparently that took all the time and attention from one of the flight crew until it was completed after many minutes.
"While automation and complex systems can indeed make life/tasks much easier, there are also quite a few problems associated with these systems. On Qantas Flight 32, the pilots claimed that once the failure message had been received, checklist after checklist after checklist had consumed the 55 minutes it took for the aircraft to resolve the failed engine issue. Too many checklists on the automated system had congested the pilots' time. Within that 55 minute timeframe, the aircraft could have been consumed in a fireball, killing all 500+ passengers and crew. In addition, the pilot claimed that he had to check off every single checklist before moving onto the next, which also congested a lot of his crucial time. "
So it looks like there still is a long way to go before they get the UI for aviation where it needs to be.
Reference:
https://en.wikipedia.org/wiki/Qantas_Flight_32
https://stonybrook.digication.com/amrit_singh_esg201/Qantas_32_Accident_Reflection