It's more difficult in slow-moving enterprise environments. In our environment, the time from someone saying "we should do this" until it's in production can e

It's more difficult in slow-moving enterprise environments. In our environment, the time from someone saying "we should do this" until it's in production can easily be 3 years. Then, add the lifetime of use which can span even decades (depending on the application). Long-term managers and architects have seen many, many technologies and methodologies come and go, and treat claims of "you better change that system quick!" with skepticism (doesn't mean it isn't true). Four to five years of life for an enterprise code base is a blink of an eye. If I proposed a major framework/foundation change for a four year old application, I'd be getting some unpleasant looks.