Drivers for the Various CSI Orders or Levels

In a previous blog we discussed the revised 7 step improvement process. Step 6 of that process is to present and use the information. There are various levels of management in an organization. When presenting this information and implementing improvements it is important to understand which level to focus on and have a good understanding of the perspectives of each level and what their drivers are. This will enable us to derive the maximum value and benefit out of the information delivered.

First order drivers: At the highest level of the organization are the strategic thinkers. The reports delivered at this level need to be short, quick to read and deliver precise data about risk avoidance, protecting the image or brand of the organization, profitability and cost savings. These are the drivers that will support your reasons for improvement efforts.

Second order drivers: The second level of management is occupied by vice presidents and directors. Here, reports can be more detailed and must summarize findings over time. Defined is how the processes delivered support and underpin the business objectives and enable the organization to react early and quickly to issues that put the business at risk. They will also illustrate how these processes are aligned to our existing measurement frameworks which enable us to define the health of the business from the perspective of the IT organization.

Third order drivers: This third level of management is made up of managers and high level supervisors. At this level reports and measurements need to demonstrate compliance to stated objectives and overall team and process performance. They should provide insight into resource constraints and continual improvement initiatives.

Fourth order drivers: At this level are the team leaders and staff members. Reports must emphasize personal benefits. Metrics must define individual performances, provide recognition of skills and identify training and career growth opportunities.

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