Sales Dashboard Layout: How to Arrange Metrics So People Act on Them

What Belongs Above the Fold on a Sales Dashboard?

One accountable number, its target, and the gap between them in dollars. Every dashboard has an owner, and that owner is measured on one figure. For a CRO it is closed-won revenue against the quarterly plan. For a VP of Marketing it is sourced pipeline against the pipeline target. Put that number at the top left in the largest type on the page, with the target immediately beside it and the variance stated in currency rather than a percentage.

The reason is arithmetic. A leader who sees "82% of plan" has to do mental math before knowing whether to act. A leader who sees "$1.4M short of plan with five weeks left" already knows the size of the problem. State the gap in the same unit the recovery plan will use.

Directly under the headline number, place the trend of that number over the last six to eight periods. The current value tells you where you are. The trend tells you whether the situation is improving on its own or getting worse while you watch.

How Many Metrics Should Fit on One Screen?

Five to seven visual elements, and no more. Past seven, viewers switch from reading to scanning, and scanning produces recognition rather than decisions. The constraint feels severe until you apply it, at which point most dashboards lose four charts nobody had ever cited in a meeting.

The test for each element is whether a specific person changes a specific action based on what it shows. A pipeline coverage gauge passes if a low reading triggers a pipeline generation push. A chart of total activities logged this week usually fails, because no plausible reading changes anyone's next move.

Density matters as much as count. A single table with fourteen columns is heavier than three clean charts. If a table needs horizontal scrolling to read, it belongs on a drill-down page with the top-level view showing only the two columns that drive the decision.

What Order Should the Metrics Follow?

Outcome first, then the driver of that outcome, then the driver of the driver. A dashboard is an argument, and the reader should be able to follow it downward without jumping around the page. The sequence answers a predictable chain of questions. Are we going to hit the number, and what is producing that result. Exceptions sit at the bottom because they are a work queue, not a status report. Readers arrive at them after they understand the context, which is when a list of twelve slipped deals is useful rather than alarming.

Where Do Targets and Comparisons Belong?

Inside the same visual element as the metric, never in a separate legend or a note underneath. A number without a reference point is decoration. Every metric on the page needs a comparison baked into its display: the target, the prior period, or the same period last year.

Use a reference line on time-series charts rather than a second series. A horizontal target line reads instantly, while a second plotted line forces the eye to trace two shapes and compute the distance between them.

For metrics that lack a plan target, use the prior four-period average as the baseline. This applies to win rate, average deal size, and sales cycle length, which rarely carry a formal quarterly goal but still need context. Composition risk is easy to miss without one. Deals routinely close for less than the amount recorded in the CRM. A pipeline carrying an $80,000 average open deal size can produce a closed-won average nearer $40,000, and only a side-by-side comparison surfaces that gap before the quarter ends.

How Should the Layout Handle Segment Breakdowns?

Break down along one dimension per row, and pick the dimension that owns the remediation. Segment, territory, product, and source all deserve analysis, but stacking four breakdowns on one screen produces a page nobody reads to the end.

Choose based on who fixes the problem. If enterprise and mid-market run separate playbooks with separate leaders, segment is the primary cut because it maps to an owner who can act. If your product lines share a sales team, product is a reporting curiosity rather than an operating lever, and it belongs on a drill-down.

Aggregate coverage hides most of what matters here. Coverage of 3.5x at the company level can conceal segments well above and well below it. Across ORM customers, whole-company coverage runs from 1.4x to 5x, with most near 3.5x, and the same spread hides inside a blended company number. Show coverage by the dimension that has an owner, or the number reassures without informing. The argument against treating a single blended ratio as the answer is covered in why the 3x pipeline coverage rule is wrong.

What Layout Mistakes Send People Back to Spreadsheets?

Burying the number people came for, and answering questions nobody asked while missing the obvious follow-up. Both push viewers into Excel, and once a leadership team exports, the dashboard stops being the source of truth.

The specific failures repeat across companies:

- Rep-level tables placed on the executive view, forcing leaders to scroll past 40 names to reach a trend line - Filters set to a default nobody uses, so every session begins with three clicks of setup - Charts sized by available space rather than importance, giving a minor metric the same visual weight as revenue - Multiple date ranges on one screen, where one chart shows quarter to date and the next shows trailing twelve months without labeling either - Percentage-only displays that hide the denominator, so a win rate move from 22% to 26% looks meaningful when it reflects four extra deals

The date-range problem is the most damaging because it produces confident wrong conclusions. Label the period inside every chart title, not in a global header that scrolls out of view.

How Do You Know the Layout Is Working?

Count how often a meeting that opens the dashboard also opens a spreadsheet. That single behavior is the honest measure of layout quality. An export means someone had a question the page did not anticipate, and the fix is structural rather than cosmetic.

Run this for one month. Write down every follow-up question asked in forecast calls and pipeline reviews that the dashboard could not answer on screen. Rank them by frequency. The top three become new elements, and three existing elements that never got referenced come off to make room.

The second test is time to first insight. Hand the dashboard to someone who has never seen it and ask whether the business is on track. If the answer takes longer than ten seconds, the headline zone is doing its job badly. Layout work is finished when a stranger reaches the right conclusion without a tour, and when your own team reaches for the page instead of the export button. For definitions behind the driver metrics in the second row, see forecast accuracy and win rate.