Power BI Dashboard Design: 12 Best Practices That Hold Up (2026)

Before you place a visual, write the page's question in one sentence: "Are we on track for quarterly revenue, and which region is behind?" Then name who reads it. A CFO, a regional manager and an analyst want different levels of detail from the same data.

Microsoft's dashboard guidance puts it as considering your audience: how they use the page, which metrics drive their decisions, and what they need to be successful. If a visual doesn't help answer the page's question for that audience, it belongs on a detail page, a drillthrough or a tooltip, not on the overview.

A good test: cover the page title and ask a colleague what the page is for. If they can't say, the page is doing two jobs.

Readers in left-to-right languages scan from the top-left corner. Learn's guidance is direct: put the highest level of data at the top left and add detail as you move right and down.

In practice that gives a reliable three-band layout on a 1280 × 720 canvas: a slim header (title, period, a few slicers) across the top at about 56-72 px high; a row of 3-5 KPI cards beneath it; and the analysis area filling the rest, with the main trend chart on the left and breakdowns on the right.

Make the headline numbers physically bigger than everything else. When every element is the same size, nothing stands out. Card visuals exist for exactly this: one number, large, with a label and context such as a target or a prior-period comparison.

Misaligned visuals are the most visible sign of an unfinished report. Fix it with a grid you decide in advance, not by eye.

On a 1280 × 720 page, a 24 px outer margin and 16 px gutters work well. With an 8 px grid every edge lands on a multiple of 8, and the arithmetic stays simple: four KPI cards across 1232 px of usable width with three 16 px gutters are 296 px each.

Power BI helps: View > Show gridlines and Snap to grid, and the Properties card under Format visual > General lets you type X, Y, width and height exactly. Select several visuals and use Align and Distribute to even them out. Lock objects (View > Lock objects) once the layout is final so nobody nudges a chart by a pixel.

Designing the layout first, as an image or a page design, then placing visuals onto it, is faster than dragging visuals until they look right.

There's no hard limit, but every visual on a page sends its own queries, and Microsoft's accessibility guidance warns that too many visuals overwhelm readers and slow the report. For an overview page, 6-10 visuals is a healthy range: 3-5 cards, one main chart, two or three supporting charts, and maybe one table.

Remove duplicates. Two visuals that show the same thing differently aren't extra insight; they're extra reading. Move the detail table to a drillthrough page and give the overview its space back.

Use tooltip pages for secondary context. A report tooltip page, sized with the Tooltip page type (320 × 240), shows a small breakdown on hover without taking space on the canvas. Keep anything critical off tooltips though: they aren't interactive, and screen readers can't read report tooltip content.

Learn's own advice: avoid variety for the sake of variety, avoid 3D charts, and prefer bar and column charts for comparing values, because people compare lengths side by side far better than angles or areas.

Use a line chart for change over time, a bar chart for ranking categories (horizontal bars fit long labels), a column chart for a few periods, a stacked bar or 100% bar for composition across categories, and a scatter chart for relationships between two measures.

Pie and donut charts are fine for part-to-whole with few categories; Microsoft suggests fewer than eight. Gauges show a single value against a goal, but a card with a target or a bullet-style bar uses the space better.

When a native visual can't show the comparison you need (a Sankey for flows, a Gantt for schedules, a waterfall with custom grouping), a custom visual is the right tool. That's what VizForge generates from a plain-English description.

Learn recommends showing no more than three or four numerals and scaling large values to thousands or millions: "3.4M" reads faster than "3,400,000". Set display units on cards and axes, and use format strings so decimals are consistent across the page.

Remove data labels that repeat the axis. A bar chart with gridlines doesn't usually need a label on every bar; label only the bars that matter, or use labels and drop the axis.

Don't mix scales on one axis. A measure in millions next to one in thousands flattens the smaller one into a line along the bottom. Use a second axis, a separate chart, or an index.

Sort deliberately: by value when you want the biggest or smallest to stand out, by the category axis when people need to find a specific item quickly.

Don't put "last month" next to a chart filtered to a different month. Microsoft calls this mixing levels of precision and time, and it's one of the fastest ways to lose a reader's trust.

Show the period in the header ("Oct 2026, month to date") and drive every visual from the same date slicer or relative date filter. If a visual deliberately shows a different period, such as a 13-month trend next to month-to-date cards, say so in its title.

Use one report theme for every page. It sets the series colours in a fixed order, structural colours for text and gridlines, and default fonts, so new visuals match automatically. Picking theme colours rather than custom hex values in the format pane means a later theme change updates every visual.

Reserve strong colour for meaning. A neutral grey for "everything else" plus one accent for the series you want people to look at beats eight equally loud colours. Status colours (the theme's good, neutral and bad) should mean the same thing on every page.

Don't rely on colour alone. Learn's accessibility checklist asks you to supplement colour with text or icons, and lists pairs to avoid together, including green and red, green and brown, and blue and purple.

Text needs a contrast ratio of at least 4.5:1 against its background, which is WCAG 2.1 criterion 1.4.3 and the first item on Microsoft's report accessibility checklist. Grey axis labels on a dark blue panel fail this more often than anything else. Check your text colours against the panel colour they sit on, not the page colour.

Add alt text to every visual that carries meaning (Format > General > Alt text, up to 250 characters) and set the tab order in the Selection pane so keyboard users move through the page in reading order. Hide decorative shapes and images from the tab order.

A designed background helps here: it keeps decoration in one image that screen readers skip, while titles and numbers stay as real, readable text.

Panels, header bars, separators and subtle shadows can all live in one page background image instead of dozens of shapes. That keeps the Selection pane clean, avoids accidentally selecting a rectangle instead of a chart, and keeps layout identical across pages.

Export the background at the exact canvas size (1280 × 720, or 2560 × 1440 for sharpness), set it with Image fit Fill and Transparency 0%, and turn off the visuals' own backgrounds so the panels show through. The background image guide on this blog has the exact steps.

Slicers should sit in the same place on every page; Microsoft's accessibility guidance asks for consistent font, colour and position. A header row is the natural home.

Buttons for page navigation and Clear all slicers should look like buttons: a fill, a clear label, and a hover state. Power BI buttons support separate formatting for Default, On hover, On press and Disabled.

If a key conclusion only appears after a click, change the default state so it's visible on load. Test the page with only a keyboard at least once.

Power BI's Fit to page view hides problems. Switch to View > Actual size to see your page pixel for pixel, then publish and open it in the browser on a laptop, a large monitor and, if the audience uses phones, the mobile app with a mobile layout.

Do a squint test: if your eye goes to data labels or decoration before the headline numbers, turn something down. Learn suggests the same test for busy visuals.

Then lock objects, save, and keep the layout as a template. The second report built on a tested layout takes a fraction of the time.

The VizForge Design Studio applies most of these rules for you: a 1280 × 720 canvas with an 8 px grid and snapping, a quick-start wizard that generates header, KPI and chart layouts with even gutters, brand kits that check text contrast, and exports for the background PNG, the theme JSON and a PBIP project with the visual containers already positioned.

Browse the template gallery for department layouts, or read the 20 dashboard examples post for the layout patterns behind them.