Progressive Summarization

Progressive Summarization: Distill Notes Without Losing Them.

Name: Mindly
Availability: InStock
Author: Mindly

A layered technique for distilling what you save. Each time you revisit a note, you compress it one layer further: bold the best passages, highlight the best of the bold, then summarize in your own words, so future-you can grasp the note at a glance without losing the detail underneath.

Created by Tiago Forte, Building a Second Brain (2022).

Try in Mindly See all methods

The basics

What Progressive Summarization actually is

Progressive Summarization is a technique for distilling notes in layers. Instead of summarizing a note once and discarding the source, you keep every version: the full captured excerpt at the bottom, a bolded pass above it, a highlighted pass above that, and a short summary in your own words at the top. Each layer compresses the layer beneath it without replacing it, so the same note can be read in five seconds or five minutes depending on what the moment requires. Tiago Forte designed the technique as the engine of the Distill step in his CODE workflow, and it answers a specific problem: notes that are complete are too long to scan, and notes that are scannable have usually thrown away the detail you later need.
The layers are numbered. Layer 1 is the captured excerpt itself: the passages you saved from an article, a book, a paper, or a transcript. Layer 2 is bolding: on a later read, you bold the best passages, the sentences that carry the core of the idea. Layer 3 is highlighting: on another pass, you highlight the best of the bold, the few phrases that could reconstruct the note's value on their own. Layer 4 is an executive summary: a few sentences at the top of the note, written in your own words, stating what the note means and why you kept it. Layer 5, which Forte describes as rare and reserved for the material that matters most, is remixing: taking the distilled ideas and turning them into original work of your own.
The layers are not applied on a schedule. Progressive Summarization is opportunistic by design: you compress a note one layer further each time you actually revisit it for a real reason, and never before. A note you saved and never open again stays at Layer 1 forever, and that is the design working rather than failing. Effort flows toward the notes that keep proving useful, so by the time a note has earned a Layer 4 summary, it has demonstrated its value several times over. Forte's phrase for the rhythm is to add a layer of summarization each time you touch a note.
The goal is a note that future-you can grasp at a glance without losing the underlying detail. Forte frames the technique as a balance between discoverability and depth. A raw capture has full depth and no discoverability; a bare one-line summary has full discoverability and no depth. The layered note has both, because each layer is a doorway into the one below it. You scan the summary, drop to the highlights if you need more, and descend to the full text only when the details matter. Nothing is lost, and almost nothing needs to be re-read.
Forte first published the technique as a series of essays on the Forte Labs blog and later folded it into his 2022 book "Building a Second Brain", where it anchors the Distill step of CODE. It assumes a capture habit is already feeding you material worth distilling and an organization scheme (Forte pairs it with PARA) is keeping that material findable. Progressive Summarization is the middle of the pipeline: the step that turns saved material into material you can actually use at the speed of writing.

Who it is for

Who Progressive Summarization is for

Heavy readers with a highlight problem

If your Kindle highlights export has five hundred entries and you have reread none of them, you have Layer 1 material with no layers above it. Progressive Summarization is the repair: you do not need to process the backlog in one heroic weekend. You bold one note the next time a project sends you back to it, and let the useful fraction of the library distill itself over months. The highlights that never get touched again were, by revealed preference, not the ones that mattered, and the technique never asks you to spend time on them.

Researchers and students returning to sources

Academic work has a long gap between reading a source and citing it. Six months after you read the paper, you remember that it mattered but not why. A progressively summarized note closes that gap: the executive summary tells you why you kept it, the highlights point to the passages that earned the citation, and the full excerpt sits underneath for verification. The second literature pass, the one that happens under deadline, becomes scanning instead of re-reading.

Knowledge workers who write from saved material

Memos, decks, proposals, and decision documents are all assembled from things you read weeks or months earlier. The bottleneck is never the writing itself; it is reconstructing what the source material said. A library of layered notes turns that reconstruction into a scan. You pull the summaries, descend into highlights where the argument needs precision, and the draft comes together from material that is already half-written in your own words.

Anyone whose notes are write-only

The most common note-taking failure is a library that only ever gets written to. Saving feels productive, so the library grows, but nothing ever comes back out. Progressive Summarization is a practice built around the return visit: it gives you something specific and cheap to do each time you open an old note, and each visit makes the next one faster. The library stops being an archive you feel vaguely guilty about and starts being a working surface that improves with use.

The core principles

What makes it different from just writing summaries

Compression without deletion
A conventional summary replaces the source; Progressive Summarization stacks compressions on top of it. This matters because summaries are lossy in ways you cannot predict at summary time. The detail that seems disposable today is the detail next year's project turns out to hinge on. Keeping every layer means the note can always be re-expanded: when a summary reads wrong or thin, the evidence for checking it is directly underneath, in the same note, rather than in a source you would have to find again.
Opportunistic, not scheduled
There is no weekly summarization chore in the method as Forte designed it. Compression happens at the moment of genuine contact: a project sends you back to a note, and while you are there, you add a layer. This keeps the cost of the practice near zero and, more importantly, aims the effort well. Time spent distilling tracks demonstrated usefulness instead of guesses made at capture time, which is when you know the least about what will matter.
Small fractions at every layer
Each layer should be a small fraction of the layer beneath it. Bold a fifth of the note, not half of it; highlight a fraction of the bold. The discipline feels stingy, but generosity is the failure mode: a Layer 2 that keeps most of Layer 1 adds work without adding scannability. The question at each pass is not "is this good" but "is this the best of what is here". Most good material does not survive the cut, and the layer is useful precisely because it is ruthless.
Designed for future-you
The reader of a progressively summarized note is you, months or years later, mid-task, short on time and missing the context you had when you saved it. Every choice in the technique serves that reader: the summary at the top because they are scanning, your own words because the source's words will have lost their context, the layers below because they might need to verify. Writing for that reader is a different act from writing for your present self, and the difference is most of what the technique teaches.

Common mistakes

Where Progressive Summarization goes wrong (and the fix)

Summarizing at capture time
Newcomers distill every note the moment they save it, trying to arrive at a finished library. This front-loads hours of labor onto notes that mostly will never be opened again, and it is the fastest route to abandoning the practice. The fix: capture stays cheap and unprocessed. Layers are added on revisits, when a note has proven it deserves the attention.
Bolding half the note
When everything feels important, the bold pass keeps most of the text, and the layer becomes decoration rather than compression. A note that is 60 percent bold reads no faster than the original. The fix: treat each layer as a strict budget, a small fraction of the layer below. If you cannot choose, you are not ready to distill this note, and it can wait for a visit when you can.
Waiting for revisits that never come
The honest critique of the method is that it presumes you return to your notes, and most people mostly do not. A library where nothing is ever reopened never earns a single layer, and the technique quietly does nothing. The fix: tie distillation to real work by starting every project with a search of your own library, or use a tool that generates the first summary layer on save so the glanceable version exists before any revisit happens.
Treating bold and highlight as the thinking
Layers 2 and 3 are selection, and selection is manual labor with only modest thinking in it. The real value of the method concentrates in Layer 4, the summary in your own words, because rewriting is where understanding happens. A library that is thoroughly bolded but has no own-words summaries has been decorated, not distilled. The fix: for any note that matters, push through to the executive summary. The layers below it are scaffolding for that sentence or two, not the product.

How Mindly fits

How to apply Progressive Summarization in Mindly

Mindly changes the economics of Progressive Summarization in one specific way: the at-a-glance layer exists from day one. Every long item you save (an article, a PDF, a transcript, a long note) gets an AI-generated summary automatically on save, before you have revisited it even once. This addresses the technique's honest weakness head on. Progressive Summarization pays off only when notes get revisited, and most saved notes never are, which means the layers most people would benefit from are exactly the layers they never get around to building. With the first compression pass automatic, the glanceable version of every note exists whether or not you come back, and when you do come back, you land on a summary instead of a wall of raw text. The part Mindly does not do for you is Layer 4 in the sense Forte means it. An AI summary is a faithful compression of what the source said; an executive summary in your own words is a record of what the material means to you, and that distillation is thinking no tool can do on your behalf. What Mindly changes is where that thinking starts: you edit a summary that already exists rather than staring down the full capture, the original text sits underneath for verification, and semantic search keeps the related items you saved within reach while you work. Layer 5, remixing distilled material into original work, happens in the Notes Editor, with your summaries and highlights one reference away from the draft. If you prefer to run the technique fully by hand, it works in any tool that supports bold and highlight, and Forte's original essays remain the best guide to the manual craft. The difference is the order of operations. Forte's version earns the summary through revisits that most libraries never receive. Mindly starts with the summary, so the revisits have somewhere to land and the own-words layer has raw material waiting.

Common questions

Progressive Summarization, answered

Who created Progressive Summarization?

Tiago Forte, the productivity teacher and author behind PARA and CODE. He first published the technique as a series of essays on the Forte Labs blog and formalized it in his 2022 book "Building a Second Brain", where it serves as the core technique of the Distill step in the CODE workflow.

What are the five layers of Progressive Summarization?

Layer 1 is the captured excerpt: the passages you saved from the source. Layer 2 bolds the best passages. Layer 3 highlights the best of the bold. Layer 4 is an executive summary at the top of the note, written in your own words. Layer 5, which is rare, remixes the distilled material into original work of your own. Every layer is kept, so the note can be read at any depth.

How much should I bold or highlight?

A small fraction of the layer below. If the bold pass keeps most of the note, it adds no scannability and the layer has failed at its one job. Forte's guidance is that less is more: each layer should feel slightly too strict. The test is whether the layer alone lets you reconstruct why the note mattered.

When am I supposed to summarize a note?

Opportunistically, not on a schedule. You add a layer each time you actually revisit a note for a real reason, and never before. Most notes stay at Layer 1 forever, which is by design: distillation effort flows toward the notes that keep proving useful, rather than being spent up front on material that may never matter.

Do AI summaries replace Progressive Summarization?

They replace the waiting, not the thinking. An AI summary is a faithful first compression of what a source said, which covers the ground the bold and highlight layers cover. The executive summary in your own words, where you state what the material means to you, is still thinking only you can do. Mindly's approach is to generate the first layer on save and leave the own-words layer to you, with the raw material in reach.

How does Progressive Summarization relate to PARA and CODE?

All three come from Tiago Forte's Building a Second Brain. CODE is the workflow (Capture, Organize, Distill, Express). PARA is the organization scheme inside the Organize step. Progressive Summarization is the technique inside the Distill step. They are designed to run together, but the summarization technique works on its own in any note system.

Is Progressive Summarization worth it if I never reread my notes?

Honestly, no, not in its manual form. The technique only pays when notes are revisited, because revisits are when layers get added and when layers get used. If you never return to your notes, fix retrieval first: start projects by searching your own library, or use a tool where the summary layer is generated automatically, so the at-a-glance version exists without depending on a habit you do not have yet.

Other methods

Start with the summary already written.

Download Mindly, save one long article, and see the at-a-glance layer appear on save. The distillation in your own words stays yours.

Download free See pricing

Progressive Summarization: Distill Notes Without Losing Them.

Created by Tiago Forte, Building a Second Brain (2022).

How to apply Progressive Summarization in Mindly

Progressive Summarization: Distill Notes Without Losing Them.

Heavy readers with a highlight problem

Researchers and students returning to sources

Knowledge workers who write from saved material

Anyone whose notes are write-only

Compression without deletion

Opportunistic, not scheduled

Small fractions at every layer

Designed for future-you

Summarizing at capture time

Bolding half the note

Waiting for revisits that never come

Treating bold and highlight as the thinking

How to apply Progressive Summarization in Mindly

Start with the summary already written.

Progressive Summarization: Distill Notes Without Losing Them.

Heavy readers with a highlight problem

Researchers and students returning to sources

Knowledge workers who write from saved material

Anyone whose notes are write-only

Compression without deletion

Opportunistic, not scheduled

Small fractions at every layer

Designed for future-you

Summarizing at capture time

Bolding half the note

Waiting for revisits that never come

Treating bold and highlight as the thinking

How to apply Progressive Summarization in Mindly

Start with the summary already written.