There is a major problem with the reporting of performance measures. The report writers often do not understand enough about performance measures, report monthly, which is far too late for prompt action, and are often unaware of the science of data visualization.
I recommend the reader follow Stephen Few's work,1 which can be accessed from his website (www.perpetualedge.com) and his three bestselling books on data visualization (see Chapter 7).
The reporting performance measures must reflect the four types of measures used (see Chapter 19) and accommodate the requirements of the board, senior management team, middle management, and the various teams.
Reporting measures to management needs to be timely. As mentioned previously, KPIs need to be reported 24/7, daily, or, at the outside, weekly; other performance measures can be reported less frequently (monthly and quarterly).
The main KPIs are reported 24/7 or daily. Exhibit 19.1 shows how KPIs should be reported on the intranet. Some form of table giving the contact details, the problem, and some history of performance is required. Another benefit of providing senior management with daily or weekly information on the key performance areas is that the month-end becomes less important. One government department had a 9 o'clock news report every morning covering the processing of benefit payments by each office around the country. Regional management teams were able to compare their service levels and achievements on a daily basis. In other words, if organizations report their KPIs on a 24/7 or daily basis, management knows intuitively whether the organization is having a good or bad month.
Planes more than two hours late | |||||||||||
Time: 4.30pm 12 Sept 201X | |||||||||||
Number of planes over one hour late | |||||||||||
Flight number | Statistics of last stop | Region manager's name | Current time at location | Contact details | Past 30 days | 30-day average of past three months | 30-day average of past six months | ||||
Arrival late by | Departure late by | Time added | Work | Mobile | Home | ||||||
BA123 | 01:40 | 02:33 | 00:53 | Pat Carruthers | 18:45 | xxxxx | xxxxx | xxxx | 4 | 4 | 2 |
BA158 | 01:45 | 02:30 | 00:45 | Basil John | 10:48 | xxxxx | xxxxx | xxxx | 2 | 3 | 1 |
BA120 | 01:15 | 02:27 | 01:12 | xxxxxxx | 20:45 | xxxxx | xxxxx | xxxx | 4 | 4 | 7 |
BA146 | 01:25 | 02:24 | 00:59 | xxxxxxx | 21:45 | xxxxx | xxxxx | xxxx | 5 | 4 | 4 |
BA177 | 01:15 | 02:21 | 01:06 | xxxxxxx | 22:45 | xxxxx | xxxxx | xxxx | 1 | 4 | 2 |
BA 256 | 01:35 | 02:18 | 00:43 | xxxxxxx | 23:45 | xxxxx | xxxxx | xxxx | 5 | 4 | 5 |
BA124 | 01:45 | 02:15 | 00:30 | xxxxxxx | 00:45 | xxxxx | xxxxx | xxxx | 2 | 4 | 6 |
Total | 7 planes |
EXHIBIT 19.1 Example of a daily KPI report
Source: David Parmenter, Key Performance Indicators: Developing, Implementing, and Using Winning KPIs, 3rd Edition, copyright © 2015 John Wiley & Sons, Inc. Reprinted with permission of John Wiley & Sons, Inc.
It is vital that key exceptions are reported to the chief executive officer (CEO) immediately when they occur. The following issues need to be addressed in private and public organizations:
The aforementioned issues are set out in a suggested intranet-based report (see Exhibit 19.2). This report should be accessible by HR staff, the senior management team, and the CEO.
Position offers still outstanding | Candidate | Contact details | Details | ||
Home | Mobile | Manager | Days outstanding | ||
Financial controller | Pat Curruthers | XXXXX | XXXXX | Jim Curruthers | 3 |
Stores manager, Brisbane | Basil John | XXXXX | XXXXX | Sally Smith | 3 |
Teams not represented in the in-house courses due in next two weeks | Manager | Work | Mobile | Expected numbers from team | Average training days of team in past six months |
Team xx | Jim Curruthers | XXXXX | XXXXX | 3 | 1 |
Team yy | Sally Smith | XXXXX | XXXXX | 4 | 1.25 |
Team zz | Jim Curruthers | XXXXX | XXXXX | 1.5 | |
Team ss | Ted Smith | XXXXX | XXXXX | 1 | 0 |
Staff who have been ill for over two weeks | Manager | Work | Mobile | Length of illness | Back to work program started |
xxxx xxx | Jim Curruthers | XXXXX | XXXXX | 10 | Yes |
xxx xxxxxxxxxxx | Sally Smith | XXXXX | XXXXX | 15 | Yes |
xxxxx xxxxx | Ted Smith | XXXXX | XXXXX | 25 | No |
Accidents and breaches of safety | Manager | Work | Mobile | Remedial action | |
Pat Gow was in a car crash, unhurt but needs two weeks' recovery time | Jim Curruthers | xxxxx | xxxx | Increase participation in advanced driving courses paid by company | |
Staff who have handed in their notice today | Staff member | Work | Mobile | Length of service | Manager |
Susan George | Tom Bent | xxxxx | xxxx | <1 | John Bull |
John Doe | Sally Shell | xxxxx | xxxx | <1 | John Bull |
Jenny Gilchrist | Ted Snell | xxxxx | xxxx | 15 | Sarah Marshall |
EXHIBIT 19.2 Example of a daily HR exception report
Source: David Parmenter, Key Performance Indicators: Developing, Implementing, and Using Winning KPIs, 3rd Edition, copyright © 2015 John Wiley & Sons, Inc. Reprinted with permission of John Wiley & Sons, Inc.
Some KPIs need only be reported weekly. Exhibit 19.3 is an example of how they could be presented. Note that while all the KPIs will be graphed over time, at least 15 months, only the three KPIs showing a decline would be graphed. The other two KPI graphs would be maintained and used when necessary.
Management will need some weekly reports covering result indicators and performance indicators. There thus will be a mix of financial and nonfinancial measures.
There are some HR issues that the CEO needs to focus on weekly. They are not as critical as the intraday or daily HR exceptions, and thus are not considered KPIs.
The following HR issues need to be addressed in most organizations:
The suggested intranet-based report that should be accessible to the HR staff, senior management team, and CEO is shown in Exhibit 19.4.
Manager details | |||||
New staff who have not attended an induction program | Start Date | Name | Office | Mobile | Staff turnover in past two years |
Alan Bevin | 12/12/xx | Pat Curruthers | xxxxx | xxxx | 30% |
Carl Dodds | 11/11/xx | Sam Smith | xxxxx | xxxx | 40% |
In house training courses due in next two months | Enrollments | Expected numbers | Date of course | Days left | |
First Aid | 5 | 20 | xxxxx | 25 | |
Supervisors Part 1 | 3 | 45 | xxxxx | 18 | |
Leadership part 2 | 40 | 60 | xxxxx | 14 | |
Presenting | 6 | 20 | xxxxx | 15 | |
Days lost | |||||
Teams with above average sick leave | This month | Days per employee | Average per month for past three months | ||
Team xx | 5 | 1.5 | 4 | ||
Team yy | 8 | 2 | 7 | ||
CEO recognitions planned for next week | Manager | Date | |||
Project ______________ | Jim Curruthers | xxxxx | |||
Finance team | Sally Smith | xxxxx | |||
________________________ | Ted Smith | xxxxx |
EXHIBIT 19.4 Example of the weekly human resources report
Source: David Parmenter, Key Performance Indicators: Developing, Implementing, and Using Winning KPIs, 3rd Edition, copyright © 2015 John Wiley & Sons, Inc. Reprinted with permission of John Wiley & Sons, Inc.
There are endless ways these can be shown (see Exhibits 19.5 and 19.6), through icons, gauges, traffic lights, and so on. There are many reporting tools available that are more robust than a basic spreadsheet. It is highly likely that your organization has the license to use at least one such reporting tool.
Stephen Few has introduced a new concept called bullet graphs. These are particularly powerful when combined with Edward Tufte's4 sparkline graphs (see Exhibit 19.7).
A sparkline graph looks like a line graph without the axes. Even with this truncated diagram you can still see the trend. The bullet graph shows different details about current performance. The shades used range from dark gray (to indicate poor performance) to lightest gray (to indicate good performance). The dark vertical line indicates a comparative measure such as a target or last year's result.
Stephen Few is very cautious about the use of color. He points out that many readers will have some form of color blindness. In Exhibit 19.6, the only use of color would be red bullet points indicating the exceptions that need investigation and follow-up.
It is a good idea to have some form of monthly icon report for staff. If this report happens to be left on a bus, it would not be damaging to the organization if it found its way to a competitor. Icon reports are ideal because they tell you what is good, what is adequate, and what needs to be improved without giving away core data. Exhibit 19.8 is an example of an icon staff report that covers the critical success factors and reminds staff about the strategies.
Entities in the private and public sectors need to report to a board, a council, or an elected government official. To simplify, let's call the reporting body a board.
In most organizations that have boards, there is a major conflict of interest over what information is appropriate for the board to receive. Because the board's role is clearly one of governance and not of management, it is totally inappropriate to be providing the board with KPIs. It should receive indicators of overall performance that need only be reviewed on a monthly or bimonthly basis. These measures need to tell the story about whether the organization is being steered in the right direction at the right speed, whether the customers and staff are happy, and whether we are acting in a responsible way by being environmentally friendly.
These measures are called key result indicators (KRIs). Typically, a board would need to see between 6 and 12 graphs covering the critical success factors and all six balanced scorecard perspectives. These measures work particularly well in helping the board focus on strategic, rather than management, issues, and they will support management in their thrust to move board meetings away from the monthly cycle. These KRIs are best reported in a board dashboard, which was discussed in Chapter 8 and is shown again in Exhibit 19.9.
Exhibits 19.10 and 19.11 are examples of the weekly and monthly reporting a team would do to monitor its own performance.
Weekly Progress Update During May | |||
Week 1 | Week 2 | Target (month) | |
Proactive visits to in-house clients | 0 | 1 | 6 |
Number of staff recognitions made | 0 | 0 | 6 |
Projects in progress | 7 | 7 | <8 |
Reports/documents still in draft mode | 12 | 15 | <5 |
Initiatives underway based on satisfaction survey | 0 | 0 | 5 by 30 June |
EXHIBIT 19.10 Example of a weekly team-progress update
The examples shown are in Excel, a useful template tool until a more robust and integrated solution is found. The weekly report tracks those measures too important to leave until the end of the month. Team reports should be communicated only to the team members until they are proud enough to report their performance to the rest of the organization on the intranet.
Exhibit 19.12 shows how the reporting of performance measures should work in a private, public, or not-for-profit organization. The important reports are the daily and weekly reports shown in the left-hand column. These are seen by the senior management team and the relevant operational staff. Some of these would be intranet-based, being updated 24/7 (e.g., late planes in the sky). At month's end, summary information would be given to:
In the right-hand column of Exhibit 19.12, we show that teams will be monitoring performance through their scorecards. If a team is involved with a KPI, team members would also be monitoring the KPI reporting shown in the left-hand column of Exhibit 19.12.
To assist the finance team on the journey, templates and checklists have been provided. The reader can access, free of charge, a PDF of the suggested templates from www.davidparmenter.com/The_Financial_Controller_and_CFO’s_Toolkit.
The PDF download for this chapter includes: