Progressive Summarization: The Layered Note-Taking Method

You capture an article.

It's 3,000 words.

You skim it once and save it.

Six months later you need that article.

But you forgot what it was about.

You read the entire 3,000 words again.

You waste 45 minutes to find one useful sentence.

This is why progressive summarization exists.

Progressive summarization is the technique of layering highlights on notes over time until only the most essential ideas remain visible.

Each layer removes noise.

Each pass makes the note more distilled and actionable.

After three layers, a 3,000-word article becomes a 200-word actionable summary.

---

What Progressive Summarization Is (and Isn't)

What It Is

A multi-pass highlighting technique where you:

1. Pass 1: Highlight key sentences (yellow)
2. Pass 2: Bold the most important parts (bold text)
3. Pass 3: Extract core ideas into a summary (30-word summary)
4. Pass 4: Link to related ideas (optional, for connections)

Each pass removes noise. Each pass makes the note smaller and more useful.

What It Isn't

Not one-pass highlighting. One pass leaves too much highlighted. The whole note is yellow. No distillation happens.

Not summarization at capture time. You don't understand the material yet. Summarizing too early loses nuance.

Not mandatory complexity. Start with one or two layers. Add more if needed.

---

The Problem Progressive Summarization Solves

The Capture Paradox

You save too much. You remember too little.

Without progressive summarization:

• You capture an article (full text)
• You review it once
• You forget what it said
• Next time you need it, you reread entire article

With progressive summarization:

• You capture an article (full text)
• You highlight key parts (first pass)
• You bold the most important (second pass)
• You write 30-word summary (third pass)
• Next time you need it, you read 30-word summary instead of 3,000-word article

Time saved: 90% of rereading time

---

The Four Layers of Progressive Summarization

Layer 1: Highlight (Yellow)

When: During first review (days after capture)

How: Mark sentences that stand out to you.

What to highlight:

• Key claims
• Surprising facts
• Relevant research
• Quotable passages
• Contradictions

Volume: Highlight 10–30% of article (not everything)

Example:

Original text: "Machine learning models trained on historical data reproduce systemic biases from that data. Smith et al. found that criminal risk assessment algorithms predicted 20-30% higher risk for minority defendants compared to majority defendants, even when controlling for crime type and severity. This is not a quirk—it's a predictable outcome of training data bias."

Highlighted version: "Machine learning models trained on historical data reproduce systemic biases from that data. Smith et al. found that criminal risk assessment algorithms predicted 20-30% higher risk for minority defendants compared to majority defendants, even when controlling for crime type and severity. This is not a quirk—it's a predictable outcome of training data bias."

Layer 2: Bold (Most Important)

When: On second review (1–2 weeks after capture)

How: From your highlights, bold the most important ones.

What to bold:

• The most surprising facts
• The strongest evidence
• The core argument
• The actionable insights

Volume: Bold 5–10% of highlights (not all highlights)

Example:

From previous highlights, bold the most important:

"Machine learning models trained on historical data reproduce systemic biases from that data. Smith et al. found that criminal risk assessment algorithms predicted 20-30% higher risk for minority defendants compared to majority defendants, even when controlling for crime type and severity."

The bold part is the core claim with evidence.

Layer 3: Executive Summary (30–50 Words)

When: On third review (1–2 weeks after bolding)

How: Write a short summary capturing the article's core idea.

Template:

"This article argues that [main claim]. Evidence: [key fact]. Implication: [why it matters]. Key source: [who to cite]."

Example:

"This article shows that AI systems reproduce racial biases from training data. Smith et al.'s evidence: criminal risk assessment algorithms show 20-30% higher error rates for minority defendants despite controlling for crime factors. Implication: without auditing, AI amplifies historical injustice. Must cite Smith et al. (2023)."

(~50 words)

Layer 4: Linked Ideas (Optional)

When: During weekly review (optional, only if connection matters)

How: Link this note to related ideas in your system.

Example:

• Links to other articles on AI bias
• Links to other articles on criminal justice
• Links to your decision notes if relevant to a project

Volume: 1–3 links per note (not all possible connections)

---

How Progressive Summarization Fits Into The Second Brain

The CODE Framework

Recall the CODE framework from Building a Second Brain:

1. Capture: Save the full article
2. Organize: Tag it and put in project/area
3. Distill: Progressive summarization (layers 1–3)
4. Express: Use the summary to write articles/make decisions

Progressive summarization is the Distill stage.

When to Apply Each Layer

Layer 1 (Highlight): During first review

• You're reading the article for the first time with fresh eyes
• You understand the material
• Highlighting is natural — mark what stands out

Layer 2 (Bold): During second review (1–2 weeks later)

• You've had time to think about the material
• You know what's important in context
• Bolding refines highlights

Layer 3 (Summary): During third review (1–2 weeks later)

• You're ready to use this idea
• The summary becomes your go-to reference
• You won't reread the whole article

Layer 4 (Links): During weekly review (optional)

• You're organizing your system
• You see connections to other ideas
• Links create a network of ideas

---

Implementing Progressive Summarization in Practice

Setup (Choose Your Tool)

Notion:

• Highlight using color blocks or toggle
• Bold text directly
• Summary goes in a "Key Takeaways" field

Obsidian:

• Highlight using ==colored text==
• Bold text directly
• Summary goes at top of note

Roam Research:

• Highlight and bold natively supported
• Summary can be separate block or linked to note

All tools work. Choose based on your second brain platform.

The Three-Week Timeline

Week 1 (Capture):

• Save article with full text
• Tag it
• Put in relevant project/area
• (Don't highlight yet)

Week 2 (Layer 1 – Highlight):

• Read article for first time
• Highlight key sentences (yellow)
• Save

Week 3 (Layer 2–3 – Bold + Summarize):

• Review highlights
• Bold most important ones
• Write 30–50 word summary
• Done

Weekly review (Layer 4 – Link):

• During weekly review, if relevant to current project, add 1–2 links

Common Implementation Mistakes

Mistake 1: Highlighting too much (first pass)

You highlight 50% of article. No distillation.

Fix: Max 20% on first pass. Let importance emerge.

Mistake 2: Delaying layers

You capture and immediately bold and summarize.

You don't understand the material yet.

Summaries are wrong.

Fix: Wait. Let time pass between layers. Understanding deepens.

Mistake 3: Linking everything

You create links to every vaguely related note.

System becomes noise.

Fix: Link only when connection is strong. 1–3 links per note, not 10.

Mistake 4: Never revisiting

You create summary but never use it.

System becomes archive.

Fix: Reference your summaries when writing. The value emerges when you use them.

---

Why Progressive Summarization Works

Why Multiple Passes Beat Single Summarization

Single pass (immediately after reading):

• You don't know what matters yet
• You highlight 50% (noise)
• You misunderstand nuance

Multiple passes (over 2–3 weeks):

• Time creates clarity
• You understand what's truly important
• Each pass refines understanding

Psychology: Sleep and time between passes help consolidation. Each pass is an active retrieval that strengthens memory.

The Exponential Return on Time

Reading full article: 30–45 minutes

Next time you need it:

• With progressive summarization: Read 50-word summary = 1 minute
• Without: Reread full article = 30–45 minutes

After 10 references to same article:

• With: 10 minutes total rereading time
• Without: 300–450 minutes total rereading time

Time saved: 290+ minutes = ~5 hours per article

Multiply that by 100 articles in your system. Progressive summarization saves you hundreds of hours.

---

Where Progressive Summarization Fits Into Workflows

Workflow 1: Research to Writing

1. Capture article (full text)
2. Review and highlight (week 1)
3. Bold and summarize (week 2)
4. When writing article on topic: Review summaries, not full articles
5. Write faster (you have distilled information)

Workflow 2: Learning and Retention

1. Capture course notes
2. Highlight key concepts (first review)
3. Bold connections to other learning (second review)
4. Summarize (third review)
5. Use summaries for studying/recall

Workflow 3: Decision-Making

1. Capture relevant information (research, past decisions, expert advice)
2. Highlight key considerations
3. Bold critical factors
4. Summarize core decision framework
5. Use summary when making similar decisions

---

Realistic Expectations

Time Investment

Per article:

• Capture: 2–5 minutes
• Highlight: 5–10 minutes (wait 1 week)
• Bold + Summary: 5–10 minutes (wait 1 week)
• Total: 12–25 minutes per article (spread over 3 weeks)

For 100 articles per year: 20–40 hours total

Return: Hundreds of hours saved rereading and researching.

When You'll See Value

Week 1: System feels like extra work

Week 4: You reference first summary (instead of rereading full article). Value emerges.

Month 3: You're synthesizing ideas across 20+ summaries. Connections become clear.

Month 6: Your system is compounding. Writing is 2x faster.

---

Common Questions

Q: Do I have to do all 4 layers?

A: No. Start with layers 1–3 (highlight, bold, summarize). Layer 4 (linking) is optional and only useful once you have 20+ notes.

Q: What if I don't understand the article on first read?

A: Reread it. Highlight is only helpful if you understand the material. If first read is confusing, spend more time on comprehension before highlighting.

Q: Can I summarize immediately after capturing?

A: You can, but it's less effective. Your understanding improves over time. Summaries made 2 weeks later are better than summaries made immediately.

Q: How long should the executive summary be?

A: 30–50 words is ideal. Long enough to capture meaning, short enough to scan in 30 seconds.

Q: Does this work for all types of content?

A: Best for: articles, books, research papers, educational content.

Okay for: videos (requires taking notes first), podcasts (requires transcripts or notes).

Not ideal for: social media posts, news headlines.

---

Conclusion

Progressive summarization turns captured content into distilled, actionable knowledge.

The layers:

1. Highlight: First pass (what stands out)
2. Bold: Second pass (what matters most)
3. Summary: Third pass (30-word essence)
4. Link: Weekly (optional connections)

The benefit:

• You revisit your notes in 1 minute instead of 30 minutes
• Understanding deepens with each pass
• Ideas compound over time

Start this week:

1. Capture one interesting article
2. Wait 1 week
3. Highlight key sentences (10–20% of text)
4. Wait 1 week
5. Bold most important (5–10% of highlights)
6. Write 30-word summary
7. Reference that summary next time you need it

After one month, you'll have 4 deeply distilled summaries. After one year, 50. Each one saves you 30 minutes of rereading.

For more on PKM, see Building a Second Brain. For notes, check Fleeting to Permanent Notes.

Summarize progressively. Think efficiently.