Skip to main content

The Best of Service Design, Part 1

We continue our "Best of" blog series by  moving into Service Design.

The Service Design Package
Originally Published in 2010

I have gotten many questions about what value does the Service Design Package provide?

We first must understand that all design activities are triggered by changes in business needs or service improvements. In order to design and deliver IT services that meet the changing needs of the customers and the business, clear, concise and unambiguous specifications of the requirements must be documented and agreed.

The SDP is where we document and agree to
  • Requirements – What the business wants and how they plan to use this new service. Define who all of the stakeholders are
  •  Service Design – Functionality of this new or changed service (SOR). Service levels to be delivered (SLRs, SLAs). Operational management requirements (OLAs, Contracts). Overall design and topology. Defined outcomes and deliverables. 
  • Organizational Readiness Assessment – Do we have the financial, technical, organizational resources and capabilities to meet the needs of the business? Have we assessed the business benefit this service will deliver?
  • Service Lifecycle Plan – Overall plan to cover the five stages of the service lifecycle including details for transitioning, operation and CSI of the new service.
  • Service Transition Plan – Overall transition strategy. Define objectives. State policy and do risk assessment.
  •  Service Operational Plan – Overall operational strategy. Define objectives. State policy and do risk assessment
  • Service Acceptance Criteria - Document to ensure that the service meets its expected functionality and quality. The service provider is ready to deliver and support the new service.
With this document in hand we can insure that the service delivered will meet the agreed needs of the customer and the business the first time with minimum of rework and interruption. It will insure that availability, capacity, security and continuity can be assured thereby delivering value to the business.


Comments

Popular posts from this blog

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, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...