Only an engineer under severe pressure would snark about gravity to leadership about a bridge collapse, though. A good engineer would challenge the missing context instead. If you ask an engineer “why did it collapse” without the correct statement of context, then of course you’ll get an answer you dislike, because they’re going to (as is human norm) assume their own context rather than the none you provided. Instead, ask better questions. “Are we liable for this collapse?” is usually what I would expect a corporate leader to want answered, and so as a senior engineer I would reply to the context-free question “why did it collapse?” with a context clarification request: “Are you asking about the immediate cause, about the root cause, or about which company should be held accountable?”. There’s nothing quite like watching an exec choke out an admission of interest in legal liability rather than engineering factors after interrupting an engineer working on the collapse who knows full well not to write checks that will get them cashiered :)
All we have to do is apply this same parable to the "engineering" of organizations, and you'll be on the right track.