Output Formats That Work.
Tell AI what shape the answer should take and you'll never get a wall of useless text again.
After this lesson you'll know
- The 8 most useful output formats and when to use each
- How to specify format without being rigid
- The "show me the structure" technique
- How to get AI to output in formats you can paste directly into other tools
The Problem
Why AI gives you walls of text.
When you don't specify a format, AI defaults to flowing paragraphs. It's like asking someone a question and getting a 10-minute monologue when you needed a yes or no.
The fix is simple: tell the AI what shape the answer should take. Not just "give me a list" — but specifically how you want the information organized.
The Formats
8 formats you'll use constantly.
Deep Dive
Format examples you can copy right now.
Knowing the formats is step one. Seeing them in action with real prompts is where the skill locks in. Here are four of the most useful formats with exact prompts and what they produce.
Format Example 1 — Markdown Table
[PROMPT]:
Compare Notion, Trello, and Asana for a 10-person
marketing team. Format as a markdown table with columns:
Tool, Best For, Price/User/Mo, Biggest Limitation,
Learning Curve (1-5). Add a recommendation row at the bottom.
[WHY THIS WORKS]:
- The table structure is explicit — AI knows exact columns
- "Recommendation row" forces a conclusion, not just data
- "10-person marketing team" gives audience context
- You can paste this table directly into Slack or a docFormat Example 2 — JSON for Automation
[PROMPT]:
Extract the action items from these meeting notes and
return them as a JSON array. Each object should have keys:
"task" (string), "owner" (string), "deadline" (ISO date
string or null), "priority" (1-5 integer).
Meeting notes:
[paste your notes here]
[WHY THIS WORKS]:
- Specifying data types (string, ISO date, integer) prevents
inconsistent formatting
- The JSON can be piped into Zapier, Make, or your own code
- "or null" handles cases where no deadline was mentionedFormat Example 3 — Executive Summary
[PROMPT]:
Summarize this 20-page report for my CEO. Format:
1. BOTTOM LINE (1 sentence — the single most important takeaway)
2. THREE KEY FINDINGS (bullet points, one sentence each)
3. RECOMMENDED ACTION (what to do next, in 2 sentences)
4. RISK IF WE DO NOTHING (1 sentence)
Total length: under 150 words. No jargon.
[WHY THIS WORKS]:
- "Bottom line first" mirrors how executives read
- Numbered sections with word limits prevent rambling
- "No jargon" forces plain language
- "Risk if we do nothing" adds urgency without you asking for itFormat Example 4 — Step-by-Step with Checkpoints
[PROMPT]:
Write a step-by-step guide for setting up Google Analytics
on a new website. Audience: a small business owner who is
not technical.
For each step:
- Number it
- Give the action in one sentence
- Add a "You'll know it worked when..." checkpoint
- Include a common mistake to avoid
Keep it under 10 steps. Use plain language — no developer jargon.
[WHY THIS WORKS]:
- "You'll know it worked when" gives the reader confidence
- "Common mistake" prevents frustration before it happens
- "Under 10 steps" prevents the AI from over-breaking the task
- "No developer jargon" matches the non-technical audienceThis lesson is for Pro members
Unlock all 520+ lessons across 52 courses with Academy Pro.
Already a member? Sign in to access your lessons.