Accountable or Responsible?

I was recently asked, "From an ITIL standpoint, what’s the difference between Accountability and Responsibility?" That's a great Question!

There is a big difference between Accountability and Responsibility. The ITIL Continual Service Improvement (CSI) book provides the following definitions:

Accountable: Ownership of a process, and/or activity. The person who is held accountable and ensures that the goals and objectives of a process are being followed.
Responsible: Performer of a task. The person responsible for getting the task/activity done. This person gets the work done and does not necessarily have the authority to ensure that others are getting their tasks completed.

Accountable roles oversee or "own" the process or task; responsible roles execute or perform one or more aspects of the process or task.

For example: A CIO is accountable for the quality of all IT services, including the results produced by the IT staff and suppliers. However, the CIO does not personally manage or perform all of the tasks required to deliver those services. He or she delegates that responsibility to others in the IT or supplier organization.

Line managers are similarly accountable for the results of their teams but delegate the responsibilities of daily tasks to individual members or suppliers. So, could one role be both accountable and responsible? Absolutely! It is important, however, to understand that there is a very different focus between "accountability for results" and "responsibility for doing the work".

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