Skip to main content

Effective and Efficient Incident Response – Rethinking the way YOU work!

Learn more about new ways to do work! Explore DevOps, ITIL, SRE, XLA’s and more!

Silos are not uncommon, but when you silo the service desk from second and third-tier support staff, you likely have a recipe for pain. An ineffective incident response system within the organization is painful and disrupts the entire organization, especially the customers. We must shift the way we think and work to stabilize and improve the situation.

One organization felt that they had a grip on service desk and incident management, but they blamed the subject matter experts for breaches to Service Level Agreements. The blame game is always detrimental. Their process consisted of the service desk agents receiving the incident, performing the initial triage, and then forwarding it to the subject matter expert based on how they categorized the incident. Sound familiar?

Sometimes we pass tickets to and fro, get everybody and their brother involved, wait on email responses, and create chaos that frustrates every stakeholder. When this happens it is not uncommon for bouncing tickets to get dropped into the infamous black hole with no fix, no response, and no communication to the users.

This is toil on steroids and sadly not uncommon. From an end-user customer perspective, their opinion of the entire organization can be based on the lack of or bad service they receive at the service desk. Social media lights up and brand recognition is damaged all due to the ineffective incident response system. In come new ways of thinking and working.

Consider new techniques like “swarming”.  

Today, when there is a major incident, “all hands on deck”, all stakeholders are immediately contacted and use collaborative tools to very quickly (with humans and Artificial Intelligence) analyze the outage and determine which experts should take this on.
NO MORE PASSING tickets!

With swarming, once the ticket is resolved a blameless post-mortem is performed. This new way of doing work shatters the silos, creates a built-in synergy across the teams and a culture of "it's okay to fail". In order to change the way, we work we must change the way we think! What are your out of the box ideas to “rethink the way YOU work”?

To learn more; consider the following ITSM Academy Certification courses:


Comments

Anonymous said…
been awhile since I dove into an ITIL pub, but did look at ITILv4 recently and saw this in 5.2.7 Monitoring and event management section....

"Figure 5.22 shows the contribution of monitoring and event management to the service value chain, with the practice being involved in all value chain activities EXCEPT PLAN:" ...

I admittedly have not had my nose in the ITIL pubs for awhile and so there may be other guidance that I'm missing or I may be a bit 'rusty' :) BUT...

unless the monitoring team is represented planning they will have NO HOPE of optimizing a portfolio of monitoring tools....seems to me if you're going to have a food-fight, you might as well have it sooner than later....allowing capacity and performance to dictate 'observability' without monitoring and event management's involvement doesn't feel right to me...

what am I missing?
ITSM_Lisa said…
Great Observation! I agree that there should be a "Plan" for every practice and that includes Monitoring and Event Management. There are plans at many levels including Strategic, Tactical and Operational. The text is not altogether clear, but my perspective is that it appears the diagram you are referring to is showing the relationship once an event is planned, configured, and instrumented for automation in the tool.

This looks to be the route that that event takes as it traverses through the Service Value Chain activities. Therefore this is the value chain journey of an individual type of "Event" rather than the "Plan" for the Monitoring and Event Management Practice.

Hope this helps.

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service Offe

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the