Not necessarily. I think the key is not to take a job that is defined as being a technical resource. Because as long as you do, you will be a member of the techie caste that exists to be plugged in to the existing cultural problems.

What you need to do to break free is simple, but not necessarily easy - get a job with no technical requirements, but which has the potential for technical/cultural solutions.

This is the direction I eventually went in, and one thing I find interesting and notable is that even after solving all sorts of things through programming, people aren't letting me withdraw into just being a programmer - which I think is a good thing. Once I write a program to do something, then I have to document it, then I have to train other people to use it, and then we have to develop contingency plans to do without it if I should be hit by the proverbial bus. And maybe figure out how to get another developer up to speed to maintain it. If I were an actual programmer/developer, then all the different jobs would be pretty much left to other specialists and managers.

Maybe some people would say, just join a startup or make your own, and you will become more well-rounded, but I'm not swamped with offers to do that and have worked in larger organizations.