Skip to content

Dashboard Design as Information Architecture

Dashboards fail when built to display data rather than support a decision. A framework built on Tufte's data-ink ratio, a layered audience hierarchy, and the common anti-patterns to avoid.

A dashboard is an argument about what matters, not a window into data. Applying Tufte’s data-ink ratio and Stoic clarity, start from the decision the dashboard supports, keep only the primary metrics and their context, remove everything else, and separate executive, manager, and analyst views.

Why do most dashboards fail to communicate?

Most dashboards fail because they are designed as data displays rather than communication tools, optimized for showing everything the data contains rather than answering the specific questions their audience needs resolved.

I audited dashboards across multiple organizations. Of those, only a minority had a documented purpose statement that named the decision the dashboard supports. The rest were built to “show the data” without a defined communication goal. The result was predictable: cluttered screens crowded with visual elements, each technically accurate, collectively unintelligible.

One executive revenue dashboard contained a wall of charts, a cluster of filter controls, several date selectors, and a scrollable data table. The executive who used it told me: “I look at a few numbers and ignore the rest.” Those numbers (monthly recurring revenue, net retention rate, and pipeline coverage ratio) were buried among many other visualizations that served no function in the executive’s decision process.

What is the data-ink ratio, and how do you apply it to dashboards?

Edward Tufte’s data-ink ratio measures the proportion of ink on a page that represents data versus ink that represents decoration, and applying it to dashboards means eliminating every visual element that does not directly support the viewer’s decision.

Tufte defined data-ink as the non-erasable core of a graphic, the ink that, if removed, would reduce the information communicated. Applied to dashboards, this means: gridlines that don’t aid value reading should be removed. Chart borders that don’t distinguish content areas should be removed. Legend entries for single-series charts should be removed. Axis labels for obvious time series (“January, February, March”) should be simplified. Color that doesn’t encode data should be muted to gray.

Step-by-step application framework:

  • Step 1: Define the decision. Write one sentence: “This dashboard helps [role] decide [action] by showing [a small set of metrics].” If you cannot write this sentence, the dashboard has no clear purpose
  • Step 2: Identify primary metrics. List only the numbers that directly inform the decision. These get prominent placement: large type, top-left position, minimal surrounding decoration
  • Step 3: Identify supporting context. For each primary metric, identify the fewest contextual views that explain why the metric has its current value (trend line, breakdown by dimension, comparison to target)
  • Step 4: Remove everything else. Every chart, table, and visual element that is not a primary metric or supporting context should be removed or moved to a separate detail view accessible via drill-down
  • Step 5: Minimize non-data elements. For every remaining chart, remove gridlines (or reduce to a minimal set of reference lines), remove chart borders, remove legends that can be replaced by direct labels, simplify axis formatting, and reduce the color palette to a restrained set of meaningful hues plus gray

How does the Stoic value of clarity apply to information design?

The Stoic commitment to clarity, saying exactly what is true and nothing more, translates directly to dashboard design: every element should convey meaning, and anything that does not convey meaning is not neutral but actively harmful because it competes for the viewer’s attention.

Marcus Aurelius wrote: “If it is not right, do not do it. If it is not true, do not say it.” Applied to dashboards: if a chart does not support a decision, do not display it. If a number does not represent something the viewer needs to know, do not show it. Silence is not emptiness; it is the space that allows what matters to be heard.

I redesigned a pipeline health dashboard using this principle. The original had a crowded set of visualizations including a real-time task execution timeline, a historical completion rate chart, a resource utilization gauge, an error distribution heatmap, and many other views. The redesigned version kept a short list of elements: a current status indicator (green/yellow/red with the specific issue description), a recent trend of SLA compliance, the latest failures with root cause, and the next scheduled maintenance window.

The on-call engineer who used this dashboard said: “I can now tell at a glance whether I need to act.” The previous version required scrolling through a long page of charts to reach the same conclusion.

How do you structure dashboard hierarchy for different audiences?

Dashboard hierarchy should follow the inverted pyramid: executives see a few summary metrics, managers see breakdowns and trends, and analysts see detail tables and filters, with each level accessible from the one above but never cluttering it.

  • Level 1 (Executive): large-format KPIs with directional indicators (up/down, on-track/off-track). No charts. No tables. Decision time target: only a glance
  • Level 2 (Manager): Each Level 1 KPI expands to show trend (sparkline or multi-week chart), breakdown by primary dimension (region, product, team), and comparison to target or prior period. A small number of visual elements in total. Decision time target: a short, focused review
  • Level 3 (Analyst): Full detail with filters, date range selectors, exportable tables, and cross-dimensional analysis. No limit on complexity because the audience has analytical skill and exploratory intent
  • Navigation rule: Each level links to the level below through click-through. Never combine levels on a single screen. The most common dashboard failure is showing Level 3 detail to a Level 1 audience

What are the most common dashboard anti-patterns?

The most common anti-patterns are: dual-axis charts that create false correlations, pie charts with many categories, traffic-light indicators without thresholds, real-time refresh on metrics that change daily, and dashboards that default to “all time” date ranges.

  • Dual-axis deception: Two Y-axes on the same chart allow arbitrary scaling that creates visual correlations between unrelated metrics. I found a dashboard where revenue and headcount appeared perfectly correlated because the axes were scaled to align. The actual correlation was negligible
  • Pie chart overuse: Pie charts are effective for showing part-to-whole relationships among very few parts. For many categories, a horizontal bar chart communicates the same information with less cognitive load and more precise comparison
  • Meaningless traffic lights: Red/yellow/green indicators without documented thresholds create the illusion of monitoring without the substance. Every status indicator should have a tooltip or footnote explaining: “Green means X metric is above Y threshold, measured over Z period”
  • False urgency refresh: Dashboards that refresh constantly for metrics that change meaningfully once per day create anxiety without information. Match refresh rate to the metric’s meaningful change frequency
  • Unbounded date ranges: “All time” defaults obscure recent trends by compressing them against years of historical data. Default to the most relevant analysis window (recent weeks, current quarter) and provide date range selection for deeper exploration

A dashboard is not a window into data. It is an argument about what matters. Every element on the screen asserts: “This deserves your attention.” The discipline of dashboard design is the discipline of deciding what deserves attention and what does not, then having the courage to exclude the rest. Tufte called it maximizing the data-ink ratio. The Stoics called it clarity. The practice is the same: say what is true, show what matters, and let everything else fall away.

adam@adam-analytics.com writes about AI systems, software architecture, and the philosophy of technology at .