Tables, Lists, Headers — When to Use Each
Reviewed by Human · Updated July 14, 2026
Real world
Same groceries, three documents: a shopping list gets you through the store, a recipe gets dinner made, a printed menu sells the dish. Nobody cooks from a shopping list.
AI parallel
Same information from AI, three shapes: a list helps you act, headers help you navigate a long answer, a table helps you compare options. Pick the shape that matches the job the answer has to do.
There's a five-second test that picks the right format almost every time. One question.
✗ Wrong way
Compare Notion, Trello, Asana, ClickUp, and Monday for a small design studio.
You get five paragraphs of prose. Each tool's pricing, strengths, and weaknesses are buried in different sentences, in different orders. To compare pricing you have to hunt through all five paragraphs and hold the numbers in your head. The information is all there — and nearly unusable for the actual decision.
✓ Better way
Compare Notion, Trello, Asana, ClickUp, and Monday for a small design studio. Present the comparison as a table with columns: Tool, Best For, Standout Feature, Weakness, Starting Price. After the table, add one sentence recommending a single tool.
The table forces parallel structure: every tool must answer the same five questions, in the same order, side by side. Your eyes travel down one column to compare prices in two seconds. The closing sentence turns comparison into a decision.
When Should You Use a Table vs a List?
**Table**: rows and columns that force every item to answer the same set of questions — built for comparing options. **Bulleted list**: one point per line, no required order — built for scanning and acting. **Numbered list**: one step per line, order matters — built for procedures. **Headers**: section titles that break a long answer into named parts — built for navigating documents. The framework: - Comparing 2+ things across the same criteria → ask for a **table** and name the columns. - Steps someone will follow → ask for a **numbered list**. - Points someone will scan or check off → ask for a **bulleted list**. - A long answer with distinct parts (report, guide, plan) → ask for **headers** and name the sections. Naming the columns or sections yourself is the power move. 'Use a table' hands the model a shape; 'columns: Tool, Best For, Weakness, Price' hands it your thinking. And if you need the model to mimic a very specific layout, showing it a sample beats describing it — we cover this fully in Few-Shot Learning.
Meeting notes, two ways
✗ Shape left to chance
No format, no sections, no length limit. You'll likely get a paragraph blob where decisions, tasks, and open debates blur together — and the one action item with your name on it hides in sentence four.
✓ Shape chosen on purpose
Named sections mean everyone finds their part instantly. The owner-per-item rule forces accountability into the structure itself. The word cap keeps it a summary instead of a retelling.
Field note
I once sent a client eight paragraphs of vendor research. The reply was one line: 'So which one is cheaper?' The answer was in paragraph five. I re-sent the identical findings as a four-column table and the decision took ten minutes on the next call. Same research, different shape — only one of them looked like an answer.
Your turn
For each task below, choose a format AND write the exact format instruction you'd add to the prompt. Name columns or sections where it helps.
Reflect
For task 1, which columns did you name? Those columns are your real decision criteria — writing the format made you articulate them.
You've finished this module.
Mark it complete to earn your XP and keep your streak alive.
Progress saved locally · Sign up to earn XP