Study Systems
Build a personal knowledge base that does not become homework
Most note systems fail because they optimize for storage. A useful knowledge base optimizes for retrieval.
A personal knowledge base should reduce the number of times you rediscover the same idea. It should not become a second inbox, a scrapbook, or a place where interesting links go to die. The smaller system usually wins.
Keep one capture inbox
Put every raw note, link, quote, and thought in one place first. Do not sort while capturing. Sorting is expensive, and expensive systems fail under pressure. The only capture requirement is that the note includes enough context for future you to understand why it mattered.
Convert raw notes into atomic notes
Once or twice a week, turn the few useful captures into atomic notes. One note should contain one idea, one claim, or one reusable procedure. Give it a plain-language title, write a two-sentence summary, and link it to one related note.
Use maps for active projects
Do not build a huge taxonomy. Instead, create temporary maps for active classes, projects, or research questions. A map is a short page that links to the notes you actually need right now. When the project ends, archive the map and keep the durable notes.
Review by usefulness
The weekly question is not "Did I organize everything?" It is "What did I reuse?" Promote notes that helped with a paper, exam, decision, or build. Delete or ignore notes that never become useful.
Template: Capture inbox, active maps, durable notes, archived projects. Four folders are enough for most people.
For a cadence that keeps this from decaying, use the weekly review template. If AI is part of your note workflow, keep the source-verification step from the AI study workflow.