Dashboards

In Brief

A dashboard is a visual display that brings key product and business metrics into a single view. You select the metrics that matter most — such as active users, conversion rates, revenue, or retention — and present them in a format the whole team can check at a glance. The output is a real-time picture of product health that surfaces trends, anomalies, and the effects of complex factors like seasonality, competitor moves, or conflicting experiments.

Description

In situations where there is great uncertainty, planning for the future has less value than having a clear picture of the current status. Dashboards give you a visual “information radiator” that shows the exact current status on key metrics affecting operations:

• How much of a product is built, or a goal already achieved?
• What is the state of current channel-testing in marketing?
• What is our market share?

Dashboards help visualize inter-relationships among parts of a business. For example, a $10k investment in a channel may seem like a lot of money, unless you knew that last year’s revenue was $250k.

Dashboards are inherently motivating. They presuppose an open and data-driven culture. For many employees and partners, this level of trust and transparency motivates them to do their best work. By going through the effort of choosing one or a handful of key metrics for the whole organization, you generate a lot of focus. Dashboards help maintain this focus operationally if everyone continually checks a dashboard that contains those key metrics driving the business.

This technique can be used for:

• The company as a whole
• Specific departments
• Key roles (such as the VP of Marketing’s dashboard)
• Individual contributors

In terms of how it works, it can be anywhere from “manually using a spreadsheet” to a custom-built monitoring system that integrates a number of the business systems so that you have a “real-time view” of the company. Stephen Few’s Information Dashboard Design frames the goal as at-a-glance monitoring — the reader should grasp the state of the business in seconds — and the hard design problem is what to leave off.

Choosing what goes on is what most teams get wrong. Eric Ries argues in The Lean Startup that “vanity metrics” — total registered users, raw page views, cumulative downloads — go up and to the right regardless of whether the product is improving, and crowd out metrics teams could act on. Pick metrics that pass Ries’s actionable, accessible, auditable test, and treat the dashboard as a prompt for investigation, not its conclusion.

How to

Prep AI Prompt

1. Decide what the dashboard is for. Write one sentence naming the decision the dashboard exists to support (e.g., “should we keep investing in this acquisition channel?”). If you can’t name the decision, the dashboard will collect metrics no one acts on.
2. Choose 5–7 candidate metrics that pass the actionability test. Avinash Kaushik, Analytics Evangelist for Google at the time he published Web Analytics 2.0, emphasises that a metric earns its place only if a movement changes what the team will do next week. For each candidate, write the action you’d take on a 20% move in either direction; if you can’t, cut it.
3. Confirm the data source is ready. Check that underlying events, definitions, and time-zone handling are stable enough to trust. Nothing erodes a dashboard’s authority faster than a metric whose definition silently changed.
4. Decide audience, cadence, and access policy. Whole-company, departmental, or role-specific? Reviewed in standup, weekly, or monthly? Public or restricted? Each combination changes what belongs on the screen.
5. Pilot one metric before scaling. Wire a single metric end-to-end (data → display → review ritual) and run it for a week. You’ll surface the data-quality and visualization gotchas before they’re embedded across seven panels.

Analysis AI Prompt

Dashboard colors, shapes (traffic light), and status icons help you quickly interpret the reported data. The size of each component should also reflect the importance of the data point. Edward Tufte’s The Visual Display of Quantitative Information supplies the diagnostic vocabulary: maximise the data-ink ratio (every pixel should encode information, not decoration), strip chartjunk (3D bevels, drop shadows, redundant gridlines), and watch the lie factor (an effect’s size on the chart should match its size in the data). Stephen Few’s bullet graph is a useful default for KPI panels — current value, target, and qualitative range in a single horizontal strip.