For a lot of software in megacorps, it makes more sense if you look at 'trained in X' as a kind of magic spell that has no real relation with the ability to do a job.
If the end user says: I have no training in X, that mostly means they don't want to work with X or don't want to accept extra workload related to X. The company then provides training in X, another magic spell meaning money was spent so the company officially did something, and the excuse about not being trained won't work anymore. Blame has now been shifted from the company to the worker or even the end user. So training being expensive has better optics.
Big tools like MSOffice have the ability to be put in hiring contracts: Everyone is assumed to know how to use it, so the company is allowed to deny the no training excuse without spending money.
Actual training for the whole company is more like a networking event, and if you ignore the trainer and read the manual or watch some youtube, you may actually learn what you're supposed to. Once in a while, you get a trainer who knows what they are talking about. But all that is secondary.
> If the end user says: I have no training in X, that mostly means they don't want to work with X or don't want to accept extra workload related to X.
This has largely been my experience working in IT as well. I think folks in the tech world take for granted how "normal" continuous learning is for us, and how undesirable it is for others in the workplace. Your average office drone very much does not want to learn something new. They want to use what they always have, and keep the same workload.
Even just attempting a switch from Windows to macOS, when their workflow is almost entirely a web browser, damn near caused a full on worker revolt at one organization I worked at. Training didn't fix it, because the desire to learn wasn't there in the first place.
That's the kind of inertia that needs to be overcome for something like open source adoption at the end-user level. It's comparatively simple for the back-end to transition, but without an already willing user-base, the front-end average office worker is not going to achieve the same level of productivity for a really long time.
> Big tools like MSOffice have the ability to be put in hiring contracts: Everyone is assumed to know how to use it, so the company is allowed to deny the no training excuse without spending money.
I would claim that if you haven't worked in the finance or insurance industry (or some related industry) for quite some time, you very likely don't know how to use Excel (I have a feeling that a similar points holds for Word and Powerpoint with respect to some industries, but I think for these applications this phenomenon is a little bit less pronounced).
Indeed, I'd claim that most books about how to use Excel are simply crap. To just give you a glimpse how to use Excel, here some internet classic on this topic:
You Suck at Excel - Joel Spolsky
https://www.youtube.com/watch?v=JxBg4sMusIg
Really understanding Excel is life task, similar to really understanding modern C++.
If the end user says: I have no training in X, that mostly means they don't want to work with X or don't want to accept extra workload related to X. The company then provides training in X, another magic spell meaning money was spent so the company officially did something, and the excuse about not being trained won't work anymore. Blame has now been shifted from the company to the worker or even the end user. So training being expensive has better optics.
Big tools like MSOffice have the ability to be put in hiring contracts: Everyone is assumed to know how to use it, so the company is allowed to deny the no training excuse without spending money.
Actual training for the whole company is more like a networking event, and if you ignore the trainer and read the manual or watch some youtube, you may actually learn what you're supposed to. Once in a while, you get a trainer who knows what they are talking about. But all that is secondary.