Are there actions that should be recorded as part of ITSM change management that aren't always?

Enterprise & IT Service Management (ITSM)Change & Release Management

830 views2 Comments

Sort by:

Sr Community Manager in Travel and Hospitality3 years ago

Andrew Nebus Moez Ayadi 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!

Director in Manufacturing3 years ago

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….

Content you might like

Which of the following areas is your technical organization looking to transform most for 2022:

Improving delivery speed of IT output11%

Modernizing older IT systems38%

Increasing stability of IT systems25%

Implementing more consistency in IT delivery and support15%

Enabling more innovation within the IT teams6%

Maintaining control over IT spend2%

Other

View Results

Would you describe your current IT operating model as more process-driven or service-driven?

Process-driven44%

Service-driven54%

Other (comment below)1%

View Results

What modern KPIs would you recommend to measure people and infrastructure performance in Service Desk?

Who owns Communication in Network vs. Security Incidents? Best Practices & RACI Guidance Needed In many organizations, Network and Security teams both play a role in incident response, especially when firewall or SASE issues impact network performance. When an issue is first diagnosed by the Network team but determined to be security-related, who should own the ongoing communication, resolution updates, and root cause reporting? I’d love to hear from the community: • Are there best practices, ITIL/ITSM frameworks, or RACI models that clarify ownership? • How does your organization handle communication handoffs between Network and Security teams?

Our IT department is refreshing our SLAs and KPIs for Incident Management. I would like to know who is a recognized authority on industry averages for IT Service Management processes for the service desk? Below are examples of what I am looking for an industry average on. P1 95% resolved within 4 elapsed hours P2 90% resolved within 8 service hours P3 85% resolved within 3-5 days P4 85% resolved within 28 days