The Case For IT Service Management

IT Service Management is still the heartbeat of IT services, making sure that the IT services we provide to our customers are available, stable, reliable, scalable and every other "able" you can think of! If you want to know why and the things you can do to ensure it is effective, you'll love this blog.
Lets dive right in...
Introduction – Why is IT Important?
In the UK approx. 1 in 20 people work in IT & telecoms
Over 30 million people use IT in their daily jobs
Less than 1% companies worldwide could cope without the Internet
IT represents a large % of total business expenditure
Many business functions totally rely on IT
IT doesn’t just support business, IT powers business
IT is at the heart of industry and fundamental to our lives
Most organisations depend on IT to help them achieve their vision, strategy and objectives
Organisations use IT to:
1) Transform the way they operate, communicate, and do business
2) Innovate, gain market advantage, and differentiate themselves
3) Improve productivity and increase sales and growth
4) Improve business processes and efficiency and make cost savings
5) Communicate with a global marketplace

Topics & Scope

Cost Vs Value
The cost of IT is never insignificant
It is important to get good value from IT investments
However, the potential business value is not always realised
Where does the business get value and benefit from?
From IT applications / services in live operation
Not from projects in development
What Is an IT Service?

IT Service Management
For an IT investment to deliver its potential value, the resulting IT service needs to be:
Well planned,
Well designed,
Well implemented,
Well delivered, and
Well received
This is what the practice of IT Service Management is about
The professional practice of planning, designing, developing, delivering and optimising IT services that are both fit for purpose and fit for use - thus ensuring value and return on investment can be maximised
A specialised discipline that includes the methods, processes, activities, functions and roles needed by a service provider to deliver IT services that provide business value for its customers
A growing profession of people, skilled and committed to delivering high-quality IT services that provide measurable value for the businesses that use them
Benefits of Good IT Service Management
IT services that align with business priorities and objectives – helping the business achieve their strategic objectives
Known, manageable IT costs - helping the business manage its Finances
Reliable services that work when the customers need them – leading to better business efficiency, effectiveness, and productivity
Improved resource management and reduced rework within IT saving the company money
More effective management of change - enabling the business to keep pace with change and drive change to its advantage
Better customer satisfaction with IT - and better end-customer perception and brand image
Common Problems
These are the common problems we find we come across with our clients when they engage us. do you recognise any of these symptoms?

Poor IT & Business Alignment

IT must be of value to the business
IT must be possible to see a direct or indirect link between the IT and the business processes / priorities / objectives
If any IT component doesn’t have a purpose relevant to the business, then its existence should be questioned
Recognising Good & Bad Practice
Misalignment between IT and the business: | Alignment between IT and the business: |
|
|
What Should We Consider?
Business relationship management - high level, strategic relationship between IT and the business / customers
Good understanding of the business, business priorities and objectives
Service portfolio management - understanding the Service Catalogue (services in operation) and the Service Pipeline (services in concept or development) and making sure they all have a clear business purpose
Clear (direct or indirect) value chain between all aspects of IT services and the business activities and objectives
Lack of customer Focus

The customer must be at the forefront of our mind
Just because we think we are doing a good job, the customers do not always feel the same way
We need to be aligned on what success looks like and how we measure it
Recognising Good & Bad Practice
Poor customer focus: | Good customer focus: |
|
|
What Should We Consider?
When designing the service and SLAs, focus on what is important to the customer and test the customer’s understanding of the service levels
Make sure service levels are written from a customer perspective
Maintain an ongoing dialogue with the customer - check their expectations and perceptions regularly
Important to have staff with good ‘soft skills’ involved
Don’t rely solely on agreed service levels because requirements change over time - regularly check whether the customer is happy with the service and what is important to the customer
Poor Linkage Between Projects & Operations

Projects and operations must start together and work together.
A key measure for success of any project must be that it is delivered with no disruption to the customer and meets the business case that was approved by the customer
Transition needs to act as the gatekeeper to Live Operations but is constrained by the strength and maturity of the other Service Management capabilities
Project / Development Process
When delivering a project the standard framework or methodology is below. The lens that you look through when delivering is always through the lens of the project team and the product that is being built.

Handover to Operations
The handover to operations feels like this for many of our clients. We have all experienced the hit-and-run approach of projects and that they get thrown over the fence to IT operations to then run. This is a common practice!

Recognising Good & Bad Practice
Poor linkage between projects & operations | Good linkage between projects & operations |
|
|
What Should We Consider?
Aspects of IT service, which need to be planned, designed, developed, tested, implemented include:
Service solution
Architectures
Infrastructure components
Measures and metrics
Management information system, tools and techniques
etc……Think of the Iceberg
Can We Do It Differently?
Of course we can!!! Imagine how the project lifecycle / framework would look if the operations team were involved from the very beginning…..
Service management involved throughout the lifecycle, to design, build, test and implement the IT service – Projects involved in early life support

Focus on Service Utility & Not Service Warranty

Common oversight from IT organisations and even knowingly neglected.
Fit for purpose, but not fit for use.
True value of a service is created if it is fit both for purpose as well for use. It must meet the conditions for both the utility and warranty. And only then, a service is valuable.
Likely to result in:
Service levels below expectations
Operational costs above expectations or not clear
Problems with operational service
Project Team disappeared
Operations ‘Responsible’ to sort out the ‘problem’
Lack of or no data on the performance of the service
Recognising Good & Bad Practice
Focus on utility but not warranty: | Focus on both utility & warranty |
|
|
What Should We Consider?
It is a common mistake to design IT services that are fit for purpose but not fit for use.
This will delay (or even prevent) the delivery of business benefits
Retro-fitting IT service design later is a high-risk strategy, which will be more costly and may even prove impossible
Once in operation, it may well be too late to make significant impact on the cost of ownership of an IT system
Once developed, it may be too late to get the service levels expected at a reasonable cost - and sometimes the required service levels cannot be met at all - meaning business benefits won’t be achieved
Service improvement can only do so much, it cannot re-engineer the operational design of a system or service
Focus on Utility & Warranty
Meaningful debate on service level options and costs BEFORE constrained by application design
Define the service in terms of all its service requirements - warranty requirements as well as utility requirements
For significant changes / projects / new services, create a service design package (SDP) and service acceptance criteria
Warranty requirements include – Capacity, Security, Availability, Reliability & Continuity
Hours of Service Availability Backup & Recoverability Service Continuity Security Privacy | Response Times & Throughput Capacity & Growth Resilience to Incident Robustness to Business Change Need for Flexibility Level of Data Integrity |
Poor Cost Management

Everything we do must make financial sense
The business need to consider IT as good value for money
Cost and value are 2 very different things