Ya but if you're really honest with yourself, did you learn what you needed to "drive decision making across the org" in Uni? You may have I guess, but it seems like you really only get that confidence or those skills after you start doing whatever it is that you do. It's hard to imagine how anything I learned or could have learned in Uni, would have at all helped enough with any of even the least complex tasks once getting started professionally, that I didn't learn in technical college or on my own prior. That said, I wasn't a FAANG go-getter trying for a spot that required complexity analysis or whatever, or a game developer with a necessary background in maths and memory. I feel like the stuff you learn in Uni that's valuable, becomes encountered in only some special cases, and even then there's probably better environments for actually learning it rather than just figuring out how to test well on the material.

I personally found the humanities and hard sciences a bit more compelling compared to any CS courses; viewing the CS testing and teaching methodology through the lens of having already been in industry, it pained me more than it might have otherwise had I been a naive impressionable student with no professional perspective. Sitting there writing out an ADT in Java with a pencil in a not large enough physical space, thinking "why did I decide to do this crap again?", but also not being able to respond to the artificial pressure of the classroom with a fabricated stress response.

I think I agree with a lot of what you said - non-CS classes can be fundamental to learning some job skills (like writing, communicating, and deep thought). However when I say that it helps me drive decision making, I mean that I am literally more confident in what I'm saying because I'm reasonably sure of the boundaries in my knowledge.

For example, I went to grad school and studied databases. On that topic, I probably know more than anyone I work with; so if I put forward a proposal that is related to DBs in any way, I can be quite sure that there are no surprising edges that will come back to bite me (i.e. no one will come along and say "well what about this?", at least from a technical perspective). That's because I know what I know, and there are things I don't know, but I also feel like I know what those are (e.g. I don't feel as comfortable with low-level programming, mostly because I actually skipped a machine organization class and never picked those skills up separately).