This slide was presented with a verbal talk track, and anyone who can't handle focusing on the topic because the slide is boring shouldn't be in a position of responsibility.
But you are right, most engineers would consider that reasonable, while complaining about the "muggles" that just don't get it.
As a Software Architect, one of my main responsibilities has been to take information presented like above and turn it into something that non-technical people can digest.
Being able to express a complex concept in simple terms is an invaluable skill.
Second, that's irrelevant to my point that the engineer is responsible for communicating, not just figuring stuff out. You cannot say "if you don't get it, that's your problem" when their not getting it means people die.
You can’t force someone to think but you can force a lot of people not to, or you can make it difficult to avoid. It’s worth investing the energy into stacking the deck the right way.
The principles of that slide apply to a lot of other circumstances.
So on the remote chance you're not just trolling: If you're doing anything safety critical, please quit your job before you kill someone. You vastly overestimate human's (including yours) ability to process information. I am being 100% sincere.
Then you shouldn't be in charge of communicating highly technical subject matter to decision makers, especially if lives are at stake.
I can be kind of a pain in the ass when it comes to details so I’ve worked on a couple such projects. It’s sobering, but also I think, “better me than” half a dozen corner cutters at my last two jobs. They could do much worse.
That said, I stayed on a commercial aerospace project about 14 months after I didn’t really want to be there because people kept saying the wrong things in meetings and thinking they sounded right.
I am consistently ranked as both one of the best engineers in my company and one of the best communicators. I would never make a slide like that for any audience. It's shit writing for non-engineers and it's shit writing for engineers, too.
You have got to get over whatever this hangup is about "PhD level analysis". That phrase doesn't mean anything.
While it does not wash the responsibility of the executives, the engineers have also the responsibility to be clear in their communication
If you can't effectively communicate how the results (or lack of results) of your research will impact the outcome of a high-stakes space mission you have no business being in that room from the start.