The Best of Service Design, Part 4

ITIL 2011: Design Coordination

Originally Published on September 20, 2011

The Service Design stage of the ITIL Service Lifecycle can be a powerful and beneficial set of activities and undertakings if managed, guided and coordinated in a holistic and comprehensive manner. One of the more powerful processes to emerge with the publication of the ITIL 2011 addition is the Design Coordination process. Previous editions of ITIL had the reader and practitioner assume or extrapolate the guidance provided in the Design Coordination process. ITIL 2011 formalizes the guidance and shows the need to have a method of ensuring the smooth operation of all the moving parts of Service Design.

Design Coordination has several important objectives including (SD 2011 4.1.1):

Ensure the consistent design of appropriate services, service management information systems, architectures, technology, processes, information and metrics to meet current and evolving business outcomes and requirements
Coordinate all design activities across projects, changes, suppliers and support teams, and manage schedules, resources and conflicts where required

Oftentimes when we work very closely to a specific operational activity we can get tunnel vision towards the both the effort and results of our activities. The Design Coordination process allows us to take a virtual “step” backwards and to see the bigger picture of needing to coordinate many parts, pieces and players into a final deliverable in the form of a comprehensive and effective Service Design Package.

The Design Coordination process also provides a method of instilling governance and rigor to our effort to create the best possible design of the IT services we provide to the business and customers. Some aspects of the rigor and governance that the Design Coordination process can bring include (SD 2011 4.1.2):

Assisting and supporting each project or other change through all the service design activities and processes

Maintaining policies, guidelines, standards, budgets, models, resources and capabilities for service design activities and processes

Planning and forecasting the resources needed for the future demand for service design activities

Ensuring that all requirements are appropriately addressed in service designs, particularly utility and warranty requirements

An important factor to keep in mind is that the Design Coordination process does not do the actual detailed design of either the individual service solutions or any work outside the scope of the Service Design phase. Those activities are best left to the specific Service Design processes or other stages of the lifecycle. Design Coordination (as the name implies) works to make sure all those individual processes work together in a seamless flow to produce effective designs that later stages can transition to production.

Design Coordination is also one of several points of integration and connection to a formal project methodology. Before a project undertakes the formal creation of deliverables, Design Coordination provides guidance on aligning the deliverables of the project to the requirements and needs of the business and customers in terms of IT services. Design Coordination provides guidance on the resources and process activities available to the project to validate that the project has what it needs to be successful.

The Design Coordination process is a breath of fresh air for those looking to construct a means of keep everyone pointed towards the same goal of effective and successful IT service designs. Take a look at the guidance provided in ITIL 2011 to bring the greatest benefits possible during Service Design.

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

Search