How to Reflect on an Article, Book, Video or Podcast

A summary tells you what the piece said. A reflection tells you what you now think because of it. Both have their place, but only the second belongs to you and helps you retrieve, reuse and share the idea later. If you only have a couple of minutes, skip the summary and write the reflection.

Three honest sentences usually beats three hundred words you never come back to. Aim for something a future version of you could read in ten seconds and understand. Long reflections are useful when the material genuinely deserves it, not because volume feels thorough.

Pick two or three per piece. You do not need all six every time.

1. What is the main idea, in one sentence?
2. What did I agree with, and why?
3. What did I disagree with, or find uncertain?
4. Where does this connect to what I already know or do?
5. What could I do differently because of it?
6. Who else might find this useful, and why?

The same framework works everywhere, but different formats reward different prompts.

• • Articles — prompts 1, 2 and 4 usually give you the most. Aim for one sentence per prompt.
• • Books — reflect chapter-by-chapter rather than at the end. One strong idea per chapter is often more useful than a whole-book summary.
• • Videos — capture the timestamp of the moment that changed your mind, plus your reaction in one line.
• • Podcasts — write your reflection while walking or before starting the next episode. What was the one thing you would repeat to a friend?

Article — a piece on decision-making: Main idea: irreversible decisions deserve slower thinking. Where it connects: our hiring loop treats every offer the same. What I would do differently: flag the two irreversible steps and add a second reviewer only there.

Book — a chapter on habits: Main idea: environment usually beats willpower. Where I disagreed: the author underplays context that resets weekly. Action: move the running shoes to the front door on Sunday nights.

Podcast — an interview with a product designer: One idea worth passing on: shipping ugly-but-usable earlier changes what users tell you. Who might care: two colleagues who are stuck polishing a prototype nobody has tried.

Copy this and keep it near where you write your reflections.

• • Writing a summary and calling it a reflection. If it could have been generated by anyone who read the piece, it is not yours yet.
• • Hedging every sentence. You are writing for future-you, not for an audience.
• • Waiting for the perfect reflection. One imperfect line, saved next to the source, beats nothing.

When you have written a few reflections you like, they become one of the most useful ways to rediscover ideas you saved previously.