<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=42246&amp;fmt=gif">
blog_header_VeriSM

ITSM Processes

ITSM-trends: VeriSM, one model to rule them all?

By Gunnar Oldenhof on May, 2 2019

Stay up to date

Gunnar Oldenhof

Service Management Consultant

Trends come and go in service management, technology, processes and frameworks. For every trend, the question is: how will it help you? Does the latest trend really help you improve your services? Today, service management expert Gunnar Oldenhof explains VeriSM: what is it, and is it here to stay?

VeriSM in one sentence


VeriSM is an approach to service management that helps you choose which frameworks and methods work best for your organization.

Why does VeriSM exist?


VeriSM was introduced in 2017 by the IFDC: the International Foundation for Digital Competences. It’s meant to be the answer to the quick pace of changes in the digital landscape. Your customers’ wishes are changing and existing tools and frameworks are becoming obsolete faster than ever – even ITIL finally has an update out since February. Plus, new technologies and frameworks are being introduced all the time, from A.I. and automation to cloud software and DevOps.

How do you make sure you stay up-to-date? How do you know your organization is still working with the most relevant tools, frameworks and best practices?

The creators of the VeriSM model want to provide insight into the IT landscape as a whole. And they want to help IT organizations select the right tools, frameworks and best practices.

OK. So, what exactly is VeriSM?

VeriSM stands for Value-driven, Evolving, Responsive, Integrated Service Management. It’s not another new framework, but rather a new way to approach existing frameworks. So VeriSM isn’t a competitor for ITIL and DevOps, for instance.

VeriSM is based on two important principles:

  1. Every company is a service provider. Organizing or improving your services is a joint effort for the entire organization. Your IT or Facilities department shouldn’t do it on their own.
  2. Be flexible. Don’t force all teams to work with the same tools or frameworks. Let your teams do what works best for them.

How do you apply VeriSM?

VeriSM does not (yet) offer a step-by-step guide for implementation. They emphasize that every organization has different needs, so a standard implementation may never come. VeriSM does provide a few guiding principles for applying their philosophy:

  1. Your customers’ wishes are your starting point. Don’t base your services on what your colleagues want, base them on your customers’ wishes.

  2. Formulate principles for your services. Based on your customers wishes, have delegates from different parts of the organization come up with guiding principles for your services. These principles may apply to quality, security or speed of your service delivery. For example, quick delivery may be more important for your organization than providing a perfect product. If you do it right, your guiding principles will match company goals.

  3. Create your own Management Mesh. For each team, pick the best resources, management practices and emerging technologies to help you provide your service the right way. The combination will be different for different teams, and your needs will change along with your circumstances.
VeriSM - Management Mesh

What does VeriSM add to theories that are already out there?


Most of the ideas presented in VeriSM expand further on existing best practices. The idea that you should work together with other departments to create the best services, is an expansion of the concept of Enterprise Service Management, also known as Shared Service Management. The ideas behind a customer focused approach and IT governance also aren’t new, and the VeriSM model for designing your services (Define, Produce, Provide, Respond) is similar to ‘Plan Do Act Check’, from the Deming circle.

VeriSM’s most important innovation is its idea that you should form guiding principles for your services. It’s a little bit similar to the 4 values of agile, but the main difference is that VeriSM doesn’t limit you when it comes to deciding which principles to adhere to. That decision is left to each organization individually. And the principles you choose provide support for the services you develop.

Does VeriSM have a future?

It’s difficult to say at this point whether VeriSM has a future. Guiding principles for your services are an interesting concept, and the pragmatic approach – use the resources that work for you – is also sensible. Especially before ITIL 4, this was a refreshing, more agile way of adopting best practices.

At the start, VeriSM’s biggest problem was that there are no examples from the real world yet. It was just a theory, there was no evidence that it actually works. Claire Agutter, Chief Architect of VeriSM, also recognized this problem. She’s encouraging companies to put VeriSM into practice and gather as much feedback as possible. There are VeriSM courses and certificates available, such as the VeriSM training Agutter's ITSM Zone offers, but Claire Agutter says you don’t need any of those to start working with the concept.

VeriSM’s success will depend on whether companies will adopt it. Are organizations going to try this theory in their work? And will they share success stories with VeriSM? VeriSM at least made a good start. Last year they published the book ‘VeriSM: Unwrapped and Applied’ , featuring case studies of digital transformation within organizations. If they manage to assemble & publish more and more case studies, there just might be a bright future for VeriSM.

More ITSM trends

Do you want to stay up to date with what's happening in the world of ITSM? Sign up for our blog and don't miss a thing.

Submit a Comment