Knowledge Concepts
What is progressive summarization? A clear explanation of Tiago Forte's note-distillation technique, how to apply it, and how it fits into a second brain
Progressive summarization is a note-taking technique developed by Tiago Forte where you distill content through multiple passes over time — highlighting key sections on first read, bolding the most important highlights on review, and writing a short summary in your own words on a third pass — so notes become more compressed and actionable each time you engage with them, without losing access to the original.
The technique is the central distillation method in Forte's Building a Second Brain framework and the "D" (Distill) step in the CODE methodology.
Tiago Forte introduced progressive summarization in a 2017 blog post and elaborated it in Building a Second Brain (2022). The technique was Forte's solution to a specific problem he kept encountering: people would capture lots of notes but find them hard to use because the notes were either too long (full article dumps) or too short (just a URL).
The insight: notes don't need to be optimized at capture time. You don't know what will matter most until you return to the note with a specific purpose. Progressive summarization defers the compression work to future reading sessions — and does it incrementally, so you're only doing the work that's warranted by how often and how usefully you return to a note.
The name references a technical concept from data compression: progressive rendering (displaying an image at low resolution first, then adding detail). The note equivalent: capturing broadly first, then progressively refining toward the essence.
The technique has four layers, applied across multiple reading sessions:
Layer 0: Capture Save the original content — the article, chapter, note, or transcript — in your note-taking system. This is your raw material. Most notes stay at Layer 0 forever, and that's fine.
Layer 1: Bold When you return to a note (usually while working on something that uses this content), read it quickly and bold the passages that seem most important or useful. Don't overthink this — bold what stands out in this reading, from this perspective. The bolded sections will be 20–30% of the original.
Layer 2: Highlight If you return to the note again — or when you're about to use it for something specific — read only the bolded sections and highlight the ones that now seem most essential. The highlighted sections will be 10–15% of the original, and the truly important ideas.
Layer 3: Executive Summary At the top of the note, write 2–4 sentences in your own words summarizing what this note is about and why it matters. This is optional — only for notes you return to repeatedly or find highly valuable. It's the note's "executive summary" that you read before deciding whether to dive into the body.
Layer 4: Remix Optional. When you produce output from the note — a blog post, a presentation, a report — you're remixing the note's content into something new. This is the step where captured knowledge becomes expressed value.
A content strategist saves an article about "information architecture for landing pages."
Layer 0: The article (2,400 words) goes into her note-taking system via web clipper.
Three weeks later, she's working on a landing page project.
Layer 1: She opens the note and reads quickly. She bolds 8 paragraphs: the section on hierarchy, two specific examples of fold placement, the research finding about attention patterns, a checklist, and one relevant quote.
Two months later, she's redesigning a different landing page.
Layer 2: She reads only the bolded sections (now maybe 600 words). She highlights the hierarchy section and the checklist — these are the most immediately useful.
Layer 3: She writes at the top: "Landing page IA: above-fold hierarchy matters more than copy. The 3-section fold structure (problem → solution → proof) outperforms alternatives. Use the attached checklist for review."
A year later: She opens the note. Reads the executive summary. Immediately knows what the note contains and whether it's relevant. Reads only the highlighted sections to refresh. Uses the checklist. Done in 3 minutes.
Without progressive summarization: she would either need to re-read 2,400 words to find the checklist, or never find the note at all because it was never organized.
| Layer | When to apply |
|---|---|
| Layer 0 | Every time you save anything |
| Layer 1 | When you return to a note for a purpose |
| Layer 2 | When you return to a bolded note again |
| Layer 3 | Only for highly valuable notes you use repeatedly |
| Layer 4 | When producing output that draws on the note |
The key principle: don't try to apply all layers at capture time. You don't know yet which notes will be worth the effort of deeper distillation. The progressive structure lets the notes that prove their value get more work invested over time.
"I should bold everything that seems interesting." Over-bolding defeats the purpose. If 80% of the note is bolded, the highlighting layer has no work to do. Bold conservatively — only what's genuinely useful for a purpose you can articulate.
"I need to create an executive summary for every note." Layer 3 is for notes that have proven their value through repeated use. Most notes should never get an executive summary — they'll stay at Layer 0 or Layer 1 forever, and that's fine. The summarization work is proportional to the note's demonstrated value.
"Progressive summarization replaces Zettelkasten." These are complementary, not competing. Zettelkasten produces permanent atomic notes. Progressive summarization distills source material (literature notes, articles, transcripts) that feeds Zettelkasten. Many PKM practitioners use progressive summarization to process sources and Zettelkasten to develop their own thinking.
"This is too complicated to start." Start with Layer 1 only. When you next open a saved article, bold the important parts before you close it. That's progressive summarization. Layers 2 and 3 are optional elaborations.
Step 1: Save without filtering. At capture time, save freely. Don't try to only save "the best" content. Your future self will filter. This keeps capture friction low.
Step 2: Only distill when you have a reason. Don't schedule distillation sessions. Bold a note when you open it for a specific purpose. The work is warranted by use, not by the passage of time.
Step 3: Bold generously, highlight sparingly. When bolding (Layer 1), include everything that might matter. When highlighting (Layer 2), be ruthless — only what's essential.
Step 4: Use the executive summary as your note's interface. A note with a good Layer 3 summary becomes a decision point in 30 seconds: read the summary, decide whether to dive in. No summary → re-read to assess.
Step 5: Produce output. Progressive summarization's value compounds when your notes feed output. A note that's been progressively summarized is fast to use in a writing session, a presentation prep, or a decision memo.
WebSnips handles the upstream portion of the progressive summarization workflow:
WebSnips doesn't perform progressive summarization automatically — the distillation work is deliberate and human. But it provides the research library that makes the distillation worthwhile.
What tools support progressive summarization? Any tool that supports formatting within notes: Notion (bold and highlight with native formatting), Obsidian (bold in markdown, custom highlights), Readwise (native highlight layers), Evernote (formatting tools). Tiago Forte built the method for Evernote originally; it now works in any note tool that supports text formatting.
Can I use progressive summarization with highlights I've already made? Yes — if you have Readwise syncing highlights from Kindle or web articles, you can apply Layer 2 thinking to your existing highlights: which ones are still important? Highlight those.
How is progressive summarization different from just taking good notes? Traditional note-taking optimizes at capture time: you decide what matters while reading. Progressive summarization defers that decision to multiple future reading sessions. This is better because context changes — what matters in your note depends on what you're working on when you read it, not what you thought mattered when you saved it.
Is progressive summarization still relevant with AI summarization tools? AI summarization (like NotebookLM, Claude with document uploads, or WebSnips's Creator Studio) can produce Layer 3 summaries quickly. This doesn't make progressive summarization irrelevant — the earlier layers (bolding and highlighting) help you develop your own understanding, not just consume an AI summary. But for initial triage of a large research library, AI-assisted summarization can be a faster starting point.
Progressive summarization is Tiago Forte's technique for distilling notes across multiple reading passes — bolding key sections, highlighting the most essential, writing a brief executive summary — so that notes become more useful each time you return to them, without losing the underlying content.
The technique is designed for the reality of knowledge work: you can't know at capture time what will matter most. You discover what's valuable through repeated use. Progressive summarization makes that discovery process systematic.
Start with one layer: the next time you open a saved article, bold the important parts before you close it. Build from there.
Related reading: The Ultimate Guide to Web Clipping.
More WebSnips articles that pair well with this topic.
What is citation management? A clear explanation for researchers and academics — how citation managers work, the best tools, and how to avoid the most
What is tacit knowledge? A clear explanation for team leads and ops people — what tacit knowledge is, why it's the hardest knowledge to transfer, and
What is a commonplace book? A clear explanation of the centuries-old knowledge collection practice, famous examples, and how to build a modern digital
What is a knowledge graph? A clear explanation of the technology, how Google's knowledge graph works, and what personal knowledge graphs in tools like
What is a Map of Content (MOC)? A clear explanation of Nick Milo's PKM concept, how MOCs organize linked notes without folders, and how to build one in
What is a personal wiki? A clear explanation of the concept, how personal wikis differ from other note-taking systems, and the best tools for building one