“We built a dashboard six months ago with twenty metrics on it. Nobody looks at it anymore. How do we build one that people actually use?”
A dashboard should be the first thing you look at when you start your workday and the last thing you check before making a big decision. It should tell you, at a glance, whether your business is healthy, where problems are emerging, and whether the changes you made last week are working. That is what a well-designed dashboard does.
Most dashboards fail to deliver this. They are cluttered with metrics nobody checks, organized by data source instead of by business question, and designed during an enthusiastic setup session that nobody revisited. The result is a dashboard that gets ignored - a wasted investment that creates the illusion of data-driven culture without the substance.
This guide covers how to design KISSmetrics dashboards that people actually use: choosing the right metrics for each role, configuring widgets effectively, laying out the dashboard for fast comprehension, setting up alerts that catch problems early, establishing review cadences that build habits, and avoiding the dashboard overload that causes teams to abandon their analytics entirely.
Choosing Metrics for Your Role
The single most important principle of dashboard design is that different roles need different metrics. A dashboard designed for everyone is optimized for no one. Build separate dashboards for each role, each containing only the metrics that person needs to make their daily and weekly decisions.
CEO Dashboard
The CEO needs to see the business from 30,000 feet. The metrics should answer: are we growing, are we profitable, and are our customers healthy? A CEO dashboard should include monthly recurring revenue (MRR) and its trend, net revenue retention rate, total customer count and growth rate, customer acquisition cost (CAC), and lifetime value to CAC ratio. That is five metrics. Not fifty. The CEO does not need to know the conversion rate on a specific landing page. They need to know whether the business is fundamentally healthy and moving in the right direction.
VP of Marketing Dashboard
The VP of Marketing needs to understand acquisition efficiency and channel performance. Key metrics include: new users by channel (with week-over-week trend), cost per acquisition by channel, trial-to-paid conversion rate, marketing-sourced revenue, and pipeline by stage. These metrics enable weekly budget allocation decisions and quick identification of channels that are over- or under-performing expectations.
Product Manager Dashboard
The Product Manager needs to understand engagement and feature performance. Key metrics include: daily and weekly active users, feature adoption rates for recently launched features, activation rate (percentage of new users who reach the “aha moment”), retention rate (7-day, 30-day), and top support-reported issues. These metrics reveal whether the product is delivering value and where the biggest improvement opportunities lie.
Growth Lead Dashboard
The Growth Lead needs to see the full conversion funnel with diagnostic detail. Key metrics include: funnel conversion rates at each step, conversion rate by device and source, experiment results for active A/B tests, activation rate for recent cohorts, and time-to-value for new users. These metrics support rapid iteration on the acquisition and activation experience. Pairing this with an actionable metrics framework ensures every number on the dashboard drives a decision.
Customer Success Dashboard
Customer Success needs to see account health and churn risk. Key metrics include: accounts by health score, churn rate (gross and net), expansion revenue rate, NPS or satisfaction scores, and support ticket volume and resolution time. These metrics enable proactive outreach to at-risk accounts and identification of systemic issues affecting customer satisfaction.
Widget Configuration
Each metric on your dashboard is displayed through a widget. Choosing the right widget type for each metric makes the difference between a dashboard that communicates clearly and one that requires interpretation.
Single Number Widgets
Use single number widgets for metrics where the current value is more important than the trend: total MRR, current customer count, active experiment count. Include a comparison indicator (up or down arrow with percentage change from the previous period) to provide context. A number without context is just a number. A number with a trend direction is information.
Line Charts
Use line charts for metrics where the trend matters more than any single data point: daily active users over the past 30 days, weekly conversion rate over the past quarter, MRR growth over the past year. Line charts make it easy to spot trends, seasonality, and anomalies. Keep the y-axis consistent across time to avoid visual distortions that make small changes look dramatic.
Bar Charts
Use bar charts for comparing discrete categories: revenue by channel, users by plan type, conversion rate by device. Bar charts make it easy to compare magnitudes across categories. Sort bars by value (largest to smallest) rather than alphabetically to make the most important comparisons immediately visible.
Tables
Use tables when you need to show multiple measures for each dimension: a table of campaigns with columns for spend, users acquired, revenue attributed, and ROI. Tables are the most information-dense widget type but also the hardest to scan quickly. Reserve them for detailed analysis sections of the dashboard, not the top-level overview.
Dashboard Layout Principles
How you arrange widgets on a dashboard determines how quickly someone can extract the information they need. Good layout follows the way people naturally read and process visual information.
Top-Down Hierarchy
Place the most important metrics at the top of the dashboard. People read top to bottom and spend the most attention on what they see first. Your headline metrics - the ones that tell you whether the business is healthy at a glance - belong in the first row. Supporting detail and diagnostic metrics belong lower on the page. The KISSmetrics metrics dashboard supports flexible widget placement so you can arrange your dashboard to match this hierarchy.
Group Related Metrics
Place related metrics near each other so they can be interpreted in context. Acquisition metrics (traffic, sign-ups, cost per acquisition) should be grouped together. Engagement metrics (active users, feature adoption, session frequency) should be in another group. Revenue metrics (MRR, ARPU, expansion revenue) in another. This grouping reduces the cognitive effort required to synthesize related information.
Limit the Scroll
If your dashboard requires scrolling to see all the metrics, it is too long. The most important information should be visible without scrolling. If you need more metrics, either create a separate dashboard for the detail or use expandable sections that hide supporting metrics until they are needed. A dashboard that requires scrolling through ten screens of widgets will never be checked daily because it takes too long.
Consistent Formatting
Use the same color scheme, number formatting, and time ranges across all widgets. If one widget shows the last 30 days and another shows the last 90 days, comparisons become confusing. If one widget uses blue for positive trends and another uses green, the visual language becomes inconsistent and harder to read quickly.
Setting Up Alerts
Dashboards require you to look at them. Alerts come to you. A good alerting system ensures that critical changes in your metrics are detected and communicated even if nobody happens to check the dashboard that day.
Threshold Alerts
Set alerts when a metric crosses a predefined threshold. Daily sign-ups drop below 50. Error rate exceeds 5%. Churn rate surpasses 3%. Threshold alerts catch acute problems - sudden drops or spikes that indicate something is broken or changed unexpectedly. Set thresholds conservatively at first (only alert for clearly problematic values) and tighten them as you learn what normal variation looks like.
Trend Alerts
Threshold alerts miss slow declines. A conversion rate that drops by 0.5% per week will not trigger a threshold alert until it has degraded significantly. Trend alerts detect these gradual changes by monitoring whether a metric has been declining (or increasing) for a specified number of consecutive periods. A trend alert might fire when conversion rate has declined for three consecutive weeks, even if the absolute value has not yet crossed a threshold.
Alert Fatigue Prevention
The enemy of effective alerting is alert fatigue. If the team receives twenty alerts per week, they will start ignoring all of them. Set alerts only for metrics that require immediate attention or investigation. Each alert should trigger a specific action: check the dashboard, investigate the cause, or notify a team member. If an alert does not lead to action, remove it. The goal is a system where every alert is taken seriously because every alert represents a real issue.
Daily vs. Weekly Review Cadence
Building a dashboard is the first step. Actually looking at it consistently is the harder and more important step. Establishing a review cadence - a regular rhythm of checking your dashboard and acting on what you see - is what turns analytics from a tool into a practice.
The Daily Check
The daily check should take two to three minutes. Glance at the top-level metrics. Are they within normal range? Has anything spiked or dropped unexpectedly? If everything looks normal, move on with your day. If something looks unusual, investigate. The daily check is about anomaly detection: catching problems before they become crises.
The best time for the daily check is first thing in the morning, before you open email or start meetings. Make it a habit by linking it to an existing routine: open laptop, check dashboard, then open email.
The Weekly Deep Dive
The weekly review should take 15 to 30 minutes and go deeper. Compare this week’s metrics to last week’s. Review trends over the past month. Check progress against goals. Identify the biggest opportunities for improvement. The weekly review is about strategic awareness: understanding the trajectory of your metrics and deciding where to focus your effort for the coming week.
Many teams incorporate the weekly review into a standing meeting. The marketing team reviews their dashboard every Monday morning. The product team reviews theirs every Wednesday. The cadence matters less than the consistency. Pick a time, commit to it, and protect it from being displaced by other meetings.
The Monthly Retrospective
Once per month, review the month as a whole. Did you hit your targets? What changed and why? What did you learn? What will you do differently next month? The monthly retrospective is about learning: converting a month of data into insights that improve your strategy. This is also the right time to review whether your dashboard metrics are still the right ones and whether any widgets need to be updated or replaced.
Avoiding Dashboard Overload
Dashboard overload is the most common reason analytics initiatives fail to produce lasting behavior change. Teams build comprehensive dashboards with dozens of metrics, feel overwhelmed by the volume of data, and gradually stop checking them. Avoiding this requires discipline.
The Five-Metric Rule
Start with five metrics per dashboard. Not fifteen. Not ten. Five. If you cannot summarize your area of responsibility in five metrics, you have not thought carefully enough about what actually matters. The discipline of choosing five forces you to prioritize ruthlessly. Which five numbers, if they moved in the right direction, would mean your business is succeeding? Those are your dashboard metrics. Everything else is diagnostic detail that you access only when the headline metrics indicate a problem.
Diagnostic Drill-Down
Instead of putting every metric on the dashboard, create a two-tier system. The dashboard shows the five headline metrics. Each headline metric links to a detailed view with supporting metrics, breakdowns, and trends. When a headline metric moves unexpectedly, you drill down to the detail to understand why. This approach keeps the dashboard clean while ensuring all the diagnostic data is accessible when needed.
Kill Unused Widgets
If you have not looked at a widget in two weeks, remove it. If nobody can explain why a metric is on the dashboard, remove it. If a metric has not changed meaningfully in three months, it is not telling you anything new and is consuming visual space that could be used for something more informative. KISSmetrics makes it easy to add and remove widgets, so treat your dashboard as a living document that evolves with your business priorities.
Evolving Your Dashboard Over Time
Your dashboard should evolve as your business evolves. The metrics that matter during a product launch are different from the metrics that matter during a scaling phase, which are different from the metrics that matter when you are optimizing for profitability.
Early Stage: Acquisition and Activation
When your product is new, the most important metrics are: are people signing up, and are they getting value? Dashboard focus: sign-up rate, activation rate, early retention (7-day), qualitative feedback volume. Revenue metrics matter less at this stage because you are still validating that the product delivers value. Understanding your activation rate is the highest priority at this stage.
Growth Stage: Conversion and Efficiency
When your product has achieved initial traction, the focus shifts to scaling efficiently. Dashboard focus: conversion rate through the full funnel, customer acquisition cost by channel, trial-to-paid conversion rate, payback period. Revenue metrics become central because you need to ensure that growth is economically sustainable.
Scale Stage: Retention and Expansion
When acquisition is working, the focus shifts to keeping and expanding your customer base. Dashboard focus: net revenue retention, churn rate by segment, expansion revenue, customer health scores. At this stage, a one-point improvement in retention often has more impact on the business than a significant increase in acquisition, and the dashboard should reflect that priority.
Quarterly Dashboard Review
Every quarter, review your dashboards with your team. Ask: are these still the right metrics? Do they reflect our current priorities? Is anyone looking at all of them? Are we missing anything important? This review prevents dashboard drift, where the metrics slowly diverge from the business priorities and the team gradually stops paying attention.
Key Takeaways
The companies that make the best decisions are not the ones with the most data. They are the ones that put the right data in front of the right people at the right time. That is what a well-designed dashboard does: it makes good decisions easy and bad decisions hard to justify.
Continue Reading
Power Reports: Build Custom Analytics Views for Any Business Question
Standard reports answer standard questions. Power reports let you build custom views that answer the specific questions unique to your business, with flexible dimensions and measures.
Read articleActivity Reports: Track Individual User Behavior in Real Time
Activity reports show you the exact sequence of actions any individual user takes in your product. This level of detail helps debug issues, understand power users, and personalize outreach.
Read articleA/B Test Reports: Measure Experiment Impact Beyond the Landing Page
Most A/B test reports stop at conversion rate. KISSmetrics A/B test reports track the downstream impact on revenue and retention, showing whether your winner actually wins where it counts.
Read article