Guidelines
Suggest edit

Reduce and shorten columns before publishing a wide table

For dense record-list tables in responsive layouts, use column reduction and shortening on tables to improve readability and mitigate cramped horizontal scanning for readers on mobile screens.

  • purpose:refine
  • basis:heuristic
  • chart:table
  • quality:readability
  • lever:layout-structure
  • density:dense
  • polish:declutter

advice

Column reduction

Reduce the number and width of columns before publishing a wide table. For example, drop nonessential columns, move repeating words into the header, use icons or abbreviations, and shorten or round long numbers.

reason

Why narrower columns help

A narrower table keeps more useful information visible at once and reduces left-to-right strain.

Mechanism: Fewer and shorter columns improve scanability, especially on small screens, because readers do less horizontal reading and see more of each row in one view.

Evidence: The post says tables become more readable with fewer columns, especially on mobile phones, and recommends icons, abbreviations, header consolidation, and shorter or rounded number formats to narrow columns (Muth, 2019).

context

Use when the table is too wide

  • User Goal: Scan rows without heavy horizontal movement.
  • Data: Many fields, repeated words, or long numeric strings.
  • Chart Setting: Responsive table or mobile reading is relevant.
  • Audience: Readers need the essential information quickly.
  • Success Criterion: The essential columns fit comfortably and remain easy to scan.

exceptions

Do not over-apply on already narrow tables

Break it when: The table already has only a few columns and fits comfortably. Why: The rule targets readability problems caused by wide tables.

costs

Tradeoffs of shortening columns

Sacrifice: You may lose full wording or full numeric precision in the visible table.
Risk: Cutting columns blindly can remove information readers actually need.
Mitigation: Keep only essential columns on mobile and show extra columns on desktop if needed.

mistakes

Common width mistake

Mistake: Including all available data as separate full-width columns. Why it fails: The table becomes harder to read, especially on mobile.

check

Check whether the table is too wide

Failure Sign: Rows feel cramped, repeated words fill cells, or long numbers dominate the width.
Quick Check: Preview the table on a phone-sized width and see whether the essential columns still fit cleanly.
Stronger Test: Move repeated terms into headers and shorten long numbers; if the table becomes much easier to scan, the original columns were too wide.

fix

Fix the width

  • Remove columns that are not essential to the story.
  • Move repeated words from cells into the column header.
  • Replace long labels with icons or abbreviations where the meaning stays clear.
  • Use shorter or rounded number formats such as compact millions or fewer decimals.

References

Muth, L. C. (2019). What to consider when creating tables. https://www.datawrapper.de/blog/guide-what-to-consider-when-creating-tables