Problem
Someone asks how four options compare across three criteria. The answer arrives as five paragraphs. Every fact is present and the reader has to hold twelve values in their head to do the comparison the question asked for.
Solution
Let the answer take the shape of the question. A comparison is a table. A sequence wants numbers down the left margin. Anything measured over time belongs on a chart. Prose is the right container for an argument and the wrong one for a grid, and a model that writes everything as paragraphs is defaulting rather than choosing.
NN/g’s finding on site chatbots points the same way: people arrive wanting an answer they can scan, not a conversation, and responses should be direct and structured with detail available on demand. The general form of that is to match the output’s structure to the information’s structure.
Tables are where most of the value and most of the failure sits. A generated table is reliable about its shape and much less reliable about its contents, and the visual authority of a grid is considerably higher than that of a paragraph. The same wrong number is questioned in prose and accepted in a cell. Where cells carry facts drawn from sources, per-cell attribution does more work than a citation on the whole answer.
Rendering has to survive contact with reality. Markdown tables break when a cell contains a pipe, wrap badly at narrow widths, and can’t be sorted. Once a table is more than about four columns it needs a real container with horizontal scrolling of its own, so that a wide grid doesn’t force the whole page sideways. Exporting to CSV is a small addition that converts an artifact people screenshot into one they use.
Accessibility is the part skipped most often. A grid rendered with alignment and spacing instead of real table semantics is unreadable to a screen reader, which announces a wall of numbers with no way to associate a value with its row and column. Header cells have to be marked as headers.
The honest limit is that the model chooses the structure, and it chooses badly in both directions. Forcing a three-row table onto a simple answer adds ceremony; answering a genuinely tabular question in prose loses the comparison. Letting the viewer ask for a different shape after the fact is cheaper than getting the routing right every time.
Use when
The information has a natural structure and the reader’s task is comparison, sequence, or lookup.
Don’t use when
The answer is an argument or an explanation. A table of an idea’s components communicates less than a paragraph, and chopping reasoning into cells removes the connective tissue that made it reasoning.
Trade-offs
Structure makes an answer scannable and strips the hedging that prose carries naturally, so a table states as fact what a sentence would have qualified. Grids also raise perceived precision without raising accuracy. Rich rendering looks better and complicates copying, since what lands in the clipboard is frequently not what was on screen. Every structured format adds a rendering path that has to survive malformed output from a model only mostly reliable about syntax.
Checklist
- Does the shape of the answer match the shape of the question?
- Can a wide table scroll inside its own container?
- Are header cells marked as headers for assistive technology?
- What happens when a cell contains a pipe, a newline, or a link?
- Is per-cell sourcing available where cells carry facts?
- Can the viewer copy the table as text and as data?
- Is there an export path for anything above a few rows?
- How does a partially streamed table render?
- Can the viewer ask for a different shape without re-asking the question?
- Does the format degrade legibly at a phone width?
Compare
ChatGPT renders markdown tables inline and offers a canvas for output meant to be edited, separating a table read once from one that becomes a working document. Perplexity leans hardest into structured answers, leading with a scannable summary before any prose, which suits a product whose users came for a fact. Claude routes substantial structured output into an artifact where it can be revised across turns rather than regenerated whole. Notion converts the output into native database rows, so a generated table becomes an object with sorting, filtering and permissions instead of formatted text.
Related
Artifact panel is where a large structure goes when the transcript can’t hold it. Code block actions is the same control problem for fenced code. Response collapse handles the length these formats produce. Streaming response determines how a table behaves while it arrives. Citation chip is what makes an individual cell checkable.