Sales Dashboard Design
Sales Dashboard
What is a sales dashboard?
- Three layers (outcomes, pipeline, activity), no more than 10 metrics
- Fix data-entry rules before building the screen
- Before-and-after activity metrics are your evidence for reporting training impact
When a sales dashboard is set up properly, the first 30 minutes of the weekly sales meeting disappear. The 'reconciling this week's numbers' that ate most of the meeting goes away, and the meeting becomes a place to ask why a metric on screen is red. Everyone seeing the same numbers at the same moment is the essence of a dashboard, which is why it differs from a report that sales operations builds in Excel on Friday night and sends out Monday morning. No one spends time arguing over where a number came from, and any activity not entered in the CRM is treated as if it never happened, so a dashboard is also a way to enforce data-entry discipline.
Stack it in three layers. The top layer is results: won deal value, revenue, quota attainment, and new customer count. The middle layer is pipeline: value and count by stage, coverage multiple against quota, stage conversion rates, and average sales cycle. The bottom layer is activity: meetings, proposals, demos, and lead response time. Each audience looks at a different layer: executives see a single results page, managers see pipeline by team, and reps see their own activity and deal list. The design principle is no more than 10 metrics per screen, with a definition sheet and threshold for each metric. If you don’t write down color rules such as “red if attainment is below 80%,” people read the colors differently. Keep CRM as the single data source; once Excel side files creep in, you are back to meetings arguing over which number is right. Refresh cycles are usually daily for results and real time for activity.
For training managers, a dashboard is a window onto training impact. Whether discovery-meeting counts rose after a questioning techniques course, or discount rates fell after a negotiation course, shows up directly in the activity and outcome layers. Simply comparing activity metrics for the four weeks before and after training makes a more persuasive report than a satisfaction survey. When planning next year at year-end, the dashboard also becomes input for choosing who to train: teams whose pipeline coverage is below 3x quota become the top candidates for new-prospecting training.
The most common failure in practice is metric overload. Nobody looks at a dashboard with 40 metrics, and sales operations ends up picking five of them and rebuilding them in Excel. Building the dashboard before CRM entry is under control is another common failure: a dashboard on top of an empty CRM just makes wrong numbers look good. The moment it becomes a surveillance tool, entries get manipulated, and logged meetings go up while real meetings go down. Meetings that only look at the colors and never ask why, and 'automatic' dashboards that someone updates by hand every Friday night, also collapse within a year. Go in knowing that maintaining metric definitions is harder than building the dashboard.
John KimAuthor of B2B Marketing Design and CEO of Nanum Consulting
Jaehyuk ParkHands-on instructor in B2B technical sales and AI-driven sales strategyThe business-dashboard idea of gathering management information on one screen like a car's instrument panel took hold with the spread of BI tools. As CRM became the system of record for sales activity, sales-specific status boards became commonplace. The three-layer structure of outcomes, pipeline, and activity is a convention that emerged from sales operations practice.
Consider a hypothetical case. Company A sells factory-automation parts, with 22 salespeople and annual revenue of KRW 36 billion (≈ US$26,934,000). Of its 90-minute Monday sales meeting, 40 minutes went to reconciling each team's Excel numbers, and a sales operations associate updated the Excel file they called the 'dashboard' every Friday until 10 p.m.
- When the head of sales ordered a BI tool, the sales operations manager pushed back: 'Our CRM required-field completion rate is 50%. If we build the screen first, we just make wrong numbers look pretty.' They argued for fixing the entry rules first.
- Over one month, the team standardized stage definitions and made customer attendee names mandatory in meeting records, raising the completion rate from 50% to 85%. Only then did they narrow the metrics to 4 outcome, 4 pipeline, and 3 activity metrics and write the definition sheet.
- The executive view is a single page, the team lead view shows coverage and conversion by team, and the rep view is a list of their own deals. The color rules are written at the bottom of each screen, such as “red if coverage is below 3x.”
- A training team manager pulled the discovery-meeting counts for the four weeks before and after a questioning-techniques course straight from the screen and reported, 'Meetings after training rose from 31 to 47 per week.' That secured the budget for the next course.
- Six months later, the Monday meeting had shrunk from 90 to 50 minutes, time spent reconciling numbers fell to zero, and the Friday-night Excel work was gone. Two teams with coverage below 3x became the top priority for new-prospecting training in next year's plan.