Notetaking for University Students

A university study system built around Obsidian hinges on one idea: notes aren’t just summaries—they’re a scheduled step in spaced repetition and active recall. The workflow starts with understanding concepts for oral exams, then turns that understanding into highly condensed, diagram-like notes, and finally uses those notes as the prompt set for repeated, timed explanations. In medicine—where exams often demand 20–30 minutes of discussion rather than memorizing isolated facts—this approach aims to preserve the “whole picture” and connections between topics, not just discrete details.

The system begins with context: the presenter studies medicine in Italy, where assessment is heavily based on interrogation. Because questions are open-ended and discussion-heavy, the study method prioritizes concept comprehension over rote practice. That shapes tool choice too: flashcards like Anki are used selectively for numbers and highly specific memorization, while most learning is driven by reading, note-making, and later recall.

Two study principles guide everything. First is spaced repetition: material is revisited at expanding intervals (roughly day 1, then 2–3 days, then a week, then two weeks) to avoid cramming and improve long-term retention. Second is active recall: before reviewing, the student tries to retrieve information from memory by answering questions, rather than rereading or highlighting.

Notes fit into this system despite being “inefficient” on their own. The value comes from forcing re-elaboration—writing in one’s own words to confirm understanding—and from creating a clean reference layer that’s easier to revisit than messy textbooks. Notes also become a personal “custom Wikipedia,” reducing reliance on the internet later. The presenter treats inefficiency as unavoidable and schedules it where it helps most: note-taking is positioned as the first recall opportunity, not a passive capture step.

Planning is handled in Notion using a calendar and a simple state model for each topic: “to read,” “to take notes,” and “to repeat,” with tracking for review counts and timestamps. A key scheduling tactic is temporal separation: reading happens now, but note-taking and the first recall happen later (often about a week). That delay makes note-taking itself an occasion to retrieve what was learned.

In Obsidian, the notes are structured for speed and compression. Instead of paragraphs, the presenter uses outline lists to mimic diagram structure (a “spider diagram” of nested bubbles). The goal is minimal wording—just enough to explain later—supported by arrows and symbols to represent relationships like increases/decreases or conditional rules. Mermaid diagrams are used when flowcharts capture complex mechanisms more efficiently than text. A plugin like Excalidraw is mentioned as another way to condense visuals.

Organization relies on an index-first approach: a master index links to notes so nothing gets lost during review. Tags are largely avoided because the Notion system already encodes review state, and the index handles grouping. When notes get too complex, splitting is treated as a later, situational decision guided by headers and the point where sub-sections multiply.

Finally, Obsidian is tuned with quality-of-life plugins—faster navigation, table formatting, pane management, and a “typewriter” cursor-centering tool—so the workflow stays focused on writing and recalling rather than wrestling with the interface. The broader takeaway is a tightly integrated loop: read for comprehension, convert into condensed prompts, then repeatedly explain from memory using those notes as the backbone of exam preparation.