Skip to main content

Balance in Operation III

In every organization the one constant is change.  In service operation, all functions, processes and related activities have been designed to deliver specific level services.  These services deliver defined and agreed levels of utility and warranty and doing so while delivering an overall value to the business.  The catch is this has to be done in an ever changing environment where requirements, deliverables and perceived value changes over time.  Sometimes this change can be evolutionary or can take place at a very fast pace.

This forms a conflict between maintaining the status quo and adapting to changes in the business and technological environments.  One of the key roles of service operation is to deal with the tension between these ever changing priorities.
This struggle can be broken down into four general imbalances that provide the service provider an opportunity to develop some guidelines to resolve these conflicts:

·         Internal  IT view vs. External business view

·         Stability vs.  Responsiveness

·         Service  quality vs. Cost

·         Reactive vs. Proactive
We will focus today on one of the more difficult elements to bring into balance: service quality versus service cost.

Early in a service lifecycle it is possible to achieve significant increases in the quality of a service with a relatively small amount of money.  For example, increasing availability or creating some enhanced functionality maybe easily accomplished with a relatively small amount of additional resources.  After a service has had time to mature it can become quite expensive and resource intensive to increase measures of quality to the customers and end users.  For example, improving the same service as mentioned above from say 98% availability to 99.9% availability or delivering some additional capability to a more finite group of users can be cost prohibitive.

Determining the optimal balance of cost and quality should be determined during the service strategy and service design phases of the lifecycle, however it is often left to service operation teams whom are generally not equipped nor have the authority to make those levels of decisions.
Having strong and well defined Service Level Requirements and Service Level Agreements from Business Relationship Management (BRM)) and Service Level Management (SLM) should create a clear understanding of the business purpose and potential risks in meeting customer needs.
It is crucial that we achieve a balance between these two views.  Services must be designed and delivered around customer needs and requirements.  They must have the ability to create the desired business outcomes for the users and deliver necessary value to the customer.   At the same time, however, it can be possible to compromise those needs and requirements by not properly planning the cost of delivering those services. 

Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 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 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 than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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