Skip to main content

The Best of Service Strategy, Part 2


Service Strategy's Four P's
Originally Published on July 10, 2012


Whenever I am introducing ITIL and ITSM to a new group of students I always make sure that the concept of Strategy as a process is always discussed.  The reaction that I usually get from most is:
“Strategy isn’t something the business does?” 

I begin our discussion with a simple definition.  Service Strategy comprises the processes of: strategy management for IT services, service portfolio management, financial management for IT services, demand management and business relationship management.  In the world of ITSM, Service Strategy is the stage of the lifecycle were we align our IT strategy the with business strategy and define our perspective, position, plans and patterns that we as a service provider will have to execute in order to meet an organizations business outcomes.   

These four elements must be present and help guide us in defining and documenting our overall IT strategy.    Let’s take a look at what is contained in the four P’s of Strategy.

Perspective:  Describes the vision and direction of the organization.  A strategic perspective articulates what the business of the organization is, how it interacts with the customer and how its services or products will be provided.  A perspective reinforces a service provider’s distinctiveness in the minds of the employees and customers.
Position:  Describes how the service provider intends to compete against other service providers in the market place.  The position refers to the attributes and capabilities that the service provider has that make them unique from their competitors.  Positions could be based on several factors such as low cost, specialized services, expertise of a particular customer’s environment or industry.
Plans:  Describe how the service provider will transition from their current state to their desired state.  Plans will describe the activities that a service provider will have to undertake in order to meet its strategic perspective.
Patterns: Describes the ongoing, repeatable actions that  a service provider will have to execute in order to continue to its strategic objectives.
We can begin with any of the four elements.  The sequence is not prescribed as long as all four are present.  In this way we can be agile in dealing with strategies that currently being executed and those that are still being envisioned.

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…