As a data architect, I am finding a bigger and bigger part of my role is bringing other group's DIY POC and now mission critical operations into our enterprise-level workflow tools. It is not exactly stated as such, but when those people are not included in development roadmaps and timelines, it gets ugly quick. I pushed back at first and adopted a pessimistic view of development (read - lock down the process workflows for sanity's sake) . However, "making things better" has been my main driver for all of my tech career. Since these projects weren't going away, I began to see half our group's purpose is actually to enable these projects to be converted to the enterprise, and therefore to build into the design ways to make this easier for the operations people using the new tools. They were used to making changes to their Access database and Excel files/formulas as desired and needed. For these people, this meant figuring out how best to allow for this, for them to be able to make changes in business rules on the fly, along with rule change tracking of course.
As far as our jobs going away, I think there will always be a need for humans to be involved. The big push in automation has not resulted in a huge amount of downsizing in my view. It is, however, highly recommended for everyone in technology to maintain their plans to stay current, and even to continue to move up the food chain. Adopt the mindset of always learning and never stopping to learn due to age or status or capability.