Types of Work / Process Outputs

Dr. Michael Hammer and his co-author James Champy wrote the groundbreaking work Re-Engineering the Corporation. Dr. Hammer has long championed the concepts of using processes to accomplish work outputs and outcomes. Dr. Hammer spoke of three categories of work (or process output). Because a service can be defined as "work done for others," we can equate the types of work described by Hammer with the categories of services described by ITIL. The three categories of work according to Hammer are:

· Value-Add (ITIL Core services): This type of work (or services) provides direct value in the form of utility and warranty to the customers and users. Customers pay directly for this work or services. This work generates the revenue of your organization. This is "why you exist" and "what you do" as a business.

· Non Value-Add (ITIL Enabling and Enhancing services): This type of work supports, underpins and enables your Value-Add work or Core Services. This work (or supporting services) does not provide direct value, rather makes it possible to provide direct value by enabling or enhancing your core work or services. Customers pay indirectly for the services in prorated methods spread across the entire customer or user base. This work (or services) is your overhead, and this helps pay your bills.

· Waste: This work brings little or no value to your customers or users. This work does not help you achieve your business goals or customer requirements. Customers do not and should not pay for work that provides no value. This type of work should be eliminated and the particular target of continual process and service improvement.

By focusing on core services first, then enabling and enhancing services and working to eliminate waste, an organization can achieve great success. The ITIL processes help you focus on value-laden work and services. By following the best practice guidance of both ITIL and Dr. Hammer you can meet the needs of your customers and users.

Comments

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 then 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 Offe

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

Search