ITIL ITIL-4-Foundation - ITIL 4 Foundation Exam

The purpose of incident management is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. Incident management can have an enormous impact on customer and user satisfaction, and the perception of those stakeholders of the service provider.

https://www.bmc.com/blogs/itil-incident-management/

In order to be aligned to customer outcomes and expectations, SLM requires focus and effort to engage and listen to the requirements, issues, concerns, and daily needs of customers:

Engagement is needed to understand and confirm the actual ongoing needs and requirements of customers, not simply what is interpreted by the service provider or has been agreed several years before. ITIL4 refers to value as being co-created, since it needs the input and validation of customers.

Listening is important as a relationship-building and trust-building activity, to show customers that they are valued and understood. This helps to move the provider away from always being in ‘solution mode’ and to build new, more constructive partnerships. Each customer is unique, and the service provider must not have a one-size-fits-all approach.

The activities of engaging and listening provide a great opportunity to build improved relationships and to focus on what really needs to be delivered. They also give service delivery staff an experience-based understanding of the day-to-day work that is done with their technology, enabling them to deliver a more business-focused service. When the customer is engaged and listened to, they feel valued and their perception of the service and service management activities improves.

https://www.bmc.com/blogs/itil-service-level-management/

You need to use all of your resources as effectively and efficiently as you can. This means that you should automate wherever you can, and use people only for tasks that can’t be automated. It also means that you need to think carefully about what you can automate and about the circumstances where only a person will do; and about simplifying those processes you do decide to automate to eliminate wasteful or inefficient steps.

You should always optimize the work BEFORE you automate it, as automating something that is inefficient or ineffective may just result in you doing the wrong thing faster!

https://www.sysaid.com/blog/itil/the-7-guiding-principles-of-itil-4-practical-advice-to-help-you-make-decisions

The purpose of the monitoring and event management practice is to systematically observe services and service components and record and report selected changes of state identified as events1. This practice helps to identify and prioritize any issues or opportunities for improvement in the delivery or support of services2. The other statements describe the purposes of different practices: incident management (A), service request management (B), and change enablement (D)3. References: ITIL Foundation - ITIL 4 Edition, page 14; ITIL® 4 – A Pocket Guide, page 31; ITIL® 4 Practice Guide: Monitoring and Event Management, page 7.

Effective incident management often requires a high level of collaboration within and between teams as this can facilitate information-sharing and learning, as well as helping to solve the incident more efficiently and effectively. There may also be a need for good collaboration tools so that people working on an incident can work together effectively. One technique that takes advantage of collaboration is termed swarming. This brings many different stakeholders together to work on the issue. Management of incidents may require frequent interaction with third party suppliers, and routine management of this aspect of supplier contracts is often part of the incident management practice.

https://www.bmc.com/blogs/itil-incident-management/