Skip to main content

The Best of CSI, Part 3

Creating a Metrics Program
Originally Published on November 30, 2010

Every organization should create a metrics program to ensure that business and process improvement goals are being achieved. We need to have the ability to show that processes achieve results and we must review and schedule process audits.

A metrics program describes the measurements needed to achieve business goals. It also identifies how to collect the data and how to use the information to continually improve performance. An effective program focuses on what you should measure to achieve business goals, individual process performance and process interfaces.

Each of the best practice frameworks stress metrics as a way of assuring continual improvement. ITIL defines the "7 Step Process" for identifying, collecting, analyzing and using data.  The Deming Cycle's "Check" stage requires that we have methods for monitoring and measuring processes.  The Balanced Scoreboard looks at performance from multiple perspectives.
Here are some useful steps for creating a meaningful program:
  • Step 1: Determine Management’s Vision
  • Step 2: Identify Critical Success Factors
  • Step 3: Identify Key Performance Indicators
  • Step 4: Identify metrics
  • Step 5: Verify metrics are SMART (Specific, Measurable, Achievable, Relevant, Timely)
  • Step 6: Identify required data elements
  • Step 7: Test and pilot your metrics and reports
  • Step 8: Document your metrics and reports
  • Step 9: Place approved metrics and reports under change management control
  • Step10: Continually review reports for effectiveness

The key to a successful metric program is to keep it simple.  Avoid measuring what you can, instead of what you should.  Produce metrics that are sufficient to control monitor and predict performance. Leverage automation whenever possible possible to analyze performance and look for trends. It is particularly important to communicate your findings via dashboards, presentations, reports, newsletters, portals or  intranet sites.  Celebrate achievements and encourage continued progress and feedback. If metrics are moving in the wrong direction, investigate quickly and determine an appropriate course of action.

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