Skip to main content

ITIL 4 Specialist Drive Stakeholder Value: Maximizing the Consumer Experience

Originally posted on The AXELOS Blog, February 2020 and written by Christian Nissen, IT management consultant and lead author for the ITIL 4 Drive Stakeholder Value module.

Back in the industrial society, goods were a dominant factor in our lives. But in the “service era” we prefer to replace ownership of goods with access to services and resources without necessarily owning them.

This is happening with and without digital transformation, although the latter accelerates this phenomenon: think Uber and Airbnb.

In this context, the ITIL® 4 Specialist Drive Stakeholder Value module – within ITIL 4 Managing Professional – is about the engagement and interaction between service providers and stakeholders and the conversion of demand to value via IT-enabled services.

But what does this mean in practice?

Previously, services were treated in the same way as manufactured goods: it was the customer’s responsibility to derive value. Conversely, the core concept of ITIL 4 is that value is co-created.

Therefore, we have built this ITIL 4 module around the customer journey – from both parties engaging, agreeing to work together and interacting to co-create value.

While ITIL v3 taught a service provider to improve one-sidedly, ITIL 4 also encourages the service provider to help the consumer to improve. For example, the business product owner (the “consumer” in IT) is encouraged to adopt service management best practices as part of the product development relationship to elevate mutual capabilities and thereby increasing the co-created value.

Key elements of driving stakeholder value

What capabilities will an ITIL 4 Specialist in driving stakeholder value develop?

1. Ensuring high satisfaction levels
ITIL had previously considered satisfaction via service level agreements focused on outcome, utility and warranty. ITIL 4 judges the experience to be equally important as the outcome when consuming a service.

2. Using human-centred design when designing services
The module gives practical guidance about, for example, design thinking to achieve better usability and experience by understanding how the customer feels when using a service.

3. Customer experience (CX) and user experience (UX) design to optimize customer experience
These ideas add to the concepts of utility and warranty (achieving quality outcomes) but speak the language of experience based agreements.

4. Communication – influencing stakeholders, encouraging collaboration and transparency
To drive stakeholder value, good communication is a prerequisite of trust: listening and understanding what each party needs and wants. By understanding the dynamics in a service relationship, the practitioner will be better placed to provide services, drive and co-create value.

This is a very different approach from an IT technician setting up a server and concentrating on availability, utility and warranty. The difference is having an awareness that the way service management professionals interact with stakeholders will influence their ultimate experience.

Who benefits from ITIL 4 Managing Professional Drive Stakeholder Value?

As ITIL now includes consumers and producers together in multi-dependent workflows and systems, this module is focused on helping practitioners increase stakeholder satisfaction via the best service offerings; something that is essential to business success in today’s highly competitive landscape.

To learn more; consider the following ITSM Academy certification courses:

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…