Before you begin taking Smart Notes
Based on Joshua Duffney's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Avoid converting every consumed item into a permanent note; practice the workflow in stages to prevent burnout.
Briefing
Turning every piece of information into a permanent note is a fast track to burnout. The core recommendation is to slow down and build a Smart Notes workflow in stages—practicing each component on its own—so the process becomes sustainable instead of instantly overwhelming.
A common failure mode is trying to “batch up” everything consumed—tweets, books, online articles, even conversations—into the slip box right away. That approach creates frustration and exhaustion because it treats capture as the goal rather than as the final step of a multi-stage system. Instead, the workflow should start with literature notes taken from a book, then fleeting notes, and only later a separate translation step that converts literature notes into permanent notes.
The suggested on-ramp is deliberately physical and constrained. Read a book (the transcript recommends physical copies, using Digital Minimalism as an example), then write literature notes on index cards. The advice is to handwrite roughly 10–20 notes first, using the physical card’s limits to help the mind internalize the format. After that practice, the notes can be copied into Obsidian for editing and refinement, but the initial reps are meant to build comfort with the structure before scaling up.
Next comes “meta learning,” borrowing a Tim Ferriss framing: break the holistic Smart Notes / “little castle method” workflow into components and learn each in isolation. Fleeting notes can be practiced in Obsidian (which has a mobile app), but the transcript also describes using a pocket notebook for fleeting capture to avoid smartphone distractions and notification temptation. The key is to make capture easy enough to happen, while keeping it focused enough that it doesn’t turn into constant checking.
The workflow should also be practiced in separate time blocks. Take fleeting notes while reading and collecting. Then, in a distinct session, translate literature notes into permanent notes—without trying to run the full loop every time new information is captured. This separation reduces cognitive load and prevents the system from becoming a perpetual task.
Even after months of use, the transcript gives a realistic output target: on an average day, only about three permanent notes are written, sometimes six. When other work projects are active, the ratio drops further. The point is not speed; it’s integration. The system is framed as a relief valve for information overload—capturing the most valuable parts of what’s been consumed and gradually integrating them into personal knowledge.
Finally, the advice is to approach the process with an open mind but not with a sprint mentality. Learn the components first, enjoy the learning, and treat the workflow as a way to deepen skills and knowledge—not as a way to store everything forever.
Cornell Notes
The transcript warns against converting every consumed item into a permanent note, which quickly leads to frustration and burnout. A sustainable approach is to learn the Smart Notes workflow in components: capture fleeting notes, write literature notes from a book, then translate literature notes into permanent notes in a separate time block. The learning phase should use constraints—like handwriting 10–20 index-card notes—before scaling into Obsidian. Output expectations stay modest even after months (often around 3 permanent notes per day), emphasizing integration over speed. The payoff is reduced information overload and better assimilation of the most valuable ideas.
Why does “turn everything into a permanent note” burn people out, and what alternative is offered?
What is the recommended starting exercise for literature notes, and why use physical constraints?
How should fleeting notes be captured without turning them into a distraction loop?
What does “meta learning” mean in this context, and how does it change the learning plan?
What role does time-block separation play in translating literature notes into permanent notes?
What output expectations are given after months of using the system, and what does that imply?
Review Questions
- What are the three main note types mentioned (and their order), and how does the transcript recommend practicing them separately?
- How does the transcript justify using physical index cards or a pocket notebook during the early stages?
- Why does the transcript recommend translating literature notes into permanent notes in a separate time block rather than immediately?
Key Points
- 1
Avoid converting every consumed item into a permanent note; practice the workflow in stages to prevent burnout.
- 2
Begin with literature notes from a single book, using handwritten index cards for an initial set of 10–20 notes to build the habit and format.
- 3
Use constraints to reduce distraction—consider a pocket notebook for fleeting notes instead of a smartphone if notifications interfere.
- 4
Learn Smart Notes components in isolation (fleeting capture, literature note-taking, then translation) before trying to run the full loop continuously.
- 5
Translate literature notes into permanent notes during a dedicated time block, not during the capture phase.
- 6
Expect modest daily output (often around three permanent notes) even after months; prioritize integration over speed.
- 7
Approach the system with patience and enjoyment—sustainable learning beats sprinting into a complete workflow at once.