This chapter is for those talented in-house staff members who have been asked to run the KPI project. One day your project may well be a leading case study. What a legacy to your organization and the other organizations that you inspire.
I am hopeful that you are carrying the title chief measurement officer (CMO). The importance of this has been discussed in Chapter 2 where I point out that it is a myth that a KPI project can be run by a consultant. In Chapter 7 I talk about the foundations stones and in Appendix B I set out a draft job description for the role.
As CMO you will need a mentor, or, as Jack Welch1 advised, a cluster of mentors. I suggest the following:
If you have been selected as a facilitator to assist in the development of performance measures, you will need to be completely familiar with Chapters 1 through 14 of this book. This resource kit provides you with three additional components to assist you in executing your role, namely:
It is important that the facilitator's role is one of facilitation and mentoring, not project leadership. The facilitator should have little hands-on involvement after the setup steps have been completed. The message in this KPI book is that project team members, coordinators, and teams should take on significant roles themselves. The facilitator's particular role is to guide the overall process, providing assistance and resources as required.
While I have merged the original 12 steps into six stages, it is important that the facilitator ensures that each of the 12 steps is understood. Each of the 12 steps contains questions and/or worksheets to be completed as the project team progresses through the implementation. The facilitator should ensure that these questions and worksheets are tailored to the organization and then followed.
A rushed and noncollaborative approach to the development and implementation of performance measures combined with a profound misunderstanding of the differences among key result indicators (KRIs), result indicator (RIs), performance indicators (PIs), and KPIs will result in failure.
To remind you of what the 12 steps are and how they have been merged into the six stages I have repeated the diagrams from Chapter 6 (see Exhibits 15.1 and 15.2).
Exhibit 15.1 Twelve-Step Implementation 16-Week Timeline (From First Two Editions of This Book)
Exhibit 15.2 Twelve Steps Merged into a Six-Stage Process
To assist I have provided a draft checklist of the main tasks the facilitator will need to consider in PDF format for you to download. It is important that the facilitator's role is just that; it should never become the project manager's role.
Sports coaches often talk about doing the fundamental or basic things well to ensure success. This is good advice for the CMO and the external facilitator because at times the KPI implementation process will appear to be quite involved and complex.
As you carry out your role, always review the seven foundation stones to check that your efforts and the project do not stray away from these key building blocks (see Exhibit 15.3).
Exhibit 15.3 The Seven Foundation Stones in the Winning KPI Methodology
Although it would be very gratifying to think that this book could provide you with everything you need to implement winning KPIs successfully, I can safely say, with years of experience behind me and a few gray hairs to add to the mix, this is not possible.
The following references, covering books, webcasts, and third parties, will also assist you in creating winning KPIs.
I would recommend that you:
To enable you to improve access to KPIs, I have listed some books that will help you with this project. Read them and leave them in an accessible area as a reference guide and a required read for all new team members.
Stephen Few conducts workshops around the world. Make sure you view his website to find the workshop nearest to you. You will not regret attending one of his workshops.
This book is a resource for anyone in the organization involved with the development and use of KPIs. It is desirable that all KPI project team members, the external project facilitator, team coordinators, and local facilitators (if required) have their own book to ensure all follow the same plan. Team members are expected to take the book with them when meeting staff and management, as they will be able to clarify issues by using examples from the book. (Note that this book is copyrighted, so it is a breach of the copyright to photocopy sections for distribution.)
Running good workshops is an acquired skill, and the KPI team should receive specific training in this area. When I am running a workshop, I follow some basic rules. I set these out more as a guide rather than an instruction. Experienced facilitators will no doubt have their own successful methods.
Kaplan and Norton, in their groundbreaking book The Balanced Scorecard: Translating Strategy into Action,10 indicated that 16 weeks is sufficient time to establish a working balanced scorecard with key performance indicators (KPIs). However, organizations of all sizes and complexity stumble with this process, and 16 weeks easily turns into 16 months. The key to success is to learn 11 key lessons:
I have been working with performance measures for many years and have spent untold hours endeavoring to unlock their secrets. Over the years one thing has become abundantly clear: you need a measurement expert in-house. Dean Spitzer called this the chief measurement officer.
I have now come to the conclusion that I have not emphasized enough the importance of this in-house resource in my earlier work.
Performance measurement is worthy of more intellectual rigor in every organization that is on the journey from average to good and finally to great. The chief measurement officer would be part psychologist, part teacher, part salesperson, and part project manager. I have discussed this position throughout this book and have included a draft job description in Appendix B.
In most of the implementations I have observed, my advice to appoint a KPI team leader, and making them where possible full time, has been compromised due to workload commitments. In every case this has delayed and put the project on the back foot. From around 250 people this position should and must be full time. In small organizations this duty must be at least half the workload and much daily operational activity reassigned so that the incumbent has a chance to focus and create some momentum in the project.
Peter Drucker said, “Never give a new job to a new person”—he called it a widow maker. When an organization wants a new system implemented, it is very tempting to hire someone who has expertise, a consultant, or a permanent appointment. Drucker pointed out that they do not stand a chance as staff members who are concerned about the change will do their utmost to destabilize the project.
Instead you need to appoint an in-house person best suited for the role, someone who is well respected in the organization, who can call on favors when required. Staff will support the new initiative when it is led by such an appointee.
The CMO position should report directly to the CEO, as befits the knowledge and diverse blend of skills required for this position. Only when we have this level of expertise within the organization can we hope to move away from measurement confusion to measurement clarity.
Appointing a CMO will give the project the best chance of success.
I would argue that more than half the new initiatives that are declined were undersold. In other words, given the right approach the initiative would have gone ahead.
If you are not prepared to learn the skills to cover the common deficiencies in a selling change process, you are better off playing golf or burying yourself in a process. Selling change requires a special set of skills, and we all can and should get better at it. In Chapter 13 on selling change I point out:
The SMT attitude is crucial—any lack of understanding, commitment, and prioritizing of this important process will prevent success. It is common for the project team and the SMT to fit a KPI project around other competing, less important firefighting activities.
The SMT must be committed to the KPI project and to driving it down through the organization. Properly implemented, the KPI project will create a dynamic environment. Before it can do this, the SMT must be sold on the concept. This will lead to the KPI project's being treated as the top priority, which may mean that the SMT allows some of those distracting fires to burn themselves out.
Consider this quote from a senior consultant:
Senior staff view the development of the BSC as an end in itself and go through the motions to keep the boss happy. If the SMT is not strategic in its perspective and consequently does not see the BSC as a tool to help it better understand and manage the organization, this will be reflected in a loss of interest when the process of development gets tough, for example, when deciding on which KPIs to use and the trade-offs to be made. While the role of the SMT is important, the role of the CEO is critical. The CEO must be the central driver carrying the embryo BSC with him all the time, talking about it frequently, and so on.
Organizations sometimes find that support for the BSC flounders if a new chief executive takes the helm before full implementation. It is important to sell, sell, sell the benefits to all new SMT members through their emotional drivers or their points of pain.
The SMT will get a buzz from being involved in a dynamic project, and there will be wider ownership as the oracles put their full weight behind the cause.
Too often, time is spent debating the perspectives, their names, and the design of the scorecard. The SMT loves this time of intellectualizing; however, it does not create much value. It is easy to get carried away with the debate, spending months determining the perspectives while making little progress on defining the CSFs.
Too much time can be spent debating whether there are four, five, or six perspectives and what their names are. Let me save you some trouble. You will need:
Using the suggested six perspective names will mean that you are using a better practice perspective template for the first 6 to 12 months. After 12 months, the SMT and staff will have enough experience, knowledge, and understanding to fine-tune the perspective names to better suit the organization's needs.
The SMT members will invest the scarce time they have available for this project in more important areas.
The critical success factors (CSFs) determine organizational health and vitality and where the organization needs to perform well. Key result indicators (KRIs), result indicators (RIs), performance indicators (PIs), and KPIs are the actual performance measures, which naturally cascade from these CSFs. It is crucial that the SMT focus on providing the project team with CSFs. If this is done well, winning KPIs are much easier to find.
Most organizations know their success factors (SFs). However, few organizations have:
If your organization has not completed a thorough exercise to know its CSFs, performance measurement will be a random process. It will create an army of measurers producing numerous numbing reports, measurers who often “measure” progress in a direction very remote from the strategic direction of the organization.
CSFs identify the issues that determine an organization's health and vitality. When you first investigate CSFs, you may come up with 30 or so issues that can be argued are critical for the continued health of the organization. The second phase of thinning them down is relatively easy, as the more important CSFs have a broader influence, impacting many success factors. Better practice suggests that there should be only between five and eight critical success factors.
Once you have the right CSFs, finding the KPIs is much easier, as they will reside within these CSF factors. This process is performed by mapping the relationships (see Exhibit 15.4) and is explained in detail in Chapter 11. The CSFs that have the most influence—shown in Exhibit 15.4 as the critical success factor with four arrows going out—are the ones to focus on first. All of the organization's KRIs and KPIs will be measuring performance within these critical success factors.
Exhibit 15.4 Relationship Mapping to Find the CSFs
Finding an organization's CSFs is, I believe, the goal of management. It will have a profound impact on staff members, as for the first time they will know what their focus should be on a daily basis. It will also help link daily activities to strategy and improve all forms of performance reporting.
Many balanced scorecards fail because the wrong measures are used. In such exercises, all their measures are called KPIs. I argue that many organizations are not working with their true KPIs, measures with special characteristics that were discussed in Chapter 1.
Kaplan and Norton recommend no more than 20 KPIs. Hope and Fraser11 suggest fewer than 10 KPIs. The 10/80/10 rule is a good guide: 10 KRIs, up to 80 RIs and PIs, and 10 KPIs.
The KPI project team and SMT need to concentrate on identifying those 10 KRIs, 80 RIs and PIs, and 10 KPIs that really matter. They must have a good understanding of the characteristics of KRIs, RIs, PIs, and KPIs and be able to distinguish between them before they deliver any workshops.
Many organizations call every measure a KPI and end up with over 200, which will create confusion rather than clarity. All leading writers are saying the same thing: “Less is better.”
Many people confuse result indicators with KPIs. Sales, net profit, customer satisfaction, and return on capital employed are not KPIs, as they are a result of many events occurring. These examples are KRIs, as they are measures that give a clear picture of whether you are traveling in the right direction. If a problem exists, they show it, but they will not tell you what you need to do to correct it.
KRIs provide useful information to the board of directors, which should not be involved in day-to-day management. The KPIs lie several layers beneath the KRIs. The KPIs connect the “workface” to the chief executive officer (CEO). During the day or every morning, CEOs working with KPIs are contacting people directly, asking for explanations or giving recognition of their success. Not all teams will have KPIs, as they cannot influence them. These teams will have RIs and PIs. It is important to note that the 10/80/10 is for the whole organization and is repeated if you have a totally separate business unit (e.g., different business units selling umbrellas and ice cream).
The KPI team will immediately focus on the end product (the 10/80/10) and not try to identify 80 KPIs in 200-odd performance measures.
KPIs can be designed successfully by a small team. Kaplan and Norton have seen BSCs designed successfully by an individual who had an in-depth understanding of the business.
Notwithstanding this possibility, a team approach of between two and four full-time staff members is recommended, as set out in Chapter 9. The external project facilitator, if involved right at the beginning, should help the SMT pick a team. Research into personnel records is recommended, as many talented staff members who may already have some KPI experience are found in obscure places. You need to look for staff who have excellent presentation skills, knowledge of the organization and its market, a track record of innovation and completion, sound communication skills, and the ability to be cheerful under pressure (a recruiting trick of Sir Edmund Hillary). See Chapter 9 for recruitment suggestions.
The SMT needs to have the selected staff committed full time to the KPI project. By that I mean the family photos are removed from their desk and taken to the project team location. Their second in command will move into their office and undertake their duties, a succession-planning bonus.
Once selected, this team must have a direct reporting line to the CEO (see Exhibit 15.5). Any layer in between means that the SMT and CEO have not understood just what SMT commitment means.
Exhibit 15.5 KPI Team Reporting Directly to the CEO
Besides the KPI project team, the organization also needs to identify a liaison person (a coordinator) for each business unit and team. This liaison person needs to be knowledgeable about the operation and be available to provide detailed knowledge and feedback to project team members.
Senior managers should exclude themselves from the project team. A SMT member in the team will lead to a string of canceled meetings as the senior manager is caught in the firefighting activities that make up much of their working days. Even SMT members with the best willpower in the world can never be fully focused on just one project.
This action will lead to a carefully picked project team who, along with the coordinators, will have a good chance of success.
The exact structure of the KRIs, RIs, PIs, and KPIs is rarely right the first time. Kaplan and Norton agree with Nike and say “Just do it.” The SMT and KPI project team need to ensure that the project culture is a “just do it” culture. It is important to ensure that the project team does not spend too much time on research. The key references are this KPI book and The Balanced Scorecard: Translating Strategy into Action.12
A “just do it” culture means that the team will not have to rely on external experts to run the project. CEOs are often wary of large projects that they perceive to be managed by expensive international consulting firms. The past decade is littered with six- or seven-figure consulting assignments that have not delivered on the value expectations. A “just do it” culture brings the belief that the project team can do it. The external project facilitator's role here is to ensure that the project team members remain confident (but not overconfident) and have picked up all the required skills they will need (e.g., delivering persuasive KPI presentations). Read Chapter 2 for more guidance.
The project will be protected against procrastination and have a good chance of implementing the KPIs within a 16-week period.
The project team should promote the use of existing in-house applications for the collection and reporting of the performance measures for at least the first 12 months. Much can be done with standard applications, such as Excel, PowerPoint, SharePoint Team Services, and Access. Often there is no need to purchase specialized software at this stage. Any such purchases can be done more efficiently and effectively 12 months down the track. The appropriate timing for implementing software to aid in the collection and deployment of KPI data will, however, vary from organization to organization. Some organizations may have a resident application that performs this task well or may already know which application they will use for this task and thus can invest in the appropriate systems earlier.
Sophisticated intranet software is of great assistance and is most likely available in-house. These applications will help the team set up its intranet website so that anyone interested in the development of performance measures can obtain access and contribute. Such applications can provide preformatted lists with expiration dates to keep announcements current and a place to collaborate on the development of KPI documentation and reports in real time.
The team will need to update the intranet site frequently themselves. Updating is too important to be left to a systems administrator who is not part of the project.
Focusing on an immediate solution using existing in-house software will avoid compromising the project time scales by delays in pre-purchase assessments, purchasing, and implementing a new system.
During the 16 weeks, a number of performance measures will be found that, while not in the top 10 KPIs, still are highly relevant to business and service teams.
The project team needs to establish a database to record these measures and communicate them through a KPI intranet home page. The fields for the database are discussed in Chapter 11.
The database should show not only all the current teams' measures but also any discarded measures. The project team can then help the teams, business units, and divisions with consistency and completeness (e.g., one measure devised by one team can and should be used by others, where appropriate).
During the 16 weeks, it is important that the project team purge the database on a regular basis to eliminate duplication and ensure consistency (e.g., the KPI team can suggest to one team, “You might like to look at measure Y as teams A, B, and C are choosing to use it”).
This action will create a comprehensive and user-friendly resource for all.
Data visualization is an area that is growing in importance. No longer is it appropriate for us to dream up report formats based on what looks good in our eyes. There is a science behind what makes data displays work. The expert in this field is Stephen Few. Stephen Few has written the top three “best-selling” books on Amazon in this field.
I recommend that the SMT leave the design of the reporting formats (24/7, daily, weekly, and monthly reports) to the KPI team, trusting in their judgment. The SMT should tell the KPI project team that they will be happy to live with their formats.
The key is to seek agreement that suggested modifications will be recorded and looked into at the end of the agreed review period. It will come as no surprise that many suggested modifications will not stand the test of time.
The KPI project team should make good use of the reporting templates provided in Chapter 14 before attempting to develop any of their own.
Understand these two writers' views and you will improve your reporting of information, its attractiveness, and its ability to stimulate action.
Key result indicators, RIs, PIs, and winning KPIs should ideally be structured within a balanced scorecard. However, across the world, there have been many failed BSCs principally due to garbage in, garbage out.
The word scorecard may have negative connotations to management. If so, what about navigator, compass, or other directional terms to help sell the concept and galvanize participation? Changing the name is particularly important where existing management has prior negative experiences with balanced scorecards.
Some organizations offer a prize for the staff person who comes up with the best name.
This action creates a KPI project name that helps galvanize the organization behind it.
To assist the KPI project team on the journey, templates and checklists have been provided. The reader can access, free of charge, a PDF of the suggested worksheets, checklists, and templates from kpi.davidparmenter.com/thirdedition.
The templates include: