The short answer
Most executive dashboards fail for the same reasons: too many charts, numbers that do not match what finance reports, and no meeting where anyone is expected to look at them. A dashboard gets used when:
- every measure connects to a decision a leader actually makes,
- each measure has one written definition and one owner,
- the figures reconcile to the general ledger or the system of record,
- it shows what changed and what needs attention, not just totals, and
- it sits at the centre of a regular review (weekly or monthly) with actions recorded.
Start with five to nine measures. You can add more once the first set is trusted.
Why dashboards get ignored
Before building anything, it helps to name the usual causes:
- Nobody asked what decisions it supports. The dashboard shows what was easy to extract, not what leaders need.
- Numbers disagree. Sales says revenue is one figure, finance says another. After one argument, nobody trusts either.
- Stale data. The dashboard refreshed last Tuesday, and nobody can tell.
- Too much at once. Forty charts on one screen means no chart gets attention.
- No rhythm. Without a standing meeting that opens the dashboard, it becomes a link in a bookmark folder.
Start from decisions, not data
Work backwards with each leader. The chain looks like this: decision, question, measure, source.
| Decision | Question | Measure | Source |
|---|---|---|---|
| Do we hire another technician? | Are we keeping up with demand? | Open work orders older than 5 days, trend by week | ERP or service system |
| Do we chase a customer segment harder? | Where is margin coming from? | Gross margin by customer group, this quarter vs last | ERP sales and cost data |
| Do we need to draw on the credit line? | Will cash cover the next 8 weeks? | Receivables due vs payables due, rolling 8 weeks | Accounting |
These rows are illustrations of the method, not recommended measures for your organisation.
If a proposed measure does not change a decision, leave it off the executive view. It may still belong in a team report.
Write a definition card for every measure
Arguments about numbers are usually arguments about definitions. Settle them once, in writing.
Measure: Gross margin by customer group
- Definition: (net sales minus cost of goods sold) divided by net sales, for invoices posted in the period.
- Includes: credit notes; freight charged to customers.
- Excludes: unposted draft invoices; intercompany sales.
- Source: posted sales invoices and stock ledger in the ERP.
- Refresh: nightly; timestamp shown on the dashboard.
- Owner: controller.
- Reconciles to: gross margin in the monthly income statement, within an agreed tolerance.
- Target and threshold: set by the leadership team; below threshold shows as "needs attention" with a text label.
Design for a five-minute read
A good executive page answers three questions in order: are we on track, what changed, and what needs attention.
- Top row: the handful of headline measures, each with a comparison (target, prior period or same period last year). A number without a comparison is hard to act on.
- Middle: trends over time for those measures, so leaders see direction rather than a single snapshot.
- Bottom: exceptions, such as overdue invoices above a threshold, stock below reorder point or projects over budget, with a link to the detail.
- Status without colour alone. Red and green are hard for many people to tell apart. WCAG 2.2 treats colour as something that should not be the only way information is conveyed (W3C), so add labels or icons.
- Show freshness. A visible "data as of" timestamp prevents decisions made on stale figures.
Make the data trustworthy
The build is usually the easy part. Trust takes discipline.
- Reconcile before launch. Compare each financial measure with the posted accounts for two or three past periods. Explain every difference or fix it.
- Pick the right layer. Many ERPs include dashboards suited to day-to-day monitoring; the ERPNext documentation describes module dashboards and points to Frappe Insights when you need custom charts or cross-module analysis (ERPNext, Frappe Insights). When data comes from several systems, a BI tool such as Power BI, or eventually a data warehouse, may be the better home.
- Control who sees what. Executive views often include payroll, margin or customer data. Test access rules properly: in Power BI, for example, row-level security applies only to users with the Viewer role, not to workspace Admins, Members or Contributors (Microsoft Learn). That detail catches many teams out.
- Monitor refreshes. A failed overnight refresh should alert someone before the Monday meeting, not during it.
Rather talk it through? If your leadership team argues about whose numbers are right, we can agree the definitions, reconcile the data and build a dashboard people rely on. Talk to a Promatics specialist
Build the habit
A dashboard earns its place when a meeting depends on it. Open it at the start of the weekly or monthly leadership meeting, review exceptions first, and record who is doing what about each one. After a quarter, remove measures nobody discussed and add the questions that kept coming up.
When to bring in help
If your data lives in one system with decent built-in reporting, and someone on your team has time to learn the tool, start there. Many organisations get a useful first dashboard from their ERP or accounting package.
Help pays off when data sits in several systems that disagree, when definitions are contested between departments, when sensitive data needs careful access control, or when your team has tried twice and the dashboard still goes unopened. An AI assistant can suggest KPIs in seconds, but it cannot see that your ERP posts freight to the wrong account or sit with your controller to reconcile last quarter. Our data analytics and business intelligence service covers the full path: decision workshops, definitions, data preparation, reconciliation, build, access testing and handover. If ERPNext is your system of record, we also work on the ERPNext side so the data is right at the source.
Launch checklist
- Each measure links to a named decision and a named owner.
- Every measure has a written definition card, agreed by the leaders who use it.
- Financial measures reconcile to posted accounts for at least two past periods.
- Each headline number has a comparison (target, prior period or last year).
- Status is shown with text or icons, not colour alone.
- A "data as of" timestamp is visible.
- Access has been tested with real user accounts in each role.
- Failed refreshes send an alert to a named person.
- The dashboard has a standing place in a leadership meeting.
- A review date is set to remove unused measures.
Sources and further reading
Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.
- Dashboard, ERPNext documentation (Frappe)
- Frappe Insights, Frappe documentation
- Row-level security (RLS) with Power BI, Microsoft Learn
- Web Content Accessibility Guidelines (WCAG) 2.2, W3C
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.