Heatmaps suit dense two-dimensional values
Aliases: heatmap use case · numeric matrix · cell color map
What it is
A heatmap arranges two discrete or discretized dimensions as rows and columns and maps one value in each cell to color. It suits finding blocks, bands, gradients, hotspots, and anomalous rows or columns in a dense matrix because many values share a regular grid instead of each requiring a bar and label. “Suits” refers to overview and structure-finding tasks. A heatmap is not the only defensible large-matrix display, and no universal row-by-column threshold determines its use.
Why it happens
The regular grid jointly preserves row identity, column identity, and adjacency, while color turns values into a field that can be scanned in parallel. Readers can integrate neighboring cells before returning to row and column labels to locate a pattern. That capacity trades away single-cell magnitude precision: color lacks the common reference supplied by position or length, and lookup becomes harder with similar colors, tiny cells, distant labels, or scrolling. Without a distinct encoding, missing values may also be mistaken for zero or the scale midpoint.
Studying it
Use synthetic matrices with known blocks, bands, anomalies, and missing values while manipulating dimensions, sparsity, effect strength, label length, and screen size. Compare heatmaps with tables, dot matrices, or faceted charts on separate pattern-detection, target-search, cell read-off, pairwise-difference, and row-column lookup tasks; record accuracy, time, confidence, and scrolling. With real data, ask domain readers to explain discoveries and confirm them against prespecified statistics or held-out data rather than treating salience as stable evidence.
Where it stops holding
Sparse relations, exact values, long text, or irregular networks may favor a table, scatterplot, or node-link view; a small matrix may not need color encoding. Cell area should not imply another quantity. Extreme skew, mixed units, and incomparable rows or columns require preprocessing or separate views. Hover can supplement pointer use but cannot replace keyboard access, programmatic names, a visible legend, or downloadable data. Display, vision, and environment affect color discrimination, so consequential judgments need values or another redundant channel.
Applying it
- State the primary task first: use a heatmap for structure finding, and add a table, labels, or a detail view for exact reading.
- Keep row and column labels traceable with stable highlighting and frozen headers or synchronized scrolling; encode missing, zero, and out-of-range states distinctly.
- Decide pagination, zoom, or aggregation from available space and task tests instead of a fixed matrix-size cutoff.
- Test block finding, cell lookup, value reading, and export on representative devices and assistive technology; keep scale, order, filters, and data version synchronized across views.
Related
- Same group: U2.10.2 Row and column ordering decides whether structure is visible · U2.10.3 Colour scale choice directly shapes the conclusion
- Adjacent: U2.16.1 Tables beat charts when exact values are needed · U4.02.1 Sequential scales must increase perceptually monotonically
- Search terms:
heatmap·matrix visualization·ensemble perception·dense values