Overview
Tables are appropriate when content is inherently tabular—when meaning depends on the relationship between rows and columns, such as in datasets, comparisons, or structured reference information. Tables should not be used as a visual or layout device. When the goal is to clarify information hierarchy, group related content, or add visual structure for readability, designers should use headings, columns, or cards instead.
Common Pitfalls to Avoid
- Using tables purely for visual layout or organization
- Putting already hierarchical content into tables
- Using tables to group related but independent ideas
- Presenting instructional, explanatory, or reasoning content in tables
- Using tables when no true data relationship exists
[Example]
Average Home Prices by Year (1980–1989)
| Year | Average Price (USD) |
|---|---|
| 1980 | $47,200 |
| 1982 | $69,300 |
| 1984 | $79,900 |
| 1986 | $92,000 |
| 1988 | $119,600 |
| 1989 | $126,800 |
Guidelines
Do
ID
Production
Use tables when the content is inherently tabular
Use tables when the content is inherently tabular—when meaning depends on relationships between rows and columns. Tables are well suited for datasets, comparisons, and structured reference information where learners benefit from scanning across categories, identifying patterns, or comparing values side by side. In these cases, the grid itself carries meaning and supports understanding.
ID
Production
Use tables when comparison or cross‑referencing is the learning task
Tables are effective when learners need to compare multiple items using the same criteria or reference information across consistent categories. When the instructional goal is to help learners notice similarities, differences, or trends at a glance, a table provides clarity that other layouts cannot.
Do Not
Production
Use tables as a visual or layout device
Tables should not be used simply to add visual structure, symmetry, or variety to a page. When the goal is to make content feel more organized or less text‑heavy, tables introduce unnecessary structure and can imply relationships that do not exist. Visual organization should be achieved through spacing, headings, columns, or cards – not tables.
Production
Use tables to establish information hierarchy
If content already has a clear hierarchy – such as headings with short explanatory text – placing it into a table does not improve clarity. Tables flatten hierarchy and encourage scanning rather than reading, which can obscure meaning instead of reinforcing it. Hierarchical content is better supported through headings, typography, and layout.
Production
Use tables to group related ideas or concepts
Tables imply data relationships, not simple grouping. When the intent is to chunk related ideas, present parallel concepts, or highlight individual items that stand on their own, tables are the wrong tool. Cards or columns provide visual grouping without suggesting comparisons or dependencies between items.
Production
Use tables for instruction, reasoning, or interpretation
Tables are a poor fit for content that requires explanation, context, or judgment. When learners need to follow a line of reasoning, interpret significance, or apply concepts, tables work against those goals by fragmenting narrative flow and hiding emphasis. Instructional and decision‑making content should be presented through text, examples, or interactive activities instead.