---
name: Information Density
status: draft
territory: spatial-composition
msi_territory: spatial-composition
sources:
  - title: Tufte, Edward R. (1983/2001), The Visual Display of Quantitative Information (2nd ed.), Graphics Press
    url: https://openlibrary.org/works/OL2824012W
  - title: Bertin, Jacques (1967/1983), Semiology of Graphics, University of Wisconsin Press
    url: https://openlibrary.org/works/OL4520539W
  - title: "Cleveland, William S. & Robert McGill (1984), \"Graphical Perception: Theory, Experimentation, and Application to the Development of Graphical Methods,\" Journal of the American Statistical Association 79(387):531-554"
    url: https://doi.org/10.1080/01621459.1984.10478080
---

# Information Density

## Why it matters

A chart is not a picture; it is a sentence made of ink. Every mark on it is either carrying meaning or getting in the way of the marks that do. The trouble is that the marks that get in the way — the drop shadows, the 3-D bevels, the rainbow gradients, the boxed legend eating a third of the canvas — are exactly the ones that look impressive, while the marks that carry the meaning are usually plain. Information density is the discipline of judging a graphic by how much it lets the reader understand per unit of ink and per unit of effort, and then cutting and re-encoding until that ratio is as high as the data will allow.

For example: a quarterly revenue dashboard arrives as a glossy 3-D pie chart with drop shadows, slices in a rainbow gradient, and a legend off to the side that you have to glance back and forth to decode. It looks like a finished, professional object. But ask what the reader is actually being made to do — compare the *angles* of tilted, shaded wedges and match each color to a word in a far-off key — and it falls apart. Redraw the same five numbers as a plain horizontal bar chart with the labels sitting next to the bars, and the comparison the reader came to make becomes effortless. Nothing was added. A great deal was removed. The second chart is denser with meaning precisely because it is sparser with ink.

- **What it reveals.** Whether a graphic earns its ink — which marks carry data, which carry necessary scaffolding, and which are decoration that could be erased without losing a single fact the reader needs.
- **How it changes the read.** You stop asking *"does this chart look polished?"* and start asking *"what exact comparison is the reader meant to make, and is the encoding I chose the most accurate one available for that comparison?"*
- **When to foreground it.** A specific information graphic — a chart, dashboard, table, infographic, map, or typographic page — that has to support a particular reading or decision, and you want prescriptive, mark-by-mark critique rather than a vague "make it cleaner."
- **What you'd miss without it.** That impressiveness and clarity are usually in tension: the features that make a chart look sophisticated — depth, gloss, saturated color, ornament — are frequently the very features that degrade how accurately a reader can extract the numbers.
- **Where it misleads.** Pushed to dogma, the urge to strip ink becomes minimalism for its own sake — erasing a gridline, a label, or a touch of redundancy that was genuinely helping the reader, and mistaking austerity for communication.

## Realtime examples

See real, dated analyses where this mode audited the information graphics behind a news story and redrew them for clarity → **[Information Density on Main Street Independent](https://mainstreetindependent.com/analyses/technique/spatial-composition/information-density)**

## How to invoke it in Ora

You have an information graphic already in hand — a chart, a dashboard, a table, an infographic, a map, a slide, a typographic page — and you want prescriptive, mark-by-mark critique grounded in how graphics actually communicate, not a vague "make it cleaner."

Bring the graphic and ask:

> "Run an Information Density audit on this chart. Here's the data and what the reader is meant to take away. Do a Tufte data-ink audit, check the Bertin visual-variable mapping, and rank the encoding by Cleveland-McGill perceptual accuracy. Give me ranked, specific recommendations."

The phrases *data-ink audit*, *chartjunk*, *visual variables*, and *prescriptive recommendations* are what route you here. Attach the image or describe the marks, axes, encodings, and typography in enough detail for mark-by-mark assessment — a clean image parses far more confidently than a rough sketch, and the mode calibrates accordingly — and always name the **intended message and audience**, because every verdict (which encoding fits, which task the chart must support, which hierarchy is right) depends on what the graphic is trying to say and to whom. State any constraints up front too — brand or house-style, accessibility, data-honesty, audience convention — so the recommendations come back feasible rather than theoretical.

Two boundaries worth knowing. If the input is a *free composition* — a poster, a painting, a page laid out for feel — and the question is the eye-path and visual balance rather than encoding fitness, the compositional-dynamics mode fits better. And if the work is the deliberately held-open *negative space* of a layout, that is the ma-reading mode; this one reads the density and accuracy of the marks, not the emptiness between them.

## How it works

Start with the simplest possible version of the problem and the rest follows. Suppose you have five numbers — the revenue share of five product lines — and one job: let a reader see, at a glance, which line is biggest and by roughly how much. That job is the whole point of the graphic, and everything else is in service of it or in the way of it.

Edward Tufte gave us the first tool for telling the difference. Imagine taking a highlighter and marking only the ink on the page that is actually showing data — the height of a bar, the position of a dot, the number printed on a slice. Everything else is either *structure* you genuinely need (an axis, a single scale reference) or it is **chartjunk**: the drop shadow, the gradient fill, the 3-D extrusion, the heavy box around the legend, the gridline every thousand dollars. Tufte's question is brutally simple: of all the ink on this page, how much of it is data-ink, and how much could you erase and lose *nothing*? A good graphic has a high ratio of data-ink to total ink. The discipline is to go mark by mark and ask of each one, "if I rub this out, does the reader lose a fact?" If not, it goes.

But erasing is only half the craft. The other half is choosing the right way to *draw* each number in the first place, and for that we turn to Jacques Bertin. Bertin noticed that we only have a small handful of ways to encode a value visually — he called them the visual variables, and they are the alphabet of every chart ever made: **position** (where a mark sits), **size** (how big it is), **value** (how light or dark), **color** (which hue), **shape**, **orientation** (which way it tilts), and **texture**. Any chart you can name is just data attributes mapped onto some of these variables. A bar chart maps quantity to *length* and category to *position along an axis*. A pie chart maps quantity to *angle*. A heatmap maps quantity to *value*. Pick the variable that fits the data, Bertin showed, and the chart reads itself; pick the wrong one — quantity onto raw color hue, say — and the reader has to work to decode what should have been obvious.

The third idea tells you *which* variable is the right one, and it is the part most people never learn. William Cleveland and Robert McGill ran the experiments, in 1984, that nobody had bothered to run: they showed people the same numbers encoded different ways and measured how accurately readers could actually judge the magnitudes. The result is a ranking. People read **position along a common scale** more accurately than almost anything else. Then *length*. Then *angle* and *slope*. Then *area*. Then *volume* and *color shading*, down at the bottom, where judgments are wildly imprecise. This single finding is why a bar chart beats a pie chart for the same data: a bar chart asks the reader to compare *positions and lengths* — near the top of the accuracy ranking — while a pie chart asks them to compare *angles and areas*, which sit much lower. The pie isn't ugly; it's just asking the eye to do a job the eye is bad at.

Put the three together and the whole craft of a dense, honest graphic comes into focus. Name the exact comparison the reader has to make. Use Cleveland and McGill to pick the visual variable that supports that comparison most accurately. Use Bertin to check that every other attribute is mapped to a fitting variable too. Then use Tufte to erase everything that is not carrying data, so the encoding you chose so carefully stands clear of the noise. Walk back to the 3-D rainbow pie with that toolkit and the verdict writes itself: the angle-and-area encoding is the least accurate option for a part-to-whole read, the depth and gloss are chartjunk that distort the very magnitudes they decorate, and the rainbow assigns *hue* — a variable Bertin reserves for categories, not amounts — to quantities. Strip it to a sorted bar chart with the numbers beside the bars, and you have packed more meaning into less ink, asking less of the reader, which is the entire game.

## Framework & implementation

*This section uses Ora's own terms for the parts of an analysis, so that if you open the actual mode file they line up. Each is glossed in plain language on first use.*

### Pipeline execution

Information Density is a **molecular mode** in the **spatial-composition** territory — not a single self-contained lens but a composite that *integrates three distinct analytical traditions* into one pass, each catching what the others miss. It runs at **Gear 4**, Ora's most thorough setting: a **Depth analyst** and a **Breadth analyst** work the graphic in parallel and then critique each other (**cross-adversarial evaluation**) before a consolidator integrates the result — so a thin minimalist reading and a wider encoding-and-task reading are forced to reconcile rather than one of them winning by default.

The mode's reasoning is carried by the lenses it loads in its **`ANALYTICAL PERSPECTIVES`** block — the named bodies of theory it applies as it works. Three are load-bearing here, and together they are the mode's whole method: the **tufte-data-ink-chartjunk** lens (classify every mark as data, structure, or junk, and erase the junk), the **bertin-visual-variables** lens (check that each data attribute is mapped to a fitting visual variable — position, size, value, color, shape, orientation, texture), and the **cleveland-mcgill-perceptual-tasks** lens (name the elementary perceptual task the message demands and rank the encoding's accuracy for it — position beats length beats angle beats area). A typographic-hierarchy reading rides alongside when the graphic's lettering is itself part of the encoding.

### Output contract

The deliverable is a fixed set of sections, so the critique is auditable and implementable rather than a loose impression: a **graphic summary and intended message** (what the reader is meant to learn, and the exact comparison the graphic must support — the fixed target the rest of the audit is measured against); a **data structure** read (the attributes in play and whether each is categorical, ordered, or quantitative); the **encoding choices per variable** (each data attribute paired with the visual variable encoding it, with a fitness verdict against Bertin's properties and the mismatch named where one exists); a **data-ink audit** (each mark classified as data-ink, structure-ink, or chartjunk, with the specific marks that could be removed without information loss listed); a **perceptual-accuracy check** (the elementary perceptual task the message requires, and the gap between what the chart asks the eye to do and what the eye does accurately, per Cleveland and McGill); and a **redesign** — prescriptive, ranked recommendations (which mark to remove, which encoding to substitute, which hierarchy to strengthen), each paired with the operation that surfaced it, its impact rank, and any residual tradeoff (brand or house-style, accessibility, data-honesty, audience expectation). Recommendations specific enough to implement without further interpretation are the verification threshold; a vague "simplify, declutter, improve hierarchy" is reshaped at the formatter step.

### Origin and evidence

The three traditions the mode fuses were built decades apart and only later recognized as halves of one craft. Edward Tufte's *The Visual Display of Quantitative Information* (1983) named the data-ink ratio and the idea of chartjunk, turning "good taste" in graphics into a measurable per-mark discipline. Jacques Bertin's *Semiology of Graphics* (originally *Sémiologie graphique*, 1967) laid out the visual variables — the finite alphabet of visual encoding — and the properties that make each one fit or unfit for a given kind of data, founding the formal study of graphics as a language. William Cleveland and Robert McGill's 1984 paper "Graphical Perception," in the *Journal of the American Statistical Association*, supplied the experimental evidence that ranks those encodings by how accurately people actually read them — the finding that turns Bertin's choices from preference into measurement and explains, in hard numbers, why position-based charts beat angle- and area-based ones. The lineage carries forward into modern data-visualization research and the grammar-of-graphics systems that now power most charting tools.

### Applications and common uses

- **Dashboard and report critique.** The native use: a business chart or KPI dashboard audited mark by mark and redrawn so the decision it supports can be read at a glance.
- **Journalism and explanatory graphics.** Auditing the chart behind a story — checking that the encoding does not exaggerate or bury the magnitude the reader is meant to take away.
- **Scientific and technical figures.** Catching the angle-for-length and area-for-position substitutions that quietly distort results in published figures and slides.
- **Maps and infographics.** Testing whether a choropleth, a flow map, or an infographic encodes its quantities on variables the eye reads accurately, rather than on hue or 3-D height.
- **Slide and presentation design.** Stripping the chartjunk that decoration-heavy templates add by default, so a single number or comparison lands.

### Failure modes and when not to use it

- **Tufte-minimalism as dogma.** Treating "erase ink" as an absolute strips gridlines, labels, or a touch of redundancy that was genuinely helping the reader. Minimalism is the default, not a commandment; the mode flags where modest structure or annotation actively serves the message.
- **Recommendations as gestures.** "Simplify" and "improve hierarchy" are not findings — they are the absence of one. The mode's discipline is mark-specific, encoding-specific, hierarchy-specific changes a designer can implement directly.
- **Auditing without a target.** The verdicts all depend on the intended message and audience; run the audit without naming what the graphic must communicate and the perceptual-task and hierarchy checks have nothing to measure against. The mode degrades for rough sketches and surfaces a degraded-audit flag when the input fidelity is too low for mark-by-mark assessment.

**When not to reach for it.** When the input is a *free composition* — a painting, a poster, a page laid out for feel — and the question is the eye-path and the relative visual weight of its parts rather than encoding fitness, route to **compositional-dynamics**, the mode for reading visual force and balance without prescriptive encoding critique. When the operative work is **negative space** — the deliberately held-open void of a typographic page or a contemplative layout — route to **ma-reading**, which reads emptiness as an active element. And when the input is not an information graphic at all but an inhabited place whose character is the subject, that is a different territory entirely.

## Related

- **Compositional Dynamics** — the depth-lighter sibling in the same territory: when the question is how the eye moves across a free composition and where its visual weight sits, not whether a chart's encoding is accurate.
- **Ma Reading** — the stance-counterpart in this territory: reading the deliberately held-open void — negative space as an active element — rather than the density of marks.
- **Tufte Data-Ink and Chartjunk** — one of the three lenses this mode loads: classify every mark as data, structure, or junk, and erase the junk so the signal stands clear.
- **Bertin Visual Variables** and **Cleveland-McGill Perceptual Tasks** — the other two lenses: pick the visual variable that fits each data attribute, and choose the encoding the eye reads most accurately (position over length over angle over area).

## Sources

- [Tufte, Edward R. (1983/2001), The Visual Display of Quantitative Information (2nd ed.), Graphics Press](https://openlibrary.org/works/OL2824012W)
- [Bertin, Jacques (1967/1983), Semiology of Graphics, University of Wisconsin Press](https://openlibrary.org/works/OL4520539W)
- [Cleveland, William S. & Robert McGill (1984), "Graphical Perception: Theory, Experimentation, and Application to the Development of Graphical Methods," Journal of the American Statistical Association 79(387):531-554](https://doi.org/10.1080/01621459.1984.10478080)