The Dashboard Nobody Opens
Most executive dashboards fail. Not because they are poorly designed or technically deficient, but because nobody opens them. I have seen this pattern repeat across every organization I have worked with — a well-intentioned PMO team builds a comprehensive dashboard with twenty metrics, drill-down charts, and real-time data feeds, sends the link to the executive team, and then watches as the dashboard's access logs show zero visits after the first week.
The problem is not the dashboard. The problem is a mismatch between what the PMO thinks executives need and what executives actually need. The PMO wants to show everything — every metric, every trend, every detail. The executive wants to know one thing: is the programme on track, and if not, what is being done about it?
Start with the Question
The most effective dashboards I have built started not with data but with a question. I sat down with the executive sponsor and asked: what is the one question that, if you could answer it every morning, would make your job easier? The answer was always some variation of 'are we on track, and what needs my attention today?'
That question defines the dashboard. The top of the dashboard answers 'are we on track' with a simple traffic-light status: green, amber, or red. Below that, a short list of items that need attention — sites that are red, budgets that are trending over, schedules that are slipping. Everything else is available on drill-down, but the top level is clean, fast, and actionable.
The Five Metrics That Matter
Through years of trial and error, I have narrowed the executive dashboard to five metrics that cover 90% of what an executive needs to know about a programme's health.
The first is schedule performance — SPI or a simple percentage of milestones achieved on time. This tells the executive whether the programme is moving at the right pace. The second is cost performance — CPI or budget variance. This tells them whether the money is being spent efficiently. The third is scope changes — the number and value of approved change orders. This tells them whether the programme is stable or growing. The fourth is risk exposure — the total value of open risks weighted by probability. This tells them what might go wrong. The fifth is resource utilization — are the key resources fully deployed, under-utilized, or over-stretched.
These five metrics, presented as trends over time with a target line for each, give the executive a complete picture of programme health in a single screen. Anything beyond these five is detail that belongs in a drill-down, not on the executive view.
The Weekly Rhythm
A dashboard that is always available is a dashboard that is rarely checked. The most effective approach I have found is to pair the dashboard with a weekly rhythm — a short email that goes out every Monday morning with the dashboard link and a two-sentence summary: 'Programme status: green. Two items need attention: Site 14 schedule slipping, procurement shortage for OLT cards.'
This weekly nudge creates a habit. The executive knows that every Monday, they will get a concise summary that takes ten seconds to read. If the summary says green and no items need attention, they can move on with their week. If it says amber or red, they click through to the dashboard for detail. The dashboard is not the primary communication channel — the weekly email is. The dashboard is the reference.
Trust Through Accuracy
The single fastest way to kill a dashboard's credibility is to have it show data that the executive knows is wrong. If the dashboard says the programme is 60% complete but the executive has just heard from a site visit that phase two has barely started, the dashboard is dead — not just for that day, but permanently. Executives have long memories for data that contradicts their own observations.
The defense is a data validation step before each weekly update. Before the email goes out, the PMO team reviews the dashboard data against qualitative input — site visit notes, contractor feedback, recent issue logs. If the data and the qualitative input disagree, the disagreement is investigated before the dashboard is published. Sometimes the data is right and the qualitative input is wrong. Sometimes it is the other way around. Either way, the dashboard that reaches the executive has been validated, not just compiled.
The Dashboard Is Not the Report
One of the most common mistakes I see is treating the dashboard as a replacement for the monthly project report. It is not. The dashboard is a monitoring tool — it shows trends, status, and alerts. The monthly report is an analysis tool — it explains why the trends are what they are, what actions were taken, and what is planned for the next period.
The dashboard answers 'what is happening?' The report answers 'why is it happening and what are we doing about it?' Both are needed. Neither replaces the other. Executives who try to replace the monthly report with a dashboard end up with executives who have numbers but no context. Executives who try to replace the dashboard with a report end up with executives who have context but no timely alerts.
Building It: Technology Choices
The technology platform for the dashboard matters less than the design principles. I have built effective dashboards in Excel, in Power BI, in Tableau, and in custom web applications. The best platform is the one that the PMO team can maintain without external help and that the executive team can access without friction.
In practice, this often means starting simple — a well-structured Excel dashboard with conditional formatting and a few charts — and graduating to a more sophisticated platform only when the Excel version's limitations become a genuine constraint. The worst dashboards I have seen were built on expensive platforms that the PMO team could not maintain, so the data went stale and the dashboard became a liability rather than an asset.
The Ultimate Test
The ultimate test of an executive dashboard is simple: does the executive open it without being prompted? If the answer is yes, the dashboard has earned its place. If the answer is no, no amount of technical sophistication will make it useful. The way to pass this test is to build for the executive's needs, not the PMO's needs — to start with the question, not the data, and to earn trust through accuracy, brevity, and consistency.
