Buyer guide

Executive dashboards that actually get used

Executive dashboards get used when each number answers a real decision, has one agreed definition and owner, and matches finance. Build fewer measures, reconcile them, and make the dashboard the centre of a regular meeting.

The short answer

Most executive dashboards fail from too many charts, numbers that disagree with finance, and no meeting that uses them. One gets used when:

  • every measure connects to a decision a leader makes,
  • each has one written definition and one owner,
  • figures reconcile to the ledger or system of record,
  • it shows what changed and needs attention, not just totals,
  • it anchors a regular review with actions recorded.

Start with five to nine measures; add more once they are trusted.

Why dashboards get ignored
  • No decision behind it: it shows what was easy to extract, not what leaders need.
  • Numbers disagree: sales says revenue is one figure, finance another; after one argument, nobody trusts either.
  • Stale data: it last refreshed on 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 it, it becomes a link in a bookmark folder.

Start from decisions, not data

Work backwards with each leader: decision, question, measure, source.

DecisionQuestionMeasureSource
Do we hire another technician?Are we keeping up with demand?Open work orders older than 5 days, trend by weekERP or service system
Do we chase a customer segment harder?Where is margin coming from?Gross margin by customer group, this quarter vs lastERP 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 weeksAccounting

These rows illustrate the method; they are not recommended measures for your organization.

A measure that changes no decision stays off the executive view; it may belong in a team report.

Write a definition card for every measure

Arguments about numbers are usually about definitions. Settle each in writing:

  • Definition
  • Includes
  • Excludes
  • Source
  • Refresh and timestamp
  • Owner
  • Reconciles to
  • Target and threshold
Example definition card
Demonstration, not a client project

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 page answers: are we on track, what changed, what needs attention?

  1. Top rowHeadline measures against target, prior period or last year.
  2. MiddleTrends, so leaders see direction, not a snapshot.
  3. BottomExceptions (overdue invoices, low stock, projects over budget) linked to detail.

A number without a comparison is hard to act on. Red and green are hard for many people to tell apart, and WCAG 2.2 says colour should not be the only way information is conveyed (W3C): add labels or icons. A visible "data as of" timestamp prevents decisions on stale figures.

Make the data trustworthy

The build is the easy part; trust takes discipline.

  • Reconcile before launch: each financial measure against posted accounts for two or three past periods; explain or fix every difference.
  • Pick the right layer: ERP dashboards for daily monitoring (ERPNext points to Frappe Insights for custom or cross-module charts); Power BI or eventually a data warehouse when data spans systems.
  • Control who sees what: executive views hold payroll, margin or customer data. In Power BI, row-level security applies only to users with the Viewer role, not to workspace Admins, Members or Contributors (Microsoft Learn), which 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 first thing in the weekly or monthly leadership meeting, review exceptions first, record who does what. After a quarter, drop measures nobody discussed; add questions that kept coming up.

When to bring in help

One system with decent reporting and someone with time to learn it? Start there: many get a useful first dashboard from their ERP or accounting package. Help pays off when systems disagree, definitions are contested, sensitive data needs access control, or two attempts went unopened. An AI assistant can suggest KPIs in seconds; it cannot spot that your ERP posts freight to the wrong account, or reconcile last quarter with your controller.

  • Decision workshops
  • Definitions
  • Data preparation
  • Reconciliation
  • Build
  • Access testing
  • Handover

Our data analytics and business intelligence service covers that full path, plus the ERPNext side when it is your system of record, so data is right at the source.

Launch checklist

  • Each measure links to a named decision and a named owner.
  • Every measure has a definition card agreed by the leaders using 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.

  1. Dashboard, ERPNext documentation (Frappe)
  2. Frappe Insights, Frappe documentation
  3. Row-level security (RLS) with Power BI, Microsoft Learn
  4. 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.

Talk to Promatics

Get a dashboard your leadership team will actually open

Paying for reporting nobody trusts is frustrating. We work from your decisions and real data, reconcile with finance, and build what your leaders use weekly.

  • Metric definitions agreed with your leaders, in writing
  • Numbers reconciled to your finance figures before launch
  • Built on the ERP and tools you already have