Skip to main content

What's in Your Strategy?

One of the things we frequently hear from individuals who attend the advanced ITIL® 4 classes such as High Velocity IT and Drive Stakeholder Value is how very different ITIL 4 is, and more specifically, how relevant it is to challenges currently facing organizations. So how can organizations leverage this guidance? They need a strategy.

More specifically, they need a set of aligned strategies that are linked to the organization’s overall objectives. According to ITIL 4® Digital and IT Strategy, this set of strategies includes:

  • business strategy – how an organization defines and achieves its purpose
  • digital strategy – a business strategy that is based all or in part on using digital technology
  • An IT strategy – a technology strategy and corresponding architecture that supports the digital strategy; along with the back-office strategy and administrative elements of information technology (e.g., the data center and infrastructure)

While seemingly separate and distinct, these strategies merge in response to an organization’s growing reliance on technology. A reliance that has been amplified by the COVID-19 pandemic.

Most organizations have been adopting some form of digital technology for decades. What differentiates a digital organization is the extent to which it uses digital technology as a basis to differentiate itself. Digital organizations rely on digital technology as a fundamental component of their business and operating models.

Even before the pandemic, most organizations recognized the need to undergo a digital transformation in order to survive and grow in our increasingly digital society. According to Gartner, 69% of boards of directors accelerated their digital business initiatives in the wake of COVID-19. According to a McKinsey survey, companies have accelerated the digitization of their customer and supply-chain interactions and of their internal operations by 3 to 4 years, and the share of digital or digitally enabled products in their portfolios has accelerated by 7 years.

The term digital transformation, as defined in ITIL 4® High Velocity IT, is used to indicate major investment in digitizing, robotizing and other forms of automation that enables organizations to:

  • Do business significantly differently (e.g., switching to a predominantly remote model for healthcare (telemedicine) or education (online training))
  • Do significantly different business (e.g., introducing new lines of business based on digital technology (e.g., amazon web services)

The term transformation is defined as dramatic or radical change. Transformation does not, however, imply a big bang adoption, although it could be based on the approach selected to achieve the change. Transformation can be achieved, and is often more successfully achieved, by making many small, continuous changes.

Transformation begins with a shift in mindset, coupled with new ways of thinking and working, new skills, and new combinations of skills. It is about reframing work by thinking about things differently, or thinking about different things. It is a journey; but when done well, it is a journey with a clearly stated direction and objectives. Objectives that cannot be achieved without a shared understanding of the organization’s priorities.

According to Mark Blanke, President and CEO of OwlPoint and Chairman of The CIO Initiative, business and IT leaders are narrowing in on four priorities:

    • Maximizing the velocity of product development and innovation efforts
    • Keeping products reliable
    • Enhancing the customer experience
    • Driving cost-efficiency

While the order in which these priorities are addressed will vary from one organization to next, most leaders recognize the risks they face when sacrificing one (e.g., quality or reliability) for another (e.g., speed) These leaders recognize that to undergo a successful transformation they must nurture a digital culture that embraces constant change and evolution, and that supports agility and resilience.

Admittedly, some organizations have scaled back their digital initiatives and made budget cuts in response to the global pandemic. These organizations are, for now, focused on surviving. Others, however, are taking action to make sure that when the crisis ends, they’ll be stronger than they are today.

For some organizations, the pandemic has accelerated the adoption of digital technologies across the enterprise. For these organizations, the need to change wasn’t as evident before, but the pandemic and the need to support remote workers forced the adoption. Other organizations found that they needed to transform to stay alive. For example, many small businesses such as restaurants and retail outlets had to rapidly adopt digital technologies in which they hadn’t previously invested. This was a total change in strategy brought on by the need to support digital engagement with their customers and to facilitate touchless interactions.

Regardless of their approach, it is important that all organizations identify and capture lessons learned during the pandemic, and use those lessons to reset the organization’s strategies, build resilience, and improve organizational readiness.

Given the current high levels of volatility, uncertainty, complexity, and ambiguity (VUCA),

organizations must move from long-term, rigid and detailed plans to an agile approach with goals that are continually redefined and adjusted based on the analysis of both external and internal factors.

Blanke suggests doing periodic strategy alignment reviews of the organization’s projects and programs. There is no rule that specifies how frequently these reviews occur. Rather, the frequency should match the volatility of the organization’s environment.

Creating and maintaining this set of strategies is not a one-off or annual activity. In fact, according to ITIL 4® Digital and IT Strategy, organizations that both define and review their strategies annually tend to be more reactive. This is because technological innovation and competitive disruption of industries and markets occur frequently. Strategies must, therefore, be managed within shorter cycles, taking into consideration more scenarios and strategic options than has been done in the past. Having said that, not everything has to be evaluated at once. Different levels of strategy (e.g., the enterprise vs. individual business units) usually have different review and update cycles. Strategies are supported by other strategies and subordinate strategies may be re-evaluated more frequently. The higher the strategy is in the hierarchy, the less volatile it should be. The key is to strike a balance between the time and effort needed to perform the reviews, and the time and effort needed to execute the strategy and turn the organization’s vision into reality.

Written by Donna Knapp and Mark Blanke

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

ITIL Leader: Digital and IT Strategy

ITIL Strategist: Direct, Plan and Improve

ITIL Specialist: High Velocity IT


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 th

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for the v

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