Building Revenue Dashboards People Actually Use

The Dashboard Graveyard

Every GTM team has one. A collection of dashboards built with good intentions, launched with a Slack announcement, used for two weeks, and then abandoned. Six months later, someone asks “do we have a dashboard for that?” and the answer is technically yes — but it is out of date, built on a data source that no longer exists, and answers questions nobody is asking anymore.

A survey by Databox found that 47% of dashboards in B2B organizations are viewed fewer than twice per month. Nearly a quarter are never viewed at all after the first week. That is not a visualization problem. It is a design problem.

Dashboards fail for three predictable reasons. Understanding them is the first step toward building dashboards that actually get used.

Too many metrics. The instinct when building a dashboard is to include everything that might be relevant. The result is a wall of charts that takes 20 minutes to review and leaves the viewer unsure what to focus on. A study by the Nielsen Norman Group showed that dashboard comprehension drops by 50% when more than 7 distinct metrics are displayed on a single view.

No context. A chart showing that pipeline is $3.2M this month means nothing without context. Is that good? Bad? How does it compare to last month, last quarter, the target? A number without context is just a number — it does not drive action.

Wrong audience. A dashboard designed for the CEO has different requirements than one designed for an SDR manager. When teams build one dashboard and expect it to serve everyone, it serves no one. The CEO does not need to see daily call volume. The SDR manager does not need to see board-level financial metrics. Mixing them creates noise for both.

The 3-Dashboard Framework

The solution is not one dashboard — it is three, each designed for a specific audience with specific decisions to make.

Dashboard 1: Executive

Audience: CEO, CRO, CFO, VP-level leaders Review cadence: Weekly (5-minute scan), monthly (15-minute review) Decision types: Resource allocation, strategic bets, hiring, board reporting

What belongs here:

• North star metric and trend. ARR, net new ARR, or revenue growth rate — whatever your company has chosen as its primary measure. Show the trailing 12 months as a trend line with the target overlaid.
• Pipeline coverage ratio. Total qualified pipeline divided by the remaining revenue target for the quarter. If this ratio drops below 3x, it is an early warning that the quarter is at risk.
• Funnel conversion summary. One row per funnel stage, showing volume, conversion rate, and comparison to the prior quarter. Not a detailed breakdown — just enough to spot where the funnel is healthy and where it is constrained.
• Win rate trend. Trailing 90-day win rate by segment. A declining win rate is one of the most important signals a CRO can act on.
• Revenue by source. Inbound, outbound, partner, expansion. Pie chart or stacked bar. The exec team needs to know the mix, not the details.
• One “watch” metric. Rotate this monthly. It is the metric that the ops team has identified as needing executive attention — maybe it is churn spiking in a segment, or a new channel showing unexpected traction.

What does not belong here: Daily activity metrics, individual rep performance, detailed campaign breakdowns, technical health monitors.

The executive dashboard should fit on a single screen without scrolling. If the viewer has to scroll, you have included too much. Every chart should answer the question “does leadership need to do something different?” If a chart does not trigger potential action at the leadership level, it belongs on a different dashboard.

Dashboard 2: Team Lead

Audience: Directors, managers, team leads across marketing, sales, and CS Review cadence: Daily (2-minute check), weekly (10-minute review with team) Decision types: Coaching, process adjustment, campaign optimization, resource rebalancing

What belongs here:

• Stage-by-stage pipeline movement. New opportunities created, deals advanced, deals slipped, deals lost — this week vs. trailing 4-week average. This is the most actionable view for a sales manager.
• Leading indicator panel. The 3-4 leading indicators identified in your GTM metrics framework that predict downstream outcomes. Show current values with trend arrows and red/yellow/green status.
• Team performance distribution. Not a leaderboard — a distribution chart showing where each team member falls relative to the team average for key metrics. This helps managers identify who needs coaching without creating a public shaming tool.
• Conversion rate by stage. Detailed funnel view showing conversion rates at each transition. Include week-over-week change and highlight any stage where conversion has dropped by more than 15%.
• Campaign performance (marketing leads only). Active campaign results: spend, pipeline generated, cost per opportunity, and conversion rates. Show only active campaigns with enough data to be meaningful.
• Forecast vs. actual (sales leads only). What did the team commit to last week vs. what actually closed? Track forecast accuracy over time — it is a skill that improves with practice.

What does not belong here: Board metrics, individual deal details, long-term strategic trends.

Dashboard 3: Individual Contributor

Audience: SDRs, AEs, CSMs, demand gen specialists, content marketers Review cadence: Multiple times per day Decision types: Task prioritization, personal performance tracking, daily workflow

What belongs here:

• Personal activity tracker. Calls, emails, meetings, tasks completed — today and this week vs. target. Simple progress bars work best here.
• Personal pipeline (AEs/CSMs). Current deals or accounts with key details: stage, amount, next step date, days in current stage. Sorted by urgency, not alphabetically.
• Inbound queue (SDRs). New leads to work, with aging and SLA status. If a lead has been waiting more than 4 hours for follow-up, it should be visually flagged.
• Goal progress. Monthly quota attainment or OKR progress shown as a simple percentage with the trajectory needed to hit target.
• Next best action. If your ops stack supports it, surface the highest-priority action: the deal that needs follow-up, the lead that is going cold, the customer whose usage just dropped.

What does not belong here: Team-wide metrics, company financials, metrics the IC cannot influence through their daily actions.

The analytics capabilities in your GTM stack should support all three dashboard levels natively. If building these views requires a data engineer and a BI tool, the implementation cost will prevent iteration, and dashboards that cannot iterate quickly end up in the graveyard.

Visualization Principles for GTM Data

Choosing the right chart type is not an aesthetic decision. It directly affects whether people can extract insight from the data.

Trend over time: line chart. Always. Not bar charts for time series — line charts show trajectory and make it easy to spot inflection points. Include a target line or benchmark for context.

Part of a whole: stacked bar or donut. Revenue by source, pipeline by stage, leads by channel. Limit to 5-6 segments maximum. If you have more categories, group the smallest ones into “Other.”

Comparison across categories: horizontal bar chart. Rep performance, channel comparison, campaign results. Horizontal bars are easier to read than vertical ones when category labels are longer than three words.

Single KPI: big number with context. Show the current value in large text, with the comparison period (vs. last month, vs. target) in smaller text below. Color-code: green for on track, red for off track. No chart needed — a number with context is enough.

Distribution: histogram or box plot. Deal size distribution, sales cycle length distribution, activity distribution across the team. These are underused in GTM dashboards but extremely informative for managers.

Things to avoid:

• Pie charts with more than 5 slices
• 3D charts of any kind
• Dual-axis charts (they confuse more than they clarify)
• Tables with more than 10 rows on a dashboard (tables belong in reports, not dashboards)
• Traffic light indicators without the underlying number

Context Is Everything

A metric without context is noise. Every metric on every dashboard should include at least one of these context elements:

Comparison to target. “Pipeline created: $1.8M / $2.2M target.” Instantly tells the viewer where they stand.

Comparison to prior period. “Win rate: 26% (vs. 31% last quarter).” Shows whether things are improving or deteriorating.

Trend direction. An arrow or sparkline showing the last 4-8 data points. Trends reveal patterns that single snapshots miss.

Threshold indicators. Color-coding based on predefined thresholds. Green means on track, yellow means watch closely, red means act now. Define these thresholds explicitly — do not let the dashboard tool auto-scale and decide for you.

The most effective dashboards we have seen combine a big number with a sparkline and a comparison: “Win Rate: 26% [sparkline showing 8-week trend] vs. 31% last quarter.” Three pieces of information in a compact space: the current value, the trajectory, and the benchmark.

Refresh Cadence

Dashboard data freshness should match the decision cadence.

Real-time or near-real-time (refresh every 15-60 minutes):

• IC activity dashboards
• Inbound lead queue
• Live campaign metrics during launch windows

Daily refresh (overnight batch):

• Team lead dashboards
• Pipeline movement views
• Conversion rate dashboards

Weekly refresh:

• Executive dashboards
• Forecast accuracy views
• Strategic trend dashboards

Refreshing executive dashboards in real-time creates anxiety without adding value. Refreshing IC activity dashboards weekly creates blindness. Match the refresh rate to the decision speed.

Embedding Dashboards into Workflows

The biggest driver of dashboard adoption is not design — it is distribution. A beautiful dashboard that lives in a BI tool nobody opens daily is useless. Put the dashboard where people already work.

Slack/Teams integration. Push a daily snapshot of the team lead dashboard to the team channel at 8:30 AM. Push a weekly executive summary every Monday morning. Automated, no manual effort required.

CRM embedding. Embed the IC pipeline dashboard directly in your CRM’s home screen. When reps open Salesforce or HubSpot, the first thing they see is their dashboard. No separate login, no extra tab.

Meeting agendas. Link specific dashboard views to recurring meeting agendas. The Monday pipeline review references Dashboard 2’s pipeline movement view. The monthly business review references Dashboard 1. When the dashboard is the meeting’s source of truth, people pay attention to it.

Email digests. For executives who do not check Slack or dashboards proactively, send a weekly email with a static screenshot of the executive dashboard and three bullet points of commentary from the ops team. This takes 10 minutes to produce and dramatically increases executive engagement with the data.

GTM engineers are often the ones building these distribution mechanisms. If your team does not have dedicated GTM engineering capacity, the RevOps function should own dashboard distribution as part of their reporting responsibilities.

Iterating Based on Usage

Build, ship, and watch what happens. Track which dashboards get viewed, how often, and by whom. Most BI tools provide usage analytics — use them.

After week 1: Check view counts. If a dashboard has fewer than 3 views in its first week, something is wrong. Talk to the intended audience. Did they know it existed? Is it answering the wrong questions? Is it in the wrong place?

After month 1: Survey the dashboard users. Three questions:

1. What is the most useful thing on this dashboard?
2. What is the least useful thing?
3. What question do you have that this dashboard does not answer?

Remove the least useful elements. Add one or two of the most requested missing elements. Do not add everything — keep the constraint of fitting on a single screen.

After quarter 1: Review dashboard usage trends. Identify which views have sustained engagement and which have dropped off. For the ones that dropped off, determine whether the dashboard needs improvement or whether the underlying question has been answered and the dashboard can be retired.

Ongoing: Treat dashboards like a product. They need a roadmap, a backlog, and regular releases. The ops team that builds dashboards and walks away will find themselves rebuilding from scratch every six months.

The Connection to Data Quality

A dashboard built on bad data is worse than no dashboard — it creates false confidence. Before launching any dashboard, validate the underlying data. Pull a sample of 20-30 records and manually verify accuracy. Check that totals reconcile across sources. Confirm that definitions match expectations.

Our Revenue Ops Playbook covers the data unification practices that make reliable dashboards possible. Without unified data, you will spend more time defending your numbers than discussing what to do about them.

The three-dashboard framework, combined with clear visualization principles and embedded distribution, will get your dashboards out of the graveyard and into daily use. Start with one — the team lead dashboard typically delivers the most immediate value — and expand from there.