Skip to main content

ITIL 2011: Strategy Management

The publication of ITIL 2011 has brought several new or revamped processes to light. One of those is the Strategy Management for IT Services process. This Strategy process is not actually new. It represents the formalization of best practice guidance for managing strategies contained in earlier editions of the ITIL publications.

The purpose of this newly minted process is to use a company’s perspective, position, plans and patterns to ensure better management, governance and control of the IT services an organization provides to support the business outcomes. The basic principles of the Strategy Management process include helping to identify the overall business strategy and then tie an underpinning IT strategy (including an IT service strategy) or manufacturing strategy to the business outcomes through integration and alignment activities.

Once an IT strategy emerges in relation to the business strategy, the organization can then decompose the IT strategy into IT tactics and IT operations. These lower, more detailed levels of decisions and activities then exist in parallel to the business tactics and operations.

The key takeaway from the Strategy Management process should be a recognition that the IT policies, plans, projects, processes, procedures and work instructions do not exist or get created in a vacuum, independent from the business strategy, tactics, or operations. IT is wholly dependent upon the business for its existence. The work of IT (and the delivery of IT backed services) occurs at the request of the business and on behalf of the business. IT does not and should not exist for the sake of existing. 

ITIL does provide a cautionary note when attempting to undertake Strategy Management for the first time, especially when no overall strategy exists or there is no linkage from IT to the business. An organization can quickly become “…inundated with data and information, before they can produce anything that can be signed off by senior management” (SS 2011 4.1.4.1)

When undertaking this important, yet potentially overwhelming process, an organization should ensure involvement by the right stakeholders and to seek “…incremental progress to get an organization up to the point of addressing service strategy in the comprehensive manner described…” (SS 2011 4.1.4.1)

Taking a properly scoped and steady, yet measured pace to Strategy Management can produce great benefit for an organization. Perhaps the biggest challenge will be an organization’s willingness to undertake a process-driven approach to developing strategies that help to meet the business outcomes and the needs of both internal and external customers.

Are you willing?

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

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 th

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