Dashboard Design Best Practices: BANs, KPI Cards, and the One-Page Rule

Good dashboard design isn't a matter of taste. Executives scan a dashboard the same way every time — top left first, big numbers before charts, one screen and no further. Design for that scan pattern and the dashboard gets used. Fight it and the dashboard gets a polite nod in one meeting and then silence.

These are the practices that hold up across Tableau and Power BI, drawn from what analytics teams converge on after enough stakeholder reviews.

Start with the questions, not the charts

Every dashboard answers a short list of questions. Write them down before touching a tool: Are we hitting the revenue target? Which region is behind? Is the trend improving?

Each question maps to a visual. A question with no visual is a gap; a visual with no question is decoration. Most dashboard bloat is decoration that survived because deleting things feels risky.

If you can't get the question list from stakeholders, prototype it. A working draft in front of them — not a requirements document — is the fastest way to find out what they actually look at.

The top row belongs to BANs

BANs — big-ass numbers, politely "big aggregate numbers" — are the KPI cards across the top of the dashboard. They exist because the first thing any reader wants is the headline: what's the number, and is it good or bad?

Four to six BANs is the working range. Fewer and the top row looks unfinished; more and the numbers compete with each other until none of them registers.

What makes a good KPI card

• One number, prominently sized. The value is the largest element on the card, no contest.
• A plain-English label. "Total Sales," not the measure's internal name. If the label needs a footnote, the KPI needs a rethink.
• Context. A comparison to target, prior period, or same period last year — as a delta, a percentage, or a small sparkline. A number without a reference point is trivia.
• Consistent formatting. Same decimal places, same currency treatment, same abbreviation rules ($1.2M, not $1,204,317) across all cards.

The order of the cards is an editorial decision. Lead with the KPI the meeting is actually about.

The one-page rule

Executive dashboards don't scroll. If a reader has to scroll to see whether the quarter is on track, the layout has already failed — the content below the fold effectively doesn't exist.

One page forces prioritization, and prioritization is the actual design work. The practical budget for a one-page executive dashboard:

• 4–6 KPI cards in the top row
• 2–3 charts in the body
• 2–3 slicers, grouped together

Detail lives elsewhere: a drill-down page, a linked report, an export. The one-pager's job is to tell the reader whether anything needs attention. It is a scorecard, not an encyclopedia.

Visual hierarchy: position and size do the work

Readers assign importance by position and size before they read a single label. Use that:

• Top left is the most valuable slot. Put the most important KPI or the primary trend there.
• Trend before breakdown. The time-series chart ("how are we doing?") sits above or left of the categorical breakdown ("where is it coming from?"), because that's the order the question gets asked.
• Size proportional to importance. The primary chart should be visibly larger than supporting ones. Four identical quadrants tell the reader nothing about where to look first.
• Align to a grid. Misaligned edges read as sloppy even when nobody can articulate why. Consistent gutters and card heights are the cheapest polish available.

Slicers: fewer, and in one place

Slicers are the dashboard's steering wheel, and they belong in one predictable location — the left rail or a row under the KPI cards, not scattered between charts.

Two or three is the right count for an executive view: almost always a date range, plus one or two dimensions like region or product category. Every additional slicer adds a question the reader must answer before trusting the numbers ("wait, what's this filtered to?"). Default every slicer to the state the meeting cares about, so the dashboard is correct at first glance with zero clicks.

Restraint in color and formatting

Color is a signal channel. Spend it on meaning, not branding:

• One accent color for emphasis; neutrals for everything else.
• Red and green reserved strictly for bad and good — never as category colors, or the semantics collapse.
• Conditional formatting on the few cells or cards where a threshold genuinely matters, not as wallpaper.

The same restraint applies to effects: no drop shadows, no 3-D, no gauge charts eating a quarter of the page to convey one number a BAN shows in a tenth of the space.

Practice beats theory

None of this sticks from reading — it sticks from shipping a layout, watching a stakeholder squint, and adjusting. The fastest loop is to prototype the layout with sample data before any production plumbing exists.

That's the workflow LiteKPI is built around: upload a CSV, lay out KPI cards, charts, and slicers on a one-page canvas that follows these defaults, and preview the live dashboard immediately. When the design is right, download it as a native file — a .twb or .twbx from the Tableau builder, or a ready-to-open .pbit template from the Power BI builder — and finish it in Desktop. Download access starts at $5/month on the pricing page.

Layout is a solved problem. The craft is in choosing the right four numbers for the top row.

Sketch your next dashboard against these rules — start in the Tableau or Power BI builder.