We have audited a lot of dead dashboards. The pattern is consistent: a launch email, two weeks of curiosity clicks, then silence, while the exec goes back to asking the finance manager for the numbers on WhatsApp. The dashboard was accurate. It was even pretty. It just was not built around how executives actually consume information.
The dashboards that survive, some of ours now four years old and checked daily, share five habits. None of them depend on which BI tool you bought.
Why most executive dashboards die
- They answer the analyst’s questions, not the executive’s. Forty filters is a workbench, not a dashboard.
- They show snapshots without context. "Revenue: R4.2m" means nothing without versus-what.
- They load slowly or need a VPN, so the WhatsApp question stays faster.
- The numbers disagree with the finance pack, once, and trust never recovers.
- Nobody owns them, so six months later half the tiles are stale.
One page, five to seven numbers
An executive dashboard is one screen with five to seven numbers, no scrolling and no tabs. If leadership cannot agree on the seven numbers that define the health of the business, that argument is the real project, and it is worth having before anyone opens a charting tool. The forcing question we use: "If you could only see five numbers from a beach in Mauritius, which five?"
Everything else, the breakdowns, the branch drill-downs, the cohort views, lives one click deeper for the people whose job is to dig. The top page is for the ten-second scan.
Every number needs a versus
A number alone is trivia. A number with a comparison is information. Every tile should carry at least one of: versus last period, versus the same period last year, or versus target. And every tile should carry a small trend line, because direction is the thing executives are actually scanning for. "R4.2m, down 6 percent on plan, third consecutive down week" is a sentence that starts a conversation. "R4.2m" starts nothing.
Reconcile with finance or die
The fastest way to kill a dashboard is one meeting where its revenue figure differs from the CFO’s pack. Before launch, sit with finance and reconcile every headline number to the cent, then document the definitions: does revenue include VAT, when does an order count, how are refunds treated. Publish those definitions behind an info icon on each tile. Trust is binary with this audience, and you only get to lose it once.
Ship it into a routine, not a URL
Dashboards get adopted when they are pushed into an existing habit, not when they wait behind a bookmark. The two mechanisms that work: a scheduled snapshot emailed at 06:30 every Monday with the top page rendered inline, and the dashboard on the boardroom screen as the first agenda item of the weekly exec meeting. Within a month the numbers become the shared language of that meeting, and the dashboard has a constituency that will defend it.
7
maximum tiles on the top page
3 sec
load time ceiling before usage drops off
06:30
Monday snapshot email that drives most repeat visits
Assign an owner and a review cadence
Every surviving dashboard has a named owner whose job includes noticing when a pipeline breaks before an executive does. Add a quarterly 30-minute review where the exec team can vote one tile off and one on. Businesses change, and a dashboard frozen at launch decays into wallpaper.
The build itself is the easy part: with a solid warehouse underneath, the executive page is two to three weeks of work. Without one, the dashboard becomes a maze of fragile direct connections, which is why we usually sequence the foundation first. If your reporting still runs on exported spreadsheets, start with our data and analytics service, or book a consultation and bring your current board pack. We will tell you which seven numbers we would put on the wall.
