> 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.
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.