What This Template Is For
A dashboard that nobody looks at is worse than no dashboard at all. It consumes engineering time to build and maintain, creates a false sense of measurement, and quietly goes stale. The problem is rarely the data. It is the design. Most product dashboards fail because they pack too many metrics into one view, use the wrong chart types, or serve too many audiences at once.
This template helps you design data visualizations and dashboards that people actually use. It covers chart type selection for different data shapes, dashboard layout hierarchy, audience-specific views, and common design mistakes. It is not a tool tutorial (your BI tool documentation covers that). It is a decision framework for what to show, how to show it, and to whom.
The Product Analytics Handbook covers the strategic context for what to measure. The analytics audit template helps you identify which metrics are worth visualizing before you build dashboards. For specific metric definitions, the glossary entry on product metrics provides a reference. The feature adoption rate metric and activation rate metric are among the most commonly visualized product metrics.
How to Use This Template
- Define the audience for this visualization. A dashboard for the product team is different from one for the executive team.
- Identify the 3-5 primary metrics the audience cares about. Resist adding more. Every additional metric dilutes attention.
- Select chart types based on the data shape (comparison, trend, composition, relationship).
- Lay out the dashboard using the hierarchy template (summary at top, detail below).
- Build a prototype in your BI tool. Share it with 2-3 stakeholders for feedback before investing in polish.
- Set a review cadence. Dashboards that are never updated become misleading.
The Template
Section 1: Audience and Purpose
| Field | Details |
|---|---|
| Dashboard name | [e.g., "Product Health Dashboard - Weekly"] |
| Primary audience | [e.g., "Product team (PMs, designers, engineers)"] |
| Secondary audience | [e.g., "VP Product, CPO (monthly review only)"] |
| Core question it answers | [e.g., "Is the product getting healthier or sicker this week?"] |
| Review cadence | [Daily / Weekly / Monthly / Quarterly] |
| Tool | [Looker / Metabase / Amplitude / Mode / Google Sheets] |
| Data refresh | [Real-time / Daily / Weekly] |
Section 2: Chart Type Selection Guide
Choose the chart type based on what you are trying to show, not what looks interesting.
Comparison (how does X compare to Y?)
| Chart Type | Best For | Avoid When |
|---|---|---|
| Bar chart (vertical) | Comparing 3-10 categories (e.g., feature usage by feature) | More than 12 categories (use horizontal bars) |
| Bar chart (horizontal) | Comparing many categories, long labels | Showing time trends |
| Grouped bar chart | Comparing categories across 2-3 segments | More than 3 segments (too cluttered) |
Trend (how does X change over time?)
| Chart Type | Best For | Avoid When |
|---|---|---|
| Line chart | Continuous trends over 5+ time periods | Fewer than 5 data points (use bar chart) |
| Area chart | Showing volume changes over time | Overlapping series that hide each other |
| Sparkline | Compact trend in a table cell or KPI card | Needing exact values (too small for labels) |
Composition (what makes up the total?)
| Chart Type | Best For | Avoid When |
|---|---|---|
| Stacked bar chart | Part-to-whole across categories or time | More than 5 segments (bottom slices are unreadable) |
| Pie/donut chart | 2-4 segments with one dominant slice | More than 5 segments or similar-sized slices |
| 100% stacked bar | Comparing proportions across groups | Needing absolute values |
Relationship (how are X and Y related?)
| Chart Type | Best For | Avoid When |
|---|---|---|
| Scatter plot | Showing correlation between two metrics | Fewer than 20 data points |
| Bubble chart | Adding a third dimension (size) to scatter | Overlapping bubbles at same scale |
| Heatmap | Two-dimensional density (e.g., day x hour) | Continuous rather than categorical axes |
Distribution (how is X spread?)
| Chart Type | Best For | Avoid When |
|---|---|---|
| Histogram | Showing distribution shape (e.g., session durations) | Comparing distributions across groups |
| Box plot | Comparing distributions across 3+ groups | Non-technical audiences (unfamiliar format) |
| KPI card with P50/P90 | Executive summary of distribution | Needing full distribution detail |
Section 3: Metric Hierarchy
Organize metrics into tiers. The dashboard layout should follow this hierarchy: Tier 1 metrics at the top (largest, most prominent), Tier 2 in the middle, Tier 3 at the bottom or in expandable sections.
| Tier | Metric | Chart Type | Size on Dashboard | Update Frequency |
|---|---|---|---|---|
| Tier 1: North Star | [e.g., Weekly Active Users] | [KPI card with sparkline] | [Large, top of page] | [Daily] |
| Tier 1: North Star | [e.g., Activation Rate] | [KPI card with sparkline] | [Large, top of page] | [Daily] |
| Tier 2: Health | [e.g., Retention by cohort] | [Line chart, 8 cohort lines] | [Medium, mid-page] | [Weekly] |
| Tier 2: Health | [e.g., Feature adoption breakdown] | [Horizontal bar chart] | [Medium, mid-page] | [Weekly] |
| Tier 2: Health | [e.g., Support ticket volume] | [Line chart with trend] | [Medium, mid-page] | [Daily] |
| Tier 3: Detail | [e.g., Engagement by plan tier] | [Grouped bar chart] | [Small, bottom] | [Weekly] |
| Tier 3: Detail | [e.g., Funnel conversion rates] | [Funnel chart] | [Small, bottom] | [Weekly] |
| Tier 3: Detail | [e.g., Error rates by page] | [Table with conditional formatting] | [Small, bottom] | [Daily] |
Section 4: Dashboard Layout Template
Row 1: Summary KPIs (always visible at top)
| KPI 1 | KPI 2 | KPI 3 | KPI 4 |
|---|---|---|---|
| [North Star metric] | [Activation rate] | [Retention rate] | [Revenue metric] |
| [Current value + % change] | [Current + % change] | [Current + % change] | [Current + % change] |
| [Sparkline, 8 weeks] | [Sparkline, 8 weeks] | [Sparkline, 8 weeks] | [Sparkline, 8 weeks] |
Row 2: Primary Trends (50% of page)
| Left (60% width) | Right (40% width) |
|---|---|
| [Main trend chart: e.g., WAU over 12 weeks with target line] | [Composition chart: e.g., users by plan tier] |
Row 3: Secondary Metrics (30% of page)
| Left | Center | Right |
|---|---|---|
| [Health metric 1] | [Health metric 2] | [Health metric 3] |
Row 4: Detail Tables (expandable or scrollable)
| Full width |
|---|
| [Sortable data table with key metrics per feature/segment/cohort] |
Section 5: Design Checklist
Apply these rules to every visualization before sharing.
Data integrity:
- ☐ Every metric has a visible definition (tooltip or footnote)
- ☐ Time zones are consistent and documented
- ☐ Null values are handled (excluded, shown as zero, or interpolated)
- ☐ Data freshness timestamp is visible ("Last updated: March 5, 2026 08:00 UTC")
- ☐ Sample size is shown for any percentage-based metric
Visual clarity:
- ☐ Y-axis starts at zero for bar charts (non-zero baselines distort perception)
- ☐ Line charts may use non-zero baselines when changes are small but meaningful
- ☐ Color is used for meaning, not decoration (red = bad, green = good, gray = neutral)
- ☐ No more than 7 colors per chart (human color discrimination limit)
- ☐ Labels are readable at the intended screen size
- ☐ Chart titles state the insight, not just the metric ("Retention improving since onboarding redesign", not "Retention Rate")
Actionability:
- ☐ Every chart answers a specific question (if you cannot state the question, remove the chart)
- ☐ Target/benchmark lines are shown where available
- ☐ Annotations mark significant events (launches, incidents, holidays)
- ☐ Drill-down paths exist for metrics that need investigation
Section 6: Audience-Specific Views
| Audience | Metrics to Show | Metrics to Hide | Cadence | Format |
|---|---|---|---|---|
| Product team | All Tier 1-3 metrics, feature-level detail | Revenue details (unless product-led growth) | Daily/Weekly | Dashboard |
| Engineering | Error rates, latency, API performance, deploy frequency | Revenue, NPS | Daily | Dashboard |
| CS team | Account health, ticket trends, NPS, feature requests | Feature-level usage detail | Weekly | Dashboard + report |
| VP/CPO | Tier 1 KPIs, cohort trends, top risks | Feature-level detail, engineering metrics | Weekly | 1-page report |
| CEO/Board | North star, revenue, retention, growth rate | Everything else | Monthly/Quarterly | Slide deck |
Filled Example: Product Health Dashboard (SaaS Collaboration Tool)
Dashboard Summary (Week of Feb 24, 2026)
| WAU | Activation Rate (7d) | D30 Retention | MRR |
|---|---|---|---|
| 12,400 (+3.2%) | 38% (+2pp) | 52% (flat) | $284K (+1.8%) |
Primary Trend: WAU Over 12 Weeks
Chart type: Line chart with weekly data points, target line at 13,000.
Annotation: "Onboarding v2 launched" at week 8. WAU trend shifted from flat to +3-4% weekly after the launch.
Feature Adoption (Horizontal Bar Chart)
| Feature | % of WAU Using |
|---|---|
| Task creation | 89% |
| File sharing | 62% |
| Comments | 54% |
| Dashboards | 31% |
| Integrations | 24% |
| API | 8% |
Insight: Dashboards and Integrations adoption is well below target (40% and 35%). Scheduled guided discovery experiment for both.
Design Decisions
| Decision | Rationale |
|---|---|
| KPIs at top with sparklines | Executives scan the top row in meetings; sparklines show trajectory without a separate chart |
| Horizontal bars for feature adoption | 6 features with long names; vertical bars would need rotated labels |
| No pie charts | All metrics are either trends or comparisons; no composition question to answer |
| Gray for baseline, cyan for current | Matches brand palette; reduces visual noise vs. multicolor |