Big Question Summary¶
Stage: Package → Descriptions
Score: 4
Evidence: practitioner observation
Pattern¶
Big Question → Conversation Summary → Key Takeaways → Links
What It Is¶
A description that opens with the central question driving the episode, summarizes the conversation arc, and lists the key takeaways.
Why It Works¶
Leading with a big question creates intellectual curiosity. Practitioners who think about this question already will recognize the episode as relevant to their work.
Example¶
What happens when your owned media strategy outlasts your marketing team? This episode explores the tension between building a durable content engine and the reality of team turnover, budget shifts, and platform changes. Key takeaways: why systemization beats talent, how to document your production workflow, and what "content resilience" actually means. Links and resources at riggg.com/episodes.
Quality Bar¶
- Question must be genuinely interesting, not rhetorical
- Summary should cover the arc, not just the topic
- Key takeaways should be scannable
- Include links to resources mentioned
When Not To Use¶
Avoid for tactical episodes where the listener wants "how to do X" — not "what should we think about."
Shows That Use This Pattern¶
| Show | Why | Link |
|---|---|---|
| Lex Fridman Podcast | Opens with a deep question, summarizes the multi-hour conversation arc | Apple Podcasts |
| Sean Carroll's Mindscape | Frames each episode around a core intellectual question | Apple Podcasts |
| The Knowledge Project | Structures descriptions around the central question explored with each guest | Apple Podcasts |
Prompt Template¶
Copy and customize this prompt to generate this pattern:
Write an episode description using the Big Question Summary pattern.
Format: Big Question → Conversation Summary → Key Takeaways → Links
Context:
- Central question: [the big question driving the episode]
- Conversation arc: [how did the discussion unfold]
- Key takeaways (3-5): [main insights]
- Resources/links: [any URLs or references mentioned]
Requirements:
- Question must be genuinely interesting, not rhetorical
- Summary should cover the arc, not just the topic
- Key takeaways should be scannable
- Under 300 words
Replace the bracketed placeholders with your specific details. The more context you provide about your audience, guest, and episode content, the better the output.