PRODUCT & SOLUTIONS
- Workflow Designer
- Service Catalog Designer
- Dashboard Designer
- Network Monitoring Interface
- Customer Survey
- ITIL® - ITSM Software Solution
- Internal Service Desk
- External IT Support Desk
- RMA Software Solution
- Sales Support Solution
We're Jumping on the ITSM Bandwagon - Where do we start?
Doesn’t that seem like the most logical place to start? It directly impacts the user (your customer) and the operability of your organization. This is far more visible than some esoteric CMDB implementation that the user never really sees. Don’t get me wrong, there is a time and place for a CMDB implementation but it’s further down the road along your service management maturity path.
Incident Management is the perfect process to implement to “cut your ITSM teeth on”. Remember that ITSM is more about the process and the culture shift within your organization than the tool you implement. To be successful we as IT need to convey to the business we understand their needs and the business needs to communicate with us and trust us (us being IT collectively) that we will fulfill their requirements.
Incident management is for the consumers of IT, hence is the most visible of all ITIL / ITSM processes and may be (in most cases) the most important process for IT’s reputation. In today’s world where smart phones, tablets and cloud services are common; our reliance on these tools is substantial and necessary for our organizations to operate. Issues need to be dealt with immediately (that 8 – 12 hours we spoke of). A successful Incident Management process will place IT in a very positive light for your end users, your organization and even the C-suite.
Remember there are five basic operational characteristics to consider when defining your Incident Management framwork/structure/process:
- Process flows– define measurable targets, make sure you have consistent communication and last but not least define meaningful categorization (download our white paper around this: https://www.monitor24-7.com/documentation/Service-Desk-Classification.pdf) to identify trends, quantifiable metrics/reporting, proper queuing and skills routing.
- Quality control – your KPIs must be defined in line with business policies, this is where working with the business is critical, they speak KPIs and these will measure our success. You should also look at KPI’s that help you predict future incidents. Often we see companies use the KPI’s for historical purposes and shame people (not a great motivator). Your SLA’s should not be there to penalize people, they should be there to support people to do better, to see which incidents should be dealt with first and make your service organization successful.
- Roles & responsibilities – Set up a framework for assigning incidents and project roles. Think this through, as it will help you manage incidents more expeditiously. You can support this with a dashboard for a visual overview
- ITIL process integration – defining the incident process also needs you to think about problem, change and service level management (your next steps in service maturity). Define when you believe an incident becomes a problem and a change. Also think about your service levels and how can they support your team and benefit your organization. Make these reasonable and easy to monitor and report upon.
- Policies – the policies applied in the configuration, SLA and process definition must be agreed upon at the C-level (or minimally with business buy-in) and communicated widely. Everyone must be aware.
So, when you ask a vendor where we should start with our ITIL/ITSM implementation if they don’t say Incident Management be very suspicious and ask “Why not Incident Management”? Hopefully they have some justification based on your individual requirements. The key things to think about are :
- Person hours of implementation (i.e. cost)
- KPI’s and success metrics
- Do we have business buy-in?
- Can the business understand the benefits and quantify the success metrics?
© 1999 - 2016 Monitor 24-7 Inc. All rights reserved.
IncidentMonitor™ is a registered trademark of Monitor 24-7 Inc.
IT Infrastructure Library® (ITIL) is a Registered Trade Mark of the Office of Government Commerce.