The Format Controller

Why this matters

Output format is a superpower most users ignore. When you need a table for a spreadsheet, a bulleted list for a slide deck, JSON for your code, or a numbered process for documentation — specifying the format doesn't just change how the output looks. It changes what the model focuses on. A 'table' instruction forces comparison. A 'numbered steps' instruction forces sequence. Format shapes content.

How to do it

1. 1

   Choose a task that could reasonably be formatted multiple ways

   Good options: compare two products, explain a process, summarize findings, list options with pros and cons.

2. 2

   Request the output in four different formats using the templates below

   Prose paragraph, bullet list, numbered steps, and a table. Use the same underlying task for all four.

3. 3

   Choose which format best serves the task and explain why

   The "best" format depends on how the output will be used. A table is better for comparison. Steps are better for instructions.

The prompt

[YOUR TASK]

Respond in prose. Write it as flowing paragraphs, no bullets or numbered lists.

[YOUR TASK]

Respond as a bulleted list. Each bullet should be one sentence. No nested bullets. No introduction sentence.

[YOUR TASK]

Respond as numbered steps. Each step should be one clear action. Number every step. Write it as if giving instructions to someone doing this for the first time.

[YOUR TASK]

Respond as a markdown table. Columns should be relevant to the comparison or analysis. Include a header row. Do not include any text outside the table.

Success criteria

• ✓You have the same task output in four different formats
• ✓You chose the best format for your intended use and can explain why
• ✓You understand that format choice depends on how the output will be used

Common mistakes