You're right. But then everyone who wants their systems worked on starts attributing "business value" to each change request. So now you have a huge backlog of changes with made-up points, and each manager says their change is more important than the other's.
The only way to get any traction is to get VP level people involved to prioritize which systems to work on. But some VP level people might see you reaching out to them as incompetence - "you can't prioritize your own work?! What did I hire you for!", etc.
At the end of the day it's really about the people in the org and how altruistic they are when considering the constraints of the IT dept.
The only way to get any traction is to get VP level people involved to prioritize which systems to work on. But some VP level people might see you reaching out to them as incompetence - "you can't prioritize your own work?! What did I hire you for!", etc.
At the end of the day it's really about the people in the org and how altruistic they are when considering the constraints of the IT dept.