Originally posted on DevClass , June 22,2021 written by Joseph Martins and sponsored by Axelos Experience is everything when it comes to delivering IT-enabled products and services. But it’s no longer about how many deadlines your team smashed, how often you’d exceeded service-level agreements (SLAs), or how many lines of code you’ve spat out. Rather it’s about how the services and products you deliver impact the rest of the organisation’s ability to do their jobs, increase productivity, deliver customer satisfaction and co-create value. “Experience” may be seen as subjective, even ephemeral, compared to the traditional IT metrics, deadlines and SLAs. But if you want proof of its importance, consider how ITIL® 4, the latest revision of the best practice framework for service management from AXELOS, focuses on improving user experience of digital services and how this enhances productivity right across the organisation. Ian Aitchison , VP Product Management at Nexthink, the leader in di

Originally posted on devclass.com, June 22, 2021 and written by Joseph Martins. Sponsored Experience is everything when it comes to delivering IT-enabled products and services. But it’s no longer about how many deadlines your team smashed, how often you’d exceeded service-level agreements (SLAs), or how many lines of code you’ve spat out. Rather it’s about how the services and products you deliver impact the rest of the organisation’s ability to do their jobs, increase productivity, deliver customer satisfaction and co-create value. “Experience” may be seen as subjective, even ephemeral, compared to the traditional IT metrics, deadlines and SLAs. But if you want proof of its importance, consider how ITIL® 4, the latest revision of the best practice framework for service management from AXELOS, focuses on improving user experience of digital services and how this enhances productivity right across the organisation. Ian Aitchison, VP Product Management at Nexthink, the leader in digital

In the past, the idea was to build in the non-functional requirements of service to the best of our ability based on experience or best guess. Sometimes the general thought was, “We will worry about any residual work for availability, capacity, and reliability after the product or service is deployed”. This focus ensured that the product was fit for purpose, but did not ensure that the product was fit for use, that it was reliable. This approach is very costly to the operations of the service and negative consumer impact impedes opportunities for market share.  This type of focus also creates silos between Dev and Ops and Ops become firefighters.  The costs for operations are not sustainable! In addition to loss of revenues, staff morale begins to slip.  So, reliability is really the key to success. Think about your cell phone. A heavy focus on functional requirements would mean that you can make phone calls. You can text, you can  take photos, you can use your maps and a variety of

Best practice has proven that to be dynamic and to consistently meet changing business requirements, services must be co-created with our customers.  I learned in a recent ITIL 4 certification class titled Driving Stakeholder Value (DSV)  that providers will start with a stakeholder map and follow up with a customer journey map. If you are not yet familiar with Customer Journey Mapping, I strongly recommend learning about this critical skill needed to enable the co-creation of services.  Once you have a stakeholder map and have mapped the customer/user journey, you will need to identify the roles required. In our example below, we use the two roles of customer/consumer and service provider. Each of these, although not the only stakeholders involved, is critical to the success of co-creation.  Notice a relationship is being established via these responsibilities  Both the service provider and the consumer have responsibilities.  An IT service provider, for example, manages resource

Learn more about new ways to do work! Explore DevOps, ITIL, SRE, XLA’s and more ! Silos are not uncommon, but when you silo the service desk from second and third-tier support staff, you likely have a recipe for pain. An ineffective incident response system within the organization is painful and disrupts the entire organization, especially the customers. We must shift the way we think and work to stabilize and improve the situation. One organization felt that they had a grip on service desk and incident management, but they blamed the subject matter experts for breaches to Service Level Agreements . The blame game is always detrimental. Their process consisted of the service desk agents receiving the incident, performing the initial triage, and then forwarding it to the subject matter expert based on how they categorized the incident. Sound familiar? Sometimes we pass tickets to and fro, get everybody and their brother involved, wait on email responses, and create chaos that frustrat

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-c

The risk is below the water and we are headed right towards it. Organizational Transformations, Business Transformations and IT Transformations are all at their very core really CULTURE Transformations!  Ok friends, I’ve loaded this one up. For a deeper dive into some of the topics addressed in this blog, be sure to click on the embedded­­ links provided. Culture must be considered to Drive Stakeholder Value - This is POWERFUL! Think about how a culture shift  enables the following: Mapping the customer journey with all touchpoints and interactions. You can potentially map the customer journey and map the stakeholder’s roles and responsibilities brilliantly, but what about the cultural shift to enable these stakeholders? Without it we will likely fall short of our goals. If we have any hope of converting demand into value via IT-enabled services – culture is key!  Properly designing XLAs , SLAs and meaningful measurement models.  Without culture, the risk is high t

All service providers are in the business of customer and user experience . It is not enough to compete on products and services, how services are delivered is as important as what is delivered. The  customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers. In order to focus on the outcomes and on the customer/user experience, service providers are seeking to master the art of mapping their customer journey. Doing so allows them to maximize stakeholder value through co-creation of value throughout the entire value chain . The customer journey begins by understanding the overall macro-level of steps or groups of activities that generate the need for interaction between the customer and the service provider. These activities begin at “Explore” and end with “Realize” where the value is actually being consumed by the end-users.   Copyright ©

Think slow and hard about that statement; Drive Stakeholder Value ! Sometimes we see and use terminology so much that the power of the statement gets lost. This is one we must hear and ignite if we have any hope of meeting the evolving door of consumer requirements.  The Drive Stakeholder Value (DSV) certification course is available within the ITIL 4 Managing Professional stream of certification.  Therefore, DSV is also a module and one of the focus areas in the Managing Professional Transition (MPT) class.  Confused? Take a look at this graphic : ITIL 4 Managing Professional Transition  is a course that provides ITIL Experts or those that have at least 17 ITIL v3 credits a fast-track way to obtain the ITIL Managing Professional certification. This course excerpts key concepts from ITIL 4 Foundation and from each of the four Managing Professional modules. The Managing Professional stream of certification courses targets IT practitioners working within technolo