Main Menu
Home / IT Governance / Legacy Support / Process Improvement is not Service Improvement

Process Improvement is not Service Improvement

The Common ITSM Mistake:

Dan Kane is the first to admit this somewhat common ITSM mistake: process improvement and service improvement are not the same thing. Kane explains how often he finds continuous service improvement efforts that all list things like fewer incidents or process efficiency as the primary goals. People believe that first contact resolution, mean time to restore, or self-service growth are the only way to measure success in IT service management. But as the author explains, it’s the service that is the product:

Here's the confusing part: We are providing a service that is also a product. Customer interactions with individuals delivering the service are part of that service. We call those interactions “providing service” or “customer service”. This word service is used all over ITSM, so it's easy to confuse the service product with the activity of customer service.
Let's be clear. Incident management is not a service. It controls a process or series of activities done in order to restore a service to normal working state. Measures of incident management or customer service have no direct correlation to the willingness of customers to consume your service-product. Those measures may have an indirect connection.

It's About Value

Kane is quick to point out that process quality is a variable of service quality, it’s certainly not synonymous. Service improvement is about value, first and foremost. It’s a way of making sure customers are comfortable in dealing with your organization—that they are getting benefits from their cost investments.

Kane follows up with another post clarifying his position and answering some of the expected questions his post brings up, but to view this post in full, click here:

About Matthew Kabik

Matthew Kabik is the former Editor of Computer Aid's Accelerating IT Success. He worked at Computer Aid, Inc. from 2008 to 2014 in the Harrisburg offices, where he was a copywriter, swordsman, social media consultant, and trainer before moving into editorial.

Check Also

COBOL Is Still Around Because Nothing Better Has Replaced It

When COBOL was made in 1959, no one could have dreamed that it would outlive …

Leave a Reply

Your email address will not be published. Required fields are marked *

Sorry, but this content
is for our subscribers only!

But subscribing to ACCELERATING IT SUCCESS is FREE and only one click away!
Join more than 40,000 IT Professionals and get the best IT management articles to your mailbox with Accelerating IT Success!

Unsubscribe at any time