problem managment yields service improvementv2
DESCRIPTION
walking a process through its life cycleTRANSCRIPT
![Page 1: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/1.jpg)
1
Problem Management Yields Service Improvement
![Page 2: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/2.jpg)
2
“Why are we in business? To help our customers
achieve their goals. Simple as that.”
John Varley, Group Chief Executive Barclays
![Page 3: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/3.jpg)
3
SUMMARY
•Approaching process implementation
•Moving from incident to problem management
•4 steps in problem management
•The next step on the evolutionary path
•The process is working why change
•The process is working why we must change
•Processes need people
•Hidden dangers
•Overview
![Page 4: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/4.jpg)
4
ITIL DEFINITION
A Problem
A cause of one or more incidents, the cause is not usually known at the time a Problem record is created, and the problem management process is responsible for further investigation.
The Problem Process
The process responsible for managing the lifecycle of all problems, the primary objectives of problem management is to prevent Incidents from happening and to minimize the impact of incidents that cannot be prevented.
![Page 5: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/5.jpg)
5
SOMETIMES YOUR REPUTATION GOES BEFORE YOU
![Page 6: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/6.jpg)
6
HOW DO WE APPROACH PROCESS IMPLEMENTATION
• The feasibility study
• Does size matter
• Review, learn and evolve
• Hardest parts of the process evolution
•The acceptance that its not doing everything you wanted it to do
•The thought that you may have been wrong.
![Page 7: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/7.jpg)
7
Incident starts
Incident detected
User impact mitigated
Service restored to pre incident level and set up
Root cause analysis
Identify root cause
Apply fix
Op
tion
1
Op
tion
2
![Page 8: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/8.jpg)
8
IT’S NEVER GOING TO BE PERFECT
“A common mistake that people make when trying to design something completely fool proof is to
underestimate the ingenuity of complete fools”
Douglas Adams
![Page 9: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/9.jpg)
9
PROBLEM MANAGEMENT EVOLUTION
![Page 10: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/10.jpg)
10
Severity 1 High SeverityA direct threat of damage to the image, reputation or credibility of the group. Multiple lines of business or locations critically affected.
Severity 2 High SeveritySignificant degradation or outage affecting a line of business key services or locations
Severity 3 Low SeverityMinor degradation to a key service, business process or location or a more severe degradation or outage to a non critical service, business process or location
Severity 4 Low SeveritySmall issue with localized scope typically affecting a single user. Can either be tolerated or worked around for an extended period of time due to its limited impact
Before We Go Any Further Lets Define Our Severities
![Page 11: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/11.jpg)
11
STEP 1 GETTING STARTED
•Problem records opened after every incident
•Problem records opened for all issues identified that needed to be improved
•Pride in the number of open problem records
MEASURES
•Focused around record updates and process adherence
•Processed policed by the problem management team
![Page 12: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/12.jpg)
12
STEP 2
•Split into low and high severity records
•Starting to focus on business impact
•Delivering business focused fixes when requested
•High volumes of problems still being opened
•Process still mainly policed not driven
MEASURES
Still focused on process adherence and compliance, and a drive to reduce the volume of records
Now they have two options if they are to evolve further
![Page 13: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/13.jpg)
13
Evolution Options
Fight the gatorsOr
Drain the swamp and find the gators a nice safe
home
THE CRITICAL POINT IN THE PROCESS DEVELOPMENT
This is the point of no return
![Page 14: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/14.jpg)
14
•Problem Validation
•Aggressive closure decisions
•Identify the issues that need addressing
•Evaluation to ensure cost effective fixes
•Logging repeat incidents to build business cases
MEASURES
Still focused on process adherence and compliance, and a drive to reduce the volume of records
STEP 3
![Page 15: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/15.jpg)
15
STEP 4
•Records prioritised with the business areas
•Fix dates were agreed with the technical teams
•New measures introduced
MEASURES
•Agreed dates for fix delivery
•Potential root cause notification
![Page 16: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/16.jpg)
16
The Next Steps
![Page 17: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/17.jpg)
17
STEP 5
•Faster delivery of fixes
•Blur the line between incident and problem
•Ownership from detection to fix
MEASURES
•End to end fix delivery agreements
•Provisional root cause accuracy
![Page 18: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/18.jpg)
18
Nothing wrong with any of the versions they were right for their time
![Page 19: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/19.jpg)
19
“Why should we change something that’s working ?”
many people in nearly every organisation
The process is doing what it always does
Look behind the process
•Are the processes delivering to the measures
•Are the measures really delivering the results we need
•Do we still want the same thing from the process
THE PROCESS IS WORKING WHY CHANGE
![Page 20: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/20.jpg)
20
• Keeps people focused
• Meet the changing needs of the business areas
THE PROCESS IS WORKING WHY WE MUST CHANGE
•To meet changing needs of the IT areas
• The drive to do things better
![Page 21: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/21.jpg)
21
WHY CHANGE? WHY NOT?
Continual service improvement ensures people don’t become complacent, and start to think they know things so well
they cut corners, or
they start to follow the process without thinking why.
![Page 22: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/22.jpg)
22
•Everyone must know more than the theoretical process
•They must understand •how it works•what it does •why it does what it does
•And most importantly what benefits it gives them
Without ownership the processes may look great on paper but they will fail to deliver
KEY PROCESS IMPLEMENTATION DANGER NON OWNERSHIP
![Page 23: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/23.jpg)
23
Processes bring their own dangers and perhaps the most significant is summed up here
“Process and Procedure are the last hiding place of people
without the wit and wisdom to do their job properly”
David Brent,The office (amongst others)
PROCESSES CAN BE DANGEROUS
![Page 24: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/24.jpg)
24
PROCESSES NEED PEOPLE
They need a special type of person to really deliver
What types do we have
•Those who the process owns
•Those who own the process
Don’t forget the process by-products'
![Page 25: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/25.jpg)
25
OUR PROCESSES ARE IN PLACE, THEIR EVOLVING CAN WE RELAX ?
Setting the targets to ensure the process delivers
•Every process needs its measures
•Every measure has a target
•Every target drives a behaviour
•Behaviours can hide the true facts
![Page 26: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/26.jpg)
26
USING YOUR PROCESSES TO IMPROVE YOUR PROCESSES
•Be proactive
•Use the processes to fix themselves
•Some times doing nothing is right
•When you think you’ve finished look again
![Page 27: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/27.jpg)
27
•Don’t hide behind the process
•If it doesn’t work, change the process
•Continue to grow and evolve even when its working
•Make continual process improvement the norm
•Ownership, Ownership its the key to success
•Remain focused on the business drivers
•The hidden dangers
•Treat your processes as a valuable asset.
•Processes are enablers not inhibitors
SUMMARY
![Page 28: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/28.jpg)
28
“An environment of continual challenge will add value across your organisation
not just to your processes”
![Page 29: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/29.jpg)
29
Clarification time
Question time
Quick coffee?
![Page 30: Problem Managment Yields Service Improvementv2](https://reader035.vdocument.in/reader035/viewer/2022070316/555b2737d8b42ae82e8b4627/html5/thumbnails/30.jpg)
30
Thank you very much