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

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

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th