Slow Reading Master: How my visual book summary process has evolved
Based on Zsolt's Visual Personal Knowledge Management's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Start with an author interview and mind map to build context before reading, turning the book into an ongoing conversation.
Briefing
A visual “book on a page” workflow is emerging as a slower, more connection-driven alternative to speed-reading: instead of compressing a book into a quick searchable summary, the process keeps the reader in ongoing dialogue with the text for 6–8 weeks, turning each chapter into a small visual artifact that later compiles into a single page. The payoff is not just recall of key points, but a web of links back to prior notes—so the book becomes part of an evolving knowledge system rather than a one-time read.
The approach draws on Thiago Forte’s progressive summarization—highlight key points, import and refine them, bold the most critical words, write a core summary, then remix it into a new format—but it abandons the method’s more sequential, “mechanical” feel. Long, uninterrupted reading can also become monotonous, and clippings may stop resonating once they’re processed too linearly. To address that, the workflow starts before the first page: it begins with an author interview. By listening to the interview and building a mind map of key points, the reader creates context about the person behind the book, turning the later reading into something closer to a conversation.
From there, the book is processed in chapter-sized chunks inside Obsidian. After each section, highlights and annotations are imported into a dedicated file rather than dumped into one large document. This segmentation preserves context and makes it easier to visualize links across the vault—each chapter becomes a discrete unit with its own trail of connections.
Each imported section then receives a two-sided note: literature notes on one side and a visual summary on the other. As the chapter highlights are reviewed, the reader adds illustrations designed to capture the section’s meaning and to connect it to other ideas already stored in the vault. The linking step uses Nick Milo’s Noma method—think finder, link finder, active thinker (spot differences), and a completion step that forces the “why it matters” conclusion. That Noma process is “supercharged” by an ontology from Excalidraw/Excalibrate and a Compass layer: north points to origins/parent ideas, south to next-level ideas and examples, west to similar ideas, and east to opposing or “supercharging” ideas.
Once all chapters are processed, the chapter visuals are compiled into the final “book on a page” summary. This page functions as a narrative map: what mattered, how ideas connected to earlier notes, and how the reader plans to apply the book. For example, while reading Rick Rubin’s The Creative Act, the workflow highlights how Rubin’s concepts connect to prior notes on creative processes, productivity, innovation, and negotiation tactics. Visual remixing reinforces those connections—reusing elements from earlier illustrations (like productivity and deep work visuals) to build a cohesive, interconnected understanding.
The method’s central claim is practical: it takes more time than fast summarization, but it produces richer engagement—more connections, deeper understanding, and a continuously evolving personal knowledge base—especially when paired with community feedback from the Visual Thinking Workshop cohorts.
Cornell Notes
The workflow replaces speed-focused summarization with a chapter-by-chapter visual process that culminates in a single “book on a page.” It starts with an author interview and mind map to establish context, then reads and processes the book in chunks inside Obsidian, creating a dedicated file per chapter. Each chapter becomes a two-sided note: literature notes plus a visual summary, with links built using Nick Milo’s Noma method and a Compass-based ontology (north origins, south next-level, west similar, east opposing). The final compilation tells a personal story of what mattered, how ideas connect across the vault, and how the reader will apply the book—turning reading into ongoing dialogue with existing knowledge.
Why does the process begin with an author interview instead of starting at page one?
How does chapter-by-chapter segmentation change the way notes are managed in Obsidian?
What does the two-sided note format accomplish during processing?
How does Nick Milo’s Noma method guide linking between ideas?
What role does the Compass layer play in building connections?
How does the final “book on a page” summary differ from a traditional compressed outline?
Review Questions
- What problems with purely sequential summarization does the workflow try to solve, and how does the interview-first step address them?
- Describe how Noma and Compass together shape the linking process. What does each Compass direction imply?
- Why does the workflow create one Obsidian file per chapter, and how does that affect later compilation into a “book on a page” summary?
Key Points
- 1
Start with an author interview and mind map to build context before reading, turning the book into an ongoing conversation.
- 2
Use progressive summarization as a foundation, but replace rigid sequencing with an iterative, chapter-sized workflow.
- 3
Create separate Obsidian files per chapter or section to preserve context and make vault-wide linking easier.
- 4
For every section, maintain a two-sided note: literature notes plus a visual summary that captures meaning and supports later recall.
- 5
Link ideas actively using Nick Milo’s Noma method, including explicit comparison (similarities/differences) and a “why it matters” completion step.
- 6
Add Compass-based spatial context to links: north (origins), south (next-level/examples), west (similar), east (opposing/supercharging).
- 7
Compile all chapter visuals into a single “book on a page” that shows personal significance, cross-note connections, and planned application.