Student & Academic
How to take better lecture notes — a practical guide for students who want note-taking strategies that improve retention, aid review, and actually connect to the rest of their coursework rather than sitting in a notebook unread.
Most students take notes. Almost no students take notes that are useful two weeks later.
The gap between note-taking and useful notes is not effort. Students who type fast and transcribe furiously are working harder at note-taking than students who write selectively — and research consistently shows they're retaining less. The gap is what the notes are designed to do.
Transcription notes — typing or writing everything the professor says — are an attempt to capture what was presented. They succeed at this and fail at the only thing that matters: helping you understand, remember, and use the material later.
Better lecture notes are not more notes. They're notes designed to do something: to capture your understanding of what was presented, not a record of what was presented; to connect new material to what you already know; and to flag what you don't yet understand rather than transcribing confusion at high speed.
By the end of this guide, you'll have a three-stage note-taking system and the specific techniques that make each stage produce notes that work at exam time, not just during the lecture.
The speed mismatch problem: A professor speaks at roughly 100-150 words per minute. Handwriting captures approximately 25 words per minute. Even fast typing can't keep up with comprehensive transcription. The brain continuously makes a triage decision: what do I write down? Without a framework for that triage, students tend to write what's easiest to write — the specific words being said — rather than what would be most useful — the concept being illustrated.
The false security of complete notes: A notebook full of dense notes creates the illusion that the lecture has been captured. But the act of transcription is not the same as the act of understanding. Mueller and Oppenheimer (2014), in research published in Psychological Science, found that students who took notes by hand — forced by speed constraints to summarize in their own words — consistently outperformed students who typed comprehensive notes on tests of conceptual understanding. The transcription suppressed processing.
The isolation problem: Most notes are written without any connection to prior lectures, prior coursework, or prior reading. The material in Lecture 7 may directly qualify what the professor said in Lecture 3, or relate to a paper you read last week — but if your notes are a chronological record of each lecture in isolation, that connection never gets made while it's most visible: right after the lecture, when the context is fresh.
The default approach: open a notebook or a new document, attend the lecture, write as much as you can, stop when the lecture ends. Close the notebook. Return to it before the exam.
The limits of this approach are structural, not effort-based:
The solution is not better tools or a faster typing speed. It's a structural change in what note-taking is for.
Taking better lecture notes requires treating the lecture as the first of three stages, not the whole process:
Goal: Record understanding, not transcription.
The two-column structure (Cornell method): Divide your page — physical or digital — into two columns. The right column (about 70% of the width) is for notes during the lecture. The left column (about 30%) is left blank during the lecture and filled in afterward with questions, key terms, and summary cues.
Walter Pauk developed the Cornell method at Cornell University in the 1950s; it has been one of the most replicated effective note-taking structures in educational research since then. Its value is not in the columns themselves — it's in the practice of separating capture (right column) from processing (left column), which forces the review pass.
What to capture:
What NOT to capture:
Goal: Process what you captured and fill the left column.
The clarification pass is the most important stage and the most commonly skipped. Research by Karpicke and Blunt (2011), published in Science, found that retrieval practice — actively generating information from memory — is significantly more effective for long-term retention than re-reading notes. The clarification pass is a form of retrieval practice: you're looking at your notes and generating questions, summaries, and connections from the material you captured.
What to do in the clarification pass:
Fill the left column with questions: For each major concept in your right-column notes, write a question in the left column that the right column answers. "What's the difference between X and Y?" written on the left; the answer in the right. These become study questions for the exam.
Write a 3-5 sentence summary at the bottom of the page: What was this lecture about? What was the main claim? What should you understand, not just recall? Writing the summary requires you to synthesize the notes you just took — which is a retrieval practice event.
Flag your gaps: Mark anything you didn't understand with a specific question: "I don't understand why the supply curve shifts right here — re-read Chapter 3 or ask in office hours." Specific gaps are actionable; vague confusion is not.
Add connections: What does this lecture connect to? A prior lecture, a reading, something from another course? Write it in the margin. These connections are what make knowledge stick — isolated facts decay; connected concepts don't.
Goal: Place this lecture's material in the context of your course and your existing knowledge.
The connection pass is brief — 10-15 minutes — and happens sometime in the week after the lecture. Review the summary and left-column questions from your clarification pass. Ask:
Note these connections explicitly. The act of connecting new material to existing knowledge is the structural change that moves information from short-term recall to long-term understanding.
Setup: Tomás is a second-year economics undergraduate attending a lecture on price elasticity of demand. He has a tendency to transcribe everything and finds his notes unreadable before exams.
Default approach (what he used to do):
"Price elasticity of demand = percentage change in quantity demanded / percentage change in price. If elasticity > 1, elastic. If < 1, inelastic. If = 1, unit elastic. Luxury goods are elastic, necessities are inelastic. Cross-price elasticity = the effect of one good's price change on the quantity demanded of another good. Complements have negative cross-price elasticity. Substitutes have positive cross-price elasticity..."
10 pages of this, from beginning to end. Two weeks later: unreadable because the context is gone.
Three-stage approach:
During lecture (right column):
"Price elasticity = how responsive quantity demanded is to price change. > 1 elastic = buyers react a lot (e.g., luxury goods — vacation travel). < 1 inelastic = buyers barely react (e.g., insulin — they need it whatever it costs). WHY does this matter? Because it tells a seller whether raising price increases or decreases total revenue."
"Key example: if transit fares go up 10% and ridership falls 5% — inelastic (0.5). Transit authority still gains revenue. But if fares up 10% and ridership falls 15% — elastic (1.5). Revenue falls even though price went up."
Clarification pass (that evening):
Left column questions:
Summary (bottom of page):
"Elasticity measures how much quantity responds to price. Elastic demand = big response; inelastic = small response. This tells sellers whether raising prices is profitable: only if demand is inelastic. The transit fare example shows this clearly — inelastic = higher fares = more revenue; elastic = opposite."
Gap flagged: "Confused about income elasticity vs. price elasticity — they're different things. Check the textbook section."
Connection: "This connects to the monopoly pricing lecture — a monopolist will only raise prices into the elastic part of the demand curve because that's where revenue is maximized. This explains why."
Three weeks later: Tomás can answer the exam question about elasticity from the left-column questions, without re-reading the full notes. The summary tells him what to revise; the questions tell him what to practice; the connections remind him where this fits in the course.
Trying to catch up on transcription: if you fall behind in a lecture, resist the urge to transcribe the last 5 minutes of what was said. Write a note to yourself — "check recording/slides for this section" — and pay attention to the remaining lecture. Five minutes of attention is more valuable than five minutes of blind transcription.
Skipping the clarification pass: the clarification pass within 24 hours is not optional. Without it, the capture stage produces notes that decay on the Ebbinghaus curve and are difficult to use at exam time. Even a 15-minute clarification pass produces significantly better retention than none.
Making every connection global: not every lecture needs to connect to everything. A forced connection that isn't genuine isn't useful. The connections that help are the ones that arise naturally: "this reminds me of..." or "this seems to contradict..." — not "I need to find a connection for this."
Organizing notes by date instead of by concept: if your notes are organized "Lecture 1, Lecture 2, Lecture 3," they're organized chronologically. Before an exam, you typically want to study by concept or topic, not by date. Creating a concept index — a simple list of topics with page references to the relevant notes — is worth 30 minutes at the end of the term.
Taking better lecture notes is not about capturing more. It's about designing notes that do something: represent understanding rather than transcription, flag gaps rather than obscuring them, and connect new material to existing knowledge rather than recording each lecture in isolation. The three-stage system — capture during the lecture, clarify within 24 hours, connect within the week — distributes the processing work across short, specific passes rather than front-loading everything into a frantic transcription session. The result is notes you can actually use when the exam arrives, rather than a record of what was said that needs to be decoded from scratch.
More WebSnips articles that pair well with this topic.
How to build flashcards from your reading — a practical guide for students who want to convert reading notes into high-quality flashcards that actually produce long-term retention, rather than low-quality cards that take time to make and time to review without producing learning.
How to organize PDFs for research — a practical guide for students and researchers who want a systematic, searchable, and durable PDF organization system that remains useful when a collection grows from 20 files to 400, and that makes it easy to find any source without remembering the filename.
How to prepare a conference presentation from notes — a practical guide for students and early-career researchers who want to transform their research notes into a focused, compelling conference talk or poster, without losing the nuance of the underlying work or overloading their audience.
How to read faster without losing comprehension — a practical guide for students who have more assigned reading than they can finish, and want to increase their effective reading rate through legitimate strategies grounded in cognitive science, not speed-reading myths.
How to write a dissertation literature chapter — a practical guide for PhD students and graduate researchers who want to write a literature chapter that makes a sustained argument about the field, rather than a survey that summarizes source after source without building toward a coherent claim.
How to avoid plagiarism with good note-taking — a practical guide for students who want a note-taking system that clearly distinguishes quotes from paraphrases from their own ideas, so attribution is automatic rather than a last-minute panic before submission.