Are there actions that should be recorded as part of ITSM change management that aren't always?
Director in Manufacturing, 1,001 - 5,000 employees
We recorded everything. Even the server shutdown on ERPs we archived. We would have tickets for when it goes read only, when we shutdown the app, when we powered down. And finally even for removal from the rack. I can’t think of anything we didn’t create tickets for….Community Manager (IT and InfoSec) in Travel and Hospitality, 5,001 - 10,000 employees
based on your recent activity on GPI I thought you might be interested in this question on ITSM change management. Would love to know your thoughts!CIO in Finance (non-banking), 1,001 - 5,000 employees
I highly recommend to log and track any change in ITSM.Content you might like
Director of IT in Healthcare and Biotech, 501 - 1,000 employees
Overall fit of the provider's services is key in any recommendation when selecting one of the big 3 clouds for any organization. Multi-cloud is significantly more difficult than most companies realize, and selecting a ...read moreYes35%
Yes, but not enough, we want/need to ramp up38%
No19%
No, but I expect this will change soon6%
658 PARTICIPANTS
TCO20%
Pricing25%
Integrations20%
Alignment with Cloud Provider7%
Security11%
Alignment with Existing IT Skills4%
Product / Feature Set7%
Vendor Relationship / Reputation0%
Other (comment)1%
791 PARTICIPANTS