Death by 1,000 Dashboards? What Next for Board Reporting
A board dashboard should be a scalpel, not confetti. Used well, it helps directors see the few things that most need attention: strategy execution, risk appetite, financial and non-financial performance, emerging threats, exceptions and decisions required. Used badly, it becomes a data dump with better graphics.
The issue is not whether dashboards belong in board reporting. They usually do. The real issue is whether they are curated, reliable, intelligible and connected to board-level judgement. In Australian governance terms, that matters because boards cannot govern effectively without the right information, and information is only useful if directors can absorb it, test it and use it to hold management to account.[1]
What is a board dashboard?
A dashboard is a visual or semi-visual summary of key information, usually drawn from multiple underlying systems and presented through tables, charts, indicators, thresholds and commentary. In a board context, it should not be a management cockpit showing every operational lever. It should be a disciplined board-level view of what matters most.
That may include financial performance, customer indicators, people and culture metrics, cyber and technology resilience, safety, compliance, sustainability, transformation delivery and material risk indicators. It may appear as a page in the board pack, a committee report, a portal view, a business intelligence report or a near-real-time dashboard in a secure platform. The form is less important than the discipline behind it.
The better examples are question-led. They do not start with “what data can we show?”. They start with questions such as: Are we executing our strategy? Are we operating within risk appetite? What has changed since the last meeting? What is outside tolerance? What decisions or interventions are required?
Why dashboards help boards
Dashboards are useful because boards operate under constraints. Directors receive large amounts of information, often across many businesses, jurisdictions, systems and committees. A well-designed dashboard can bring recurring information into a consistent structure, allow comparisons across time, show performance against plan or tolerance, highlight exceptions and prompt better questions.
They can also reduce unnecessary prose. A trend line may show a pattern more clearly than a paragraph. A concise table may allow directors to compare business units more efficiently than a narrative summary. A clear exception report may prevent material issues being buried in a long operational update.
However, a dashboard is not analysis. It is not assurance. It is not a substitute for management explanation. It should show the “what”, but the board paper must still explain the “why”, “so what” and “now what”.
The problem: dashboard fatigue
The expression “death by dashboard” captures a familiar boardroom problem. More metrics can create less insight. Directors may be given dozens of charts, tables, traffic lights, gauges and RAG ratings, but no clear account of what has changed, what matters, what is reliable and what requires board attention.
ASIC’s work on oversight of non-financial risk is a useful warning. ASIC identified dense and voluminous board packs, immature or ineffective risk metrics, excessive reliance on lag indicators and information that did not always give directors the right line of sight over material non-financial risks.[2] That is not an argument against dashboards. It is an argument against poorly curated reporting.
Common failure modes include vanity metrics, unexplained green traffic lights, inconsistent definitions across business units, missing baselines, arbitrary thresholds, untested assumptions, charts without narrative, buried red flags and commentary that reports activity rather than outcomes. In the worst cases, directors are left to infer the meaning themselves, or the board is pushed into operational problem-solving because the reporting has not done the work of synthesis.
What good looks like
There is no universal optimal number of dashboard metrics. A complex APRA-regulated financial institution, a listed industrial company, a health insurer and a technology start-up will not need the same dashboard. The better approach is to use a hierarchy.
Level 1: a primary board dashboard showing the small number of indicators most connected to strategy, risk appetite, financial resilience, compliance and stakeholder outcomes.
Level 2: committee dashboards for audit, risk, people, technology, sustainability or project oversight, with more specialised indicators.
Level 3: management dashboards for operational control, which should not be pushed into the board pack unless they reveal a board-level risk, exception or decision.
Each board-level metric should have an owner, a clear definition, a data source, a reporting frequency, a target or tolerance range, a prior-period comparator, a trend, a confidence level where relevant, and commentary explaining causes and actions. If management cannot explain the definition, source and meaning of a metric, it probably does not belong in the board dashboard.
The mix of indicators also matters. Boards need financial and non-financial indicators, lead and lag indicators, internal and external indicators, and measures of both performance and control. APRA-regulated entities have additional expectations around management information systems, risk appetite, tolerance levels, operational resilience and clear reporting to boards.[3] For other entities, those principles remain useful by analogy: reporting should be proportionate, timely and decision-useful.
Choosing the right visual
A good dashboard uses visualisation sparingly. Line charts are usually better for trends over time. Bar charts work well for comparison. Tables and matrices remain appropriate where directors need exact values or a structured comparison. Scatter plots can show relationships between variables. Waterfall charts can explain movement between two positions. Traffic lights can be useful for exceptions, but only if the thresholds are clear and the colours are not doing all the work.
Gauges and dials should be used carefully. They can be attractive, but often consume too much space for a single number and may imply precision that does not exist. Pie charts are often overused and can become misleading where there are too many segments or small differences. Heat maps can be useful for risk reporting, but they should not disguise weak data quality or unresolved judgement.
Accessibility should also be part of governance quality. Dashboard design should not rely on colour alone to convey meaning. Labels, icons, patterns and text should support colour-coded information so that the report remains readable for people with colour vision deficiency and for anyone viewing the report in poor display conditions.[4]
Static, interactive or real-time?
The next debate is whether board dashboards should become more live, interactive and predictive. In some areas, near-real-time information is valuable. Cyber incidents, liquidity, safety events, service outages, customer harm, regulatory breach reporting and critical operations may require faster escalation than the normal board cycle.
That does not mean directors should be expected to monitor live dashboards as if they were management. Board reporting still requires a reliable point-in-time record, adequate reading time, version control, management commentary and a clear line between oversight and execution. Live data may be useful as an update at the meeting, or as an exception alert between meetings, but it should not become an unmanaged stream of uncurated information.
Real-time access can also create new risks. Directors may see different numbers at different times. The board record may not show which version informed a decision. Data may be unaudited, incomplete or later corrected. Directors may be tempted into operational interrogation rather than governance oversight. The answer is not to reject live data, but to govern its use: define when it is used, who explains it, how it is captured in the record, and what assurance applies.
AI and the dashboard’s next life
AI is unlikely to kill dashboards. It is more likely to change what dashboards do. Modern business intelligence and board management tools are increasingly capable of summarising trends, detecting anomalies, generating narrative explanations, supporting natural language queries, producing visualisations and helping users explore underlying data.[5]
Those capabilities are useful, but they must be treated as aids to judgement, not replacements for it. AI-generated commentary can be wrong, incomplete or overconfident. It may draw from poorly defined data, miss context, expose confidential information, or produce a plausible explanation that has not been verified. Australia’s voluntary AI safety guidance places proper emphasis on governance, risk management, data governance, testing and monitoring, human oversight, transparency and records.[6] Those principles are directly relevant to AI-assisted board reporting.
For boards, the better use of AI is not “ask the dashboard anything and trust the answer”. It is using approved and secure tools to help management identify anomalies, test consistency, draft first-pass summaries, compare current results with prior periods, generate questions for review, and flag matters requiring human explanation. Company secretaries and executives should remain responsible for the final board paper. Directors should remain responsible for reading, testing and applying judgement.
Will legal expectations move?
It would be too strong to say that Australian law presently requires directors to use sophisticated dashboards, live data or AI. The better position is that legal and regulatory expectations focus on the substance of governance: directors must take a diligent and intelligent interest in the company’s affairs, read and understand material information, make further inquiries where required, and ensure appropriate systems and processes exist to support reporting and oversight.[7]
Over time, however, available technology may influence what is considered reasonable in particular circumstances. A board overseeing a complex, regulated or technology-dependent enterprise may find it harder to justify persistent reliance on slow, inconsistent or manual reporting if better and proportionate systems are available. The point is not technology for its own sake. The point is whether the board has designed information flows that are fit for the organisation’s risks, strategy and obligations.
The dashboard test
A practical test for any board dashboard is this: after reading it, can a director explain what is on track, what is off track, what has changed, why it matters, what management is doing, what assurance exists and what the board is being asked to decide or monitor? If not, the dashboard has failed.
Boards and company secretaries can improve dashboard reporting by asking management to apply seven disciplines:
Purpose: link every dashboard to strategy, risk appetite, compliance obligations or a board decision.
Curation: include what matters, not everything available.
Definitions: standardise data definitions, sources and ownership.
Context: show trends, comparators, thresholds, tolerances and assumptions.
Narrative: explain causes, consequences, actions and decisions required.
Accessibility: use visuals that can be read quickly and do not rely on colour alone.
Governance: maintain version control, assurance, confidentiality, audit trails and records.
Conclusion
The future is not “death to dashboards”. It is death to lazy dashboards.
Boards do not need more charts. They need sharper information. They need reporting that respects directors’ time without oversimplifying the issues. They need dashboards that reveal exceptions, illuminate trends, test risk appetite, connect to strategy and prompt better questions. And they need narrative and judgement around the numbers.
Dashboards are not dead. But dashboards that bury judgement under a sea of graphs should be.
Governance in Action Pty Ltd can assist clients with board reporting, including the design and application of dashboards.
David Cantrick-Brooks FGIA FCG, Principal & Director of Governance in Action Pty Ltd, would be pleased to assist with enquiries. Please feel free to reach out via LinkedIn or via gia.net.au.
AI-assisted tools and techniques were used here to support the research, drafting and editing of this publication. Responsibility for the final content rests with David Cantrick-Brooks.
Whilst accounting and legal terms and references may be contained in this publication, it does not constitute or purport to be or represent accounting or legal advice of any kind – whatsoever. Readers should seek their own professional advice.
Source notes and references
[1] ASX Corporate Governance Council, Corporate Governance Principles and Recommendations, 4th edition, especially Recommendation 1.1 and the discussion of board information, management reporting and challenge.
[2] ASIC, Director and officer oversight of non-financial risk report and related ASIC speech on non-financial risk oversight, including comments on dense board packs, lag indicators and inadequate metrics.
[3] APRA CPS 220 Risk Management and APRA CPS 230 Operational Risk Management, especially board accountability, risk appetite, management information systems, monitoring and escalation requirements.
[4] W3C, Web Content Accessibility Guidelines, Success Criterion 1.4.1: Use of Color.
[5] Public vendor and platform materials reviewed from Microsoft Power BI, Domo, Diligent and Board Intelligence. These sources were used to identify market capabilities, not to endorse any product.
[6] Australian Government, Voluntary AI Safety Standard / Guidance for AI Adoption, including guardrails on governance, data governance, testing, monitoring, human oversight, transparency and records.
[7] ASIC INFO 183, Directors and financial reporting, and general Australian governance materials concerning directors’ duty of care, active inquiry, delegation and understanding of company affairs.
[8] ASIC media release concerning ASIC v Star Entertainment Group executives and AICD commentary on governance takeaways. This draft does not assert that Star non-executive directors were found liable.
