Useful Metrics that have nothing to do with measurement.

There are many ways that metrics tie organizational strategy to execution including organizational alignment, clear outcomes, refined action plans, employee motivation, compensation benefits and more, but one of the most powerful applications of metrics has nothing to do with measurement at all.

One of the top ten reasons for failure in a strategic planning process is that the plan is written, then it gets placed on a shelf where it collects dust. Certainly communicating the plan immediately after its preparation is important, but without constant reinforcement, the strategic plan's message grows stale and its message becomes forgotten.

The powerful thing about metrics is that measurement must be continuous. Just as an organization needs to turn out monthly financials (financial metrics), a well-executing organization will track key metrics on a monthly basis as well. Ideally these metrics will be on a dashboard and shared across the organization.

One of the greatest strengths of metrics, then, is that they serve to continuously reinforce the strategic plan to all team members on an ongoing basis. They keep the organization focused on the few Most Important things that need to be done and help to maintain organizational focus against the threat of day to day entropy that takes over daily activities.

So, by all means measure for measurement's sake, but also remember to measure for communications' sake.

Metrics: Right or Left Brain Activity?

I was reviewing one of my favorite books, Daniel Pink's A Whole New Mind: Why Right-Brainers Will Rule the Future and thinking about metrics and whether they are a right brain or left brain activity.

The initial response, of course, is that metrics are a numbers-based, quanitification-oriented activity that must be a left brain function. These are logical, step-by-step activities if they are taken at face value. Who are the primary metricians in a corporation? The accountants - who, by definition are left-brainers.

The reason Daniel Pink got me thinking about this is that when properly deployed, metrics are not about measuring routine activities, but rather they are about conceptualization, systems-level thinking and big-picture approaches to problem solving in business.

Metrics are borne of big ideas. Sam Walton is well known for saying "you get what you measure." The question about "what do you want to get" in a company is typically a board level/executive level function that includes setting the company's vision and mission, clarifying its values and setting its goals.

Metrics are how you go about achieving the vision, mission, values and goals. There is a lot of creativity involved in translating those high level objectives into specific, measurable actions that are carried out by each and every member of the organization. When you have a goal such as "Provide world class customer service." there is not much for your staff to dig their teeth into in how they carry out their day-to-day activities.

Hermes is the greek figure who served as the messenger of the gods. His job was to translate the deities' messages into a form that was understood by the mortals. The job of creating organizational metrics is no less challenging than this. Abstract concepts such as "world class customer service" consist of many critical tasks and projects that must be carried out, each of which has measurable outcomes. By focusing on these measurable outcomes we empower teams to use their creativity and to gain ownership in how the outcomes are achieved, while creating a crystal-clear description of what specifically needs to happen.

After all this has happened, it falls to someone to collect, organize and present the metrics data. And "yes", I suppose this is a left-brain activity, but this collection and presentation of data is not what metrics is about any more than cleaning paint brushes is what an artist does when he is creating a painting. Cleaning the brushes is an integral part of the process, but comes well after the creativity has occurred.

Metrics: Focus on the Future or the Past?

Are Metrics Based in the Future or the Past?

When you hear the word “metrics” what do you think of? Measurement of results and outcomes of a process? Or do you think of metrics tied to strategic initiatives with future outcomes?

Your perception of metrics as future or past based will have a lot to do with how you use metrics and what you can get out of them.

A good example of this distinction is the way that W. Edwards Deming approached quality management. One of Deming’s “Fourteen Points for Management” as described in his book Out of the Crisis (p. 23-24), was that companies need to “cease dependence on inspection to achieve quality. Eliminate the need for inspection on a mass basis by building quality into the product in the first place.” Thus, Deming’s approach was not to use metrics in the past (dependence on inspection), but rather in the future (building quality into the product in the first place.)

Metrics is at its most powerful when it is coupled with the strategic planning process. Ultimately it becomes cyclical so that it drives process in the beginning of a change and then measures results as they become available. Organizations then practice continuous process improvement by taking the resulting metrics into account when fine tuning their strategic plans, until ultimately the desired results are achieved.

Six Dilemmas Challenging Organizational Execution

Strategic planning commonly involves establishing a vision and mission for an organization. From there, objectives are determined and sometimes an action plan is created to help achieve the objectives. Unfortunately, many organizations stop there and the plan goes on the shelf with little more than lip service when it comes to execution.

Why do organizations so often drop the ball when it comes to carrying out their most important goals? There are many reasons and, to be sure, achieving change is difficult. The strategic use of metrics can help with this challenge. Some of the ways that metrics can be applied to organizational change include:

1) Dilemma: Everyone is on board with the action plan, but the goals appear to be intangible and it is not clearly understood how they will be achieved.

Metrics force an organization to define what it is that they REALLY want in terms of outcomes and behaviors. There is nothing so difficult that it cannot be measured, although finding the right measures requires special skills.

2) Dilemma: There is organizational resistance to change.

Metrics help an organization to clearly understand "who is on board" and who is not. Reward systems built around clear metrics provide inducement to team members to get on board and disincentives to those who passively or actively resist the change.

3) Dilemma: Everyone is excited about achieving the new goals, but different groups within the organization have different ideas about how to achieve those goals.

Use clear metrics to align your teams together with an agreed upon action plan that focuses everyone's actions on the same goals. Metrics alone will not ensure alignment because there may be many ways to achieve agreed upon measures. In this case, the important thing is to understand that metrics can be deployed at many levels of specificity. You may measure a very low level of specificity by setting a goal of increasing organizational profits, for example. There are virtually infinite ways that teams may work to achieve this goal. If your metrics have very high levels of specificity, however, then tasks are more easily aligned. So, instead of saying that your goal is to increase organizational profits, an organization may say that it will increase sales by 5% by engaging in a Search Engine Marketing campaign with a budget of $50,000. Within this specific goal, there should be a host of metrics such as cost per click, click through ratios, conversion rates, cost per sale, etc. There may be many such specific goals that all support the more general goal.

4) Dilemma: The problem with metrics is that "you might just get what you asked for."

Someone actually told me this at a conference earlier this year. Of course, the powerful thing about metrics is that you might just get what you asked for. Anything that is powerful requires special handling and forethought. If you choose the wrong metrics, you may get the wrong outcomes. For this reason, a rigorous process, complete with risk analysis and feedback from key stakeholders is critical. Also, organizations need to be flexible. If you don't get your metrics right the first time, by all means, come back and adjust them until they are right.

5) Dilemma: Our organization can't get perfect measurement data, so there is no point in measuring anything.

It is true that perfect measurement data is rarely, if ever, available. The goal of using metrics is not to achieve perfect measurement, it is to drive organizational behaviors aligned towards agreed upon outcomes that help to achieve the organization's mission and vision. Your metrics must be chosen carefully so that they not only support the desired outcomes, but so that when compensation is tied to metrics, the system is perceived as being fair and just by those who are participating.

6) Dilemma: Sometimes the cost to collecting the data can exceed the benefit of the behavior that is measured.

An organization should never use data collection methodologies where the cost of collecting the data exceeds the benefit. Organizations are often surprised with just how many metrics they may already have at their fingertips where the cost of collecting them is close to zero. Every organization is experienced with metrics and invests in them. Financial metrics are a requirement and entire teams of people are deployed to collect these metrics so that income statements and balance sheets may be prepared, taxes paid, payroll met, etc. The most expensive metrics to gather are those that are in the past. Transactions need to be researched and reports prepared. It is always easiest and most cost effective if metrics can be built into the day-to-day processes that an organization conducts, so that at the end of each period, the measures are easily available.

What are the steps to effective performance measurement?

Effective performance measurement is the cornerstone of successfully executing organizational change, and yet, many companies do not have effective performance measurement programs. There are many reasons for this ranging from a lack of buy-in to misperceptions about the use of metrics to the belief that all important factors cannot really be measured.

The first thing to keep in mind is that all measurement is for the purpose of executing change. You want something to happen so you develop a plan and as a part of that plan you decide what the Key Performance Metrics are that demonstrate successful execution of the plan. People struggle with metrics because it is hard work. It's one thing to come up with a set of objectives and strategies in a brainstorming meeting, but quite another to dig down deep and determine what it really means to successfully accomplish what you've set out to do. Typically goals are vague and metrics are specific. It's a lot easier to be vague!

The first step in a performance measurement program is to figure out your "critical questions." Start by asking questions about what you want to accomplish. Try using the Toyota method of "five whys". Keep asking "why" until you get to a root answer. This is what Socrates did in ancient Greece. The effect of his questioning was that he was not often very popular. People were shown to have little understanding of the fundamentals underlying their assumptions. Socratic dialogue is a great way to discover what you really need to measure.

The critical questions ultimately lead to which metrics you will choose for your effort. Remember to measure only the critical elements because each measurement takes time and costs your organization and the more metrics you collect, the more chance you run of diluting the importance of each measure.

The next step is to develop a process for measurement. Who will do the measuring? How often? In what medium will the data be stored? What quality measures will be put into place to ensure the data collection is good? Are there metrics already being captured by other processes or automated systems that can be used? How do your information systems talk to one another? Can the data be updated automatically and fed into a dashboard?

So now you've decided what to measure, how to measure it and where to store it. The next step is to develop a dashboard or other methodology for reporting your metrics. The objectives are to deliver clean information in a format that communicates trends, "normal" ranges and variations, benchmarks, targets and current values. The best dashboards are automatically updated and can present information in real time. For many organizations an Excel spreadsheet posted on an Intranet once a month is sufficient. Part of your reporting process will be to determine how to present your information, to whom the information will be presented and how often it should be updated.

Periodic Review: Strategic plans rarely go exactly as planned. There are infinite environmental variables that will change during the course of plan execution and it is necessary to review results and adjust the plan on a regular basis. This could be daily in some cases, weekly in others, monthly or quarterly. I would recommend at least monthly updates because if too much time elapses between meetings, the initiative can go way off course or worse, momentum can be lost. Regular reporting and review ensures that everyone is aware of accountability and their role in the success of the project.

Iteration: One of the functions of the periodic review is to ensure that targets are being met, but sometimes a mid-course trend analysis might show that the beginning of the year targets are no longer relevant. There may be game-changing events that require immediate strategic revision and iteration of the strategy. The iterative process is a continuous improvement based on execution, test, review, revision and execution of the new strategy. The iterative process acknowledges that information is imperfect during the planning process and that it is impossible to predict the future. Organizations that practice iteration are quick to respond to changes in the situation and adjust to maintain or gain competitive advantage.

Metrics work hand in hand with scenario planning when metrics are used as "triggers" to implement a scenario plan. The time to review scenario plans is during these regular metric review meetings.