It's also just indicative of differing expectations. IT and programming evolves at an incredibly rapid pace. Technically proficient people are used to continually shifting tools, best practices, and thought paradigms. If there's a way to drastically streamline or improve something, it's basically second nature to choose that solution because you're going to have to learn something new sooner or later anyway.

But this is the exception, not the rule. Digital marketing is the only other area I can think of that also has a rapid pace of change, and coincidentally is also the most exhausting area I've done work in because of the amount of ramp up it takes to relearn the landscape if there's even a small gap in engagements. Most other business functions are slow changing, and workers in those functions resist drastic change simply because drastic change isn't part of their usual expectations for their working environment. Small, incremental changes are a lot easier to work in. As long as each incremental change brings enough benefit to be worth it, it's easy to win people over. But a completely new process will have just as many warts (whether training-, process-, or expectation- based warts) as their existing process, and just replaces one set of problems with another. So they'll resist it.