# Affordance density: how much belongs on a row before it stops being readable

> Agents solve row density in one of two ways: everything visible (unreadable) or almost nothing visible and everything behind a click (high-ceremony). The right answer is a calibrated three-tier model.

Source: https://www.thedesignagent.ai/field-notes/affordance-density · Patterns · 2026-05-06

A data row is a unit of information. How much it holds before it stops being readable is a calibration question, and agents tend to land at one of two extremes: everything visible at once, or almost nothing visible with the rest behind clicks.

The dense version collapses into noise. The sparse version adds ceremony — the user has to expand or click into every row to find the detail that should have been glanceable. Neither is right, and both fail in the same underlying way: they're calibrated to the schema rather than to the user's triage pattern.

## The three-tier model

A well-calibrated row operates on three tiers, each corresponding to how quickly the user needs the information and how often they need it.

**Tier one — always visible, no interaction required.** The primary identifier (what is this record?), the key status or priority signal (does this record need my attention?), and the primary action (what would I do to this record right now?). This is the scanning layer. The user should be able to triage the entire list at this tier — moving quickly past the records that don't need attention and stopping at the ones that do — without a single click.

**Tier two — one interaction away.** Secondary context: related metadata, the most recent activity, a confidence signal with its supporting reasoning, secondary actions that apply to a subset of records. This tier reveals on row hover, expand, or a secondary button — something that requires intent but not navigation. The user who needs it gets it quickly. The user who doesn't need it isn't paying the visual cost of seeing it.

**Tier three — full detail on demand.** The full record, edit state, history, linked entities, audit trail. This is a navigation event — a click into a detail view or an in-place expansion that replaces the row with a richer panel. It represents a context switch and should be designed as one.

> **Pattern:** a well-calibrated row shows everything the user needs to decide at a glance and nothing they don't need until they ask. Tier one enables triage. Tier two enables context. Tier three enables deep work.

## Calibrating to the triage pattern

The right content for tier one depends on the job. For an expense approvals queue, tier one is: vendor name, amount, submitter, approve/reject. The approver is scanning for items that require judgment — anomalous amounts, unfamiliar vendors — and passing quickly through the routine ones. Showing the full expense details at tier one would require reading every row rather than scanning them.

For a support ticket queue, tier one is: ticket title, customer name, priority, assigned agent, age. The support lead is looking for anything urgent and unassigned. Everything else can wait for tier two.

The mistake agents make is using the same tier-one content regardless of job. A generic "name, status, date, actions" row is not calibrated to anything — it's the data model projected onto the row. What goes in tier one has to come from the job, not from the available columns.

## The hover pattern and its limits

Many table designs use hover states to reveal tier-two content. This is a reasonable pattern for desktop workflows with a predictable interaction model. Its limits are worth understanding.

Hover reveals create invisible affordances — the user has to discover that hovering reveals more. For users new to a tool, this creates a learning cost. For users switching between tools, the inconsistency creates re-learning cost. And for touch or stylus-primary contexts, hover doesn't exist.

A better pattern for tier-two actions is a contextual action bar that appears at the row level when the row has focus (keyboard or cursor selection), not on hover. It's more discoverable, works across input methods, and keeps the primary scan uncluttered. The visual difference is subtle. The interaction difference is significant.

## How TheDesignAgent scores it

The `/visual` lens scores `density_fit` — whether the information density of the layout matches the cognitive profile of the job. A low `density_fit` score on a dense row means elements are competing for attention. A low score on a sparse row means the user is paying a click-tax to access information they need frequently.

Patches on density tend to be paired: reduce tier-one content to primary identifier, key signal, and primary action; move secondary context to a hover or expand state. The specific fields moved are named in the patch. The agent gets "move [columns] to tier two" rather than "simplify the row."
