My Exact Learning Process: Uncut Demo (LIVE)
Based on Justin Sung's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Skim first to build an intentionally rough structure from the table of contents, then update it as new information arrives.
Briefing
Product learning sticks when it’s treated as an active, goal-driven thinking process—then organized into a living knowledge network (often via mind maps) that’s constantly pruned and restructured. The core takeaway from this live demo is that long-term retention and real-world usefulness come less from memorizing what’s on the page and more from repeatedly asking, “Why does this matter for the problems I’ll face?” That relevance filter becomes the engine that keeps reading from turning into passive consumption.
The session starts with a deliberate setup: before opening the book, the learner skims the table of contents to build a rough “map” of how major topics might connect. Importantly, accuracy isn’t the goal on the first pass. The point is to reduce cognitive load by giving the brain something to hang new information on. From there, the learner reads quickly—often a blend of normal reading and skimming—because the content is already familiar enough to avoid treating every sentence as brand-new. When something feels unclear or doesn’t fit the relevance frame, the pace slows, the reader pauses, and then returns with a “mini goal” (e.g., understanding a specific sentence or concept) to restore clarity.
A major theme is self-regulation. The learner describes a trained ability to notice when relevance drops—sometimes within a single sentence. At that moment, the response is to stop reading, refresh the goal, and then continue. This prevents the common trap of understanding words while failing to build usable knowledge. The demo also highlights how learning pace can be recursive: skim forward, catch a mismatch, go back, and reprocess. Even when the learner catches up later, the overall time cost is framed as efficient because the mind is doing the work of integrating meaning rather than passively absorbing.
To make knowledge durable, the learner builds structured networks. When new information challenges an existing mental model, the learner compares the old and new structures and updates the map—sometimes by creating a temporary separate mind map to test a connection, then merging it back. Visual hierarchy (including color) is used mainly to make navigation faster, not as a memory trick. Chunking is another retention lever: the learner groups lists into manageable clusters using a “2-4 rule” (no chunk larger than four items) to avoid overwhelming recall.
The session also addresses practical questions from viewers. The learner argues that mind maps shouldn’t become cluttered with obvious material; as understanding grows, earlier “starting maps” can become irrelevant and should be rebuilt with only what still helps organize new information. On using AI for chunking, the stance is skeptical: even if an LLM can generate chunks quickly, the thinking and organization process must happen in the learner’s own head to create real expertise. Overall, the demo presents learning as building a snowball—slower upfront work that makes later details easier to place, compare, and retrieve.
Cornell Notes
The live demo centers on a learning method designed for long-term retention and practical expertise. The learner starts by skimming the table of contents to create a rough, intentionally imperfect “connection map,” then reads with a constant relevance filter: every paragraph must connect to real problems, decisions, or questions the learner will face. When relevance drops or comprehension fails, the process becomes recursive—pause, refresh the goal, and re-read with a mini-goal (often tied to a specific sentence). Knowledge is consolidated by building and updating mind maps through comparison, chunking (using a “2-4 rule”), and occasional micro-retrieval from memory. The approach also includes pruning: when earlier map elements become obvious, they should be removed and the structure rebuilt.
Why does the learner avoid memorization-heavy study, and what replaces it?
What does “goal-directed reading” look like in practice?
How does the learner handle moments when skimming goes too fast?
How do mind maps improve retention beyond simply listing facts?
What’s the learner’s approach to chunking large lists (like product knowledge categories)?
Why does the learner resist using an LLM to chunk everything for them?
Review Questions
- When relevance drops during reading, what exact stop-and-reset cycle does the learner use, and why is it faster than continuing passively?
- How does the learner use comparison between an initial (possibly wrong) mind map and new information to improve retention?
- What does “pruning” a mind map mean over time, and how does it prevent knowledge structures from becoming cluttered or obsolete?
Key Points
- 1
Skim first to build an intentionally rough structure from the table of contents, then update it as new information arrives.
- 2
Read with a constant relevance filter tied to real decisions, questions, and problems—not to understanding sentences for their own sake.
- 3
When comprehension or relevance fails, pause and re-read using a mini-goal (often a specific sentence or concept) to restore clarity.
- 4
Use mind maps as living networks: compare old vs. new models, merge changes, and add lateral connections only when they improve recall and application.
- 5
Chunk large lists into small groups using a “2-4 rule” so the brain can hold and retrieve the structure.
- 6
Consolidate with micro-retrieval from memory to test whether the organized network is actually accessible.
- 7
Prune and rebuild mind maps as knowledge becomes obvious; remove obsolete “starting” structure to prevent clutter and preserve usefulness.