VeriSM™ and ITIL®4 are very different. It’s the same story as any other question of how VeriSM differs from ITIL, COBIT®, IT4IT®, ISO/IEC 20000, etc. VeriSM isn’t a standard, methodology, or framework, but rather an operating model. ITIL, 20K, COBIT, etc. all are process (practice) driven standards, methodologies, or frameworks.
VeriSM recognizes that all the various standards, frameworks, methodologies have a different emphasis. What VeriSM points to is that depending on the requirements, the appropriate methodology should be used be it ITIL, COBIT, Agile, Lean, etc. VeriSM expands the service management philosophy across the enterprise.
ITIL still is focused in the technology area even though it’s putting forth practices around workforce and talent management, project management, and business analysis – it’s trying to take the enterprise step but it’s not quite there yet (note: there is still information not yet released and therefore a full judgement can’t be made). ITIL 4 states that it is incorporating Lean, Agile, DevOps into its practices (processes) and operating models. That may well be true, but there is a lot of altering of the methodologies in order to ‘fit’ the ITIL principles.
VeriSM is an operating model; ITIL, et al are all players within that operating model. VeriSM is the only service management philosophy that is truly neutral and non-biased. The operating model clearly states to use whatever framework, methodology, or standard that is most appropriate for the consumer requirements, organizational capabilities, and the mission/goals of the organization. Lastly, as with any of the management practices, ITIL is just one strand of the mesh (key concept in VeriSM) and it is up the organization to populate that mesh with the practices, disruptive technologies, resources and environment that accurately reflect the organization.