An entity — a person, a task, a document — must appear somewhere: inside running text, among its peers in a list, on its own page. Each moment fixes how much of it the actor needs — bare recognition in passing, quick comparison, a full working surface — and no single rendering serves them all.

Forces

• Recognition vs. depth — the entity must be recognisable wherever it appears, yet most appearances need only a fraction of its detail
• Flow vs. focus — the actor wants to stay in the current task, but sometimes must shift into deep work on the entity itself
• Link vs. workplace — the same entity is sometimes a pointer to somewhere else, sometimes a self-sufficient centre of work

Solution

Render the entity at the level of detail its moment needs, chosen from a ladder of representations — glyph, reference, summary, detail — and keep it recognisable as the same entity at every level.

The representation ladder

Item representation is the combination of a ladder rung and a UI element. The two co-vary: choosing a level of detail is also choosing how much surrounding context remains — a reference sits inside running text, a row keeps the collection in view, a full view gives the item the whole frame.

Glyph

• Purpose: locate and encode within a population
• Data: position plus one or two attributes, rendered visually — a map pin’s price, a seat’s colour-shaded availability, a dot on a plot
• Interaction: navigation only — the glyph exists to be opened

The lowest level: it doesn’t even identify the entity by name, and it is only legible in relation to others — a glyph on its own means little.

Reference

• Purpose: identify and link to items
• Data: name, type
• Interaction: navigation

An inline @mention that opens to richer detail on demand, rendered as a reference:

Summary

• Purpose: quick assessment and comparison without leaving current task
• Data: key attributes, status, recent activity
• Interaction: navigation, actions for common operations

As a row in a table:

Detail

• Purpose: inspection of most important information while maintaining context
• Data: relevant details for current task
• Interaction: editing, navigate to full page

Full

• Purpose: complete focus on a single item
• Data: all data, history, relationships
• Interaction: editing, analysis, management

UI element

• Inline: within text or structured UI.
• Contextual overlay: popover, hovercard.
• Transient container: modal, drawer, side panel.
• Dedicated view: section, panel, page, workspace, tab.

Transitions

Item views support fluid navigation up and down the ladder:

• Glyph → summary: click a map pin to open its card
• Reference → summary: hover over an inline reference to reveal a popover
• Summary → detail: click a table row to expand a detail panel or open a modal
• Detail → full: navigate from the modal to the entity page
• Full → collection: return to the parent data view, its framing preserved

Related components

• Reference
• Dialog & drawer
• Card – summary-level item representations

Resources & references

• Shneiderman (1996) The eyes have it — details-on-demand: the ladder makes the “more” steps explicit design decisions instead of one undifferentiated drill-down
• Obenauer — Lab notes — the itemized-OS programme: the item as the primitive that renders across many contexts and levels of detail