There is a major problem with reporting. The writers often do not understand enough about the science of reporting. In addition, too many reports have been prepared monthly, which is far too late for prompt action.
The reporting framework used in an organization must accommodate the requirements of the different levels in the organization (board, senior management team, middle management, and the various teams) and the reporting frequency that supports timely decision making. This chapter displays some better practice formats that will help speed up this vital step. This chapter should be read in conjunction with the white papers and books written by Stephen Few1 (see www.perpetualedge.com). Stephen Few is the expert in this field, having written Amazon's top three bestselling books2 on data visualization.
Data visualization is an area that is growing in importance. No longer is it appropriate for well-meaning accountants and managers to dream up report formats based on what looks good to them. There is a science behind what makes data displays work.
All reporting of winning KPIs and other performance measures is vastly improved if one adopts Few's design techniques in all forms of balanced-scorecard reporting.
Stephen Few has come up with a very useful list of common pitfalls in dashboard design which include:
Exceeding the boundaries of a single screen | Here Few is warning us to think about the design carefully and avoid giving the reader the option to access different options. We need to define what should be seen instead of leaving the manager to click on an icon to get the important data. |
Supplying inadequate context for the data | Far too often we show dials which do not give enough information as to what is good or bad performance. |
Displaying excessive detail or precision | Graphs should summarize the information and be a big picture view. The graph should have no more than a five point scale and this should avoid unnecessary precision, e.g., $5m instead of 5,000,000.00. |
Starting scale midway | Often to emphasize a point the press will show an exchange rate between a very narrow band, say US$ to Euro between a five cents range magnifying the movement. Few is adamant that this may mislead and give rise to poor decisions. Better to express the graph starting the scale from zero. |
Choosing inappropriate media in displays | Choosing the wrong graph, especially a pie chart! Few points out that it is far better to use a horizontal bar graph instead of a pie chart. |
Introducing meaningless variety | Introducing a myriad of different graphs just because we can do them. |
Arranging the data poorly | Not linking issues together and not positioning graphs about the same issue together on the dashboard. |
Using a lot of color to highlight everything | Few points out that many readers cannot distinguish between certain colors and it is better to be a minimalist with color, only using red to highlight areas of concern. |
Cluttering the screen with useless decoration | Managing the white space is important. Only things that matter to the reader should be included. |
Each one of these is explained in detail in Few's white paper on the topic, “Common Pitfalls in Dashboard Design,” available on www.perceptualedge.com/articles.
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 14.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.
Exhibit 14.1 Example of a Daily KPI Report
Planes more than two hours late | |||||||||||
Time: 4.30pm 12 Sept 201X | Number of planes over one hour late | ||||||||||
Statistics of last stop | Contact details | ||||||||||
Flight number | Arrival late by | Departure late by | Time added | Region manager's name | Current time at location | Work | Mobile | Home | Past 30 days | 30-day average of past three months | 30-day average of past six months |
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 |
Another benefit of providing senior management with daily/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.
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 14.2. This report should be accessible by HR staff, the senior management team, and the CEO.
Exhibit 14.2 Example of a Daily HR Exception Report
Position offers still outstanding | Contact details | Details | |||
Candidate | Home | Mobile | Manager | Days outstanding | |
Financial Controller | Pat Curruthers | xxxxx | xxxx | Jim Curruthers | 3 |
Stores manager, Brisbane | Basil John | xxxxx | xxxx | 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 | xxxx | 3 | 1 |
Team yy | Sally Smith | xxxxx | xxxx | 4 | 1.25 |
Team zz | Jim Curruthers | xxxxx | xxxx | 2 | 1.5 |
Team ss | Ted Smith | xxxxx | xxxx | 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 | xxxx | 10 | Yes |
xxx xxxxxxxxxxx | Sally Smith | xxxxx | xxxx | 15 | Yes |
xxxxx xxxxx | Ted Smith | xxxxx | xxxx | 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 |
Some KPIs need only be reported weekly. Set out in Exhibit 14.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.
Exhibit 14.3 Weekly KPI Report
Source: David Parmenter, Key Performance Indicators: Developing, Implementing, and Using Winning KPIs, 2nd ed. Copyright © 2010 by David Parmenter. Reprinted with permission of John Wiley & Sons, Inc.
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 14.4.
Exhibit 14.4 Example of the Weekly Human Resources Report
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 |
There are endless ways these can be shown (see Exhibit 14.5) 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.
Exhibit 14.5(a) Examples of a Monthly Report to Management
Source: Used with the permission of Inside Info, www.insideinfo.com.au.
Exhibit 14.5(b) Examples of a Monthly Report to Management
Source: Used with the permission of Stephen Few, www.perceptualedge.com.
Stephen Few has introduced a new concept called “bullet” graphs. These are particularly powerful when combined with Edward Tufte's5 “sparkline” graphs, see Exhibit 14.6.
Exhibit 14.6 Combination of “Sparklines” and “Bullet” Graphs
Source: Used with the permission of Stephen Few, www.perceptualedge.com.
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) through 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 14.5b, 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 14.7 is an example of an icon staff report that covers the critical success factors and reminds staff about the strategies.
Exhibit 14.7 Example of a Monthly Report to Staff
Source: David Parmenter, Winning CFOs: Implementing and Applying Better Practices. Copyright © 2011 by David Parmenter. Reprinted with permission of John Wiley & Sons, Inc.
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. As mentioned in Chapter 2, it is a myth that a balanced scorecard can report progress to both management and the board.
To me, KPIs are the very heart of management. Used properly, many of them are monitored 24/7 or at least weekly; they are certainly not measures to be reported monthly or bimonthly to the board.
We need 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 dashboard.
A dashboard should be a one-page display (see Exhibit 14.8) with the graphs, summary financials, and commentary all appearing on the page.
Exhibit 14.8 Board Dashboard on a Large (A3/U.S. Fanfold) Page
To help teams, there are ten good KRIs graphs in Exhibit 14.9 that you might want to use.
Exhibit 14.9 Key Result Indicators for a Board
Source: David Parmenter, Winning CFOs: Implementing and Applying Better Practices. Copyright © 2011 by David Parmenter. Reprinted with permission of John Wiley & Sons, Inc.
Staff satisfaction: No different or less important than customers' satisfaction. As one person said, “Happy staff make happy customers, which makes happy shareholders.” If you believe in this connection, run a survey now! A staff satisfaction survey need not cost the earth and should never be done covering all staff; instead it should be replaced by a rolling survey. See my article on “How to seek staff opinion and not blow your budget” www.davidparmenter.com. |
![]() |
Expenses to revenue as a ratio: The Board should be interested in how effective the organization has been in utilizing technology and continuous improvement to ensure cost of operations is tracking well against revenue. |
![]() |
Customer satisfaction: This needs to be measured at worst every three months by using statistical samples and focusing on your top 10 to 20 percent of customers (the ones that are generating most if not all of your bottom line). This process does not need to be overly expensive. If you think once a year is adequate for customer satisfaction, stick to running a sports club as you are not safe in the public or private sectors. |
![]() |
Value of new business: All businesses in the private sector need to focus on the growth of their rising stars. It is important to monitor the pickup of this new business, especially among the top 10 to 20 percent of customers. |
![]() |
Net profit before tax (NPBT): Since the board will always have a focus on the year-end, it is worthwhile showing the cumulative NPBT. This graph will include the most recent forecast which should be updated on a quarterly basis. Access my article “Throw away your budget” www.davidparmenter.com. |
![]() |
Health and safety: All boards are interested in this area as the well-being of staff is a much higher priority these days. |
![]() |
Return on capital employed: The old stalwart of reporting. The difference now that it is no longer a KPI, but a KRI. |
![]() |
Cashflow: This would be projected out at least six months forward. ![]() |
|
Capacity: This monitors the capacity of key equipment and facilities. It would go forward at least 6 to 12 months. The board needs to be aware of capacity limitations, and such a graph will help focus the board on new capital expenditure requirements. |
![]() |
Operational efficiency: This measure looks at the operational efficiency of key units (e.g., key plant and equipment). |
![]() |
There are some key points that need to be understood about the graphs in Exhibit 14.9, including:
Set out in Exhibits 14.10 and 14.11 are examples of the weekly and monthly reporting a team would do to monitor its own performance. The examples shown are in Excel, a useful template tool until a more robust and integrated solution is found.
Exhibit 14.10 Example of a Weekly Team-Progress Update
Source: David Parmenter, Winning CFOs: Implementing and Applying Better Practices. Copyright © 2011 by David Parmenter. Reprinted with permission of John Wiley & Sons, Inc.
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 14.11 Example of an IS Monthly Team Balanced Scorecard
Source: David Parmenter, Winning CFOs: Implementing and Applying Better Practices. Copyright © 2011 by David Parmenter. Reprinted with permission of John Wiley & Sons, Inc.
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 14.12 shows how the reporting of performance measures should work in a private, public, or not-for-profit organization.
Exhibit 14.12 Performance Reporting Portfolio
Source: David Parmenter, Winning CFOs: Implementing and Applying Better Practices, copyright © 2011 by David Parmenter. Reprinted with permission of John Wiley & Sons, Inc.
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 14.12, we show that teams will be monitoring performance through their scorecards. If a team is involved with a KPI, they would also be monitoring the KPI reporting shown in the left-hand column of Exhibit 14.12.
It is important to design your reports based on the user's technology. Many 24/7, daily, or weekly reports will now be read via the user's phones and tablets. See Exhibit 14.13 for an example from Stephen Few.6 There is a whole raft of suppliers who can revolutionize your reporting. Some of the current solutions on offer, at the time of writing, are:
Exhibit 14.13 An IPhone Dashboard
Source: Used with the permission of Stephen Few, www.perceptualedge.com
There are many more. Start by asking your GL provider who are the best users of our GL who are within a day's travel from you. Contact them and organize a benchmarking visit. During the discussions about better use of the GL ask them, “What reporting tool do you use?” These companies will have done the homework for you, and you will be able to see their clever use of this technology.