I would compare this to asking a dev team to support a big code base without embarking on a major redesign or re-engineering.
It's hard to keep a good (confident, ambitious) team from re-engineering. All the same dynamics apply: In your mind the disadvantages of change are small because you don't know them, but the advantages are large because you planned them. Making change gives you more control over your fate because you are executing your own plan as opposed to staying the course. Finally, how do you keep people motivated to show up every morning if you don't have a vision for change in the future?
I don't think its that different for managers and engineers. There's a lot pushing people to try something, even if the objective odds of success aren't great.
It's hard to keep a good (confident, ambitious) team from re-engineering. All the same dynamics apply: In your mind the disadvantages of change are small because you don't know them, but the advantages are large because you planned them. Making change gives you more control over your fate because you are executing your own plan as opposed to staying the course. Finally, how do you keep people motivated to show up every morning if you don't have a vision for change in the future?
I don't think its that different for managers and engineers. There's a lot pushing people to try something, even if the objective odds of success aren't great.