Most people take notes the way they were never taught to: writing down as much as possible, as fast as possible, and rarely looking at any of it again. The result is pages of transcription that feel productive in the moment and are almost useless a week later. Good note-taking is not about capturing more. It is about deciding what matters, recording it in a form your future self can use, and building the habit of going back.
This guide explains how to take better notes in lectures, meetings and while reading: what the well-known methods actually do and when each fits, the handwriting-versus-typing question, how to review notes so they turn into understanding, and the mistakes that make notes look thorough while teaching you nothing.
What notes are actually for
Notes serve two different purposes, and confusing them is where most trouble starts. During the session, writing forces you to process: you have to decide what the speaker's point was in order to write it down in fewer words. After the session, notes are a record you can review, test yourself against and connect to other things you know.
Verbatim transcription fails both purposes. It skips the processing (you're copying, not deciding) and produces a record too long to review. Almost every good method is a structure for forcing you to condense and organise while you write.
The main note-taking methods and when to use them
The Cornell method
Divide the page into a wide right column for notes, a narrow left column for cues, and a strip at the bottom for a summary. During the session you write in the right column. Afterwards, you add questions or keywords in the left column that the notes answer, and a two-or-three-sentence summary at the bottom. Reviewing means covering the right column and answering the cues from memory. It suits lectures and any content you'll be tested on, because the review step is built into the layout.
Outlining
Main points as headings, supporting points indented beneath them, details indented further. It works best for well-structured material (a lecture that follows a clear sequence, a textbook chapter) and falls apart when the speaker jumps around. Its strength is that the hierarchy itself shows how ideas relate.
Mind mapping
The central topic in the middle, branches for main themes, sub-branches for details, drawn rather than listed. Useful for subjects where connections matter more than sequence, for planning essays, and for revision where you want to see a whole topic on one page. Less suited to fast-moving, detail-heavy content.
The sentence or "flow" method
Writing each idea as a short sentence in your own words, in the order it comes, with arrows or margins linking related points. It's the most flexible for unstructured discussions and meetings, and it forces paraphrasing, which is where the processing happens.
Pick by context, not loyalty. Cornell for lectures, outlining for structured reading, flow for meetings, mind maps for revision is a reasonable default set.
Handwriting or typing?
Typing is faster, which is exactly the problem: it lets you transcribe instead of condense. Handwriting is slower, so it forces choices about what to write, and many people find that helps understanding and recall. Typed notes are easier to search, reorganise and share.
A practical compromise: handwrite during sessions where understanding matters most, then type up a condensed version afterwards as your first review. If you must type live, deliberately paraphrase and use shorthand rather than trying to keep up word for word. Whichever you use, the medium matters less than the habit of processing.
Taking notes in the moment
- Prepare. Skim the reading or the agenda first. Knowing the shape of what's coming makes it far easier to spot what's important.
- Listen for signposts. "The key point is", "there are three reasons", "in contrast", "for example". These tell you what to write and how to structure it.
- Write in your own words. If you can't paraphrase it, you don't yet understand it; mark it with a question mark and come back.
- Use a consistent shorthand. Arrows for causes, abbreviations for recurring terms, a symbol for "definition" and another for "example". Keep it simple enough to read in a month.
- Leave space. Wide margins and gaps between sections give you room to add cues, corrections and connections later.
- Mark what you didn't get. A question mark in the margin is a to-do item for the review, not a failure.
The review: where notes become learning
Notes you never revisit decay quickly, along with the memory of the session. A short review within a day, then again a few days later, does far more than a long re-read the night before a deadline. In the first review, tidy the notes: fill gaps while the session is fresh, resolve the question marks, write cues and a summary. In later reviews, test yourself rather than re-reading: cover the notes, answer the cues, then check. This is the same active-recall principle covered in our guide to study techniques that actually work, and notes are the raw material it runs on.
Spaced review also tells you which notes matter. Material you can recall easily after two reviews needs less attention; the sections you keep getting wrong are where to spend time.
Notes for meetings and work
Work notes have a different job: decisions, actions and reasons, not the whole discussion. A simple structure covers it: what was decided, who is doing what by when, and any context you'll need to explain the decision later. Write the actions in a separate section so they don't get lost in narrative, and send or file them the same day. Well-kept meeting notes also make it much easier to turn recurring processes into documentation; our article on writing standard operating procedures starts from exactly that kind of record.
Keeping digital notes findable
If you type or transcribe your notes, the tool matters less than the organisation. Use consistent titles (date, subject, topic), a small set of tags or folders rather than an elaborate taxonomy, and link related notes to each other where the app allows it. Search is your main way back in, so write in the words you'd search for. Whatever the tool, make sure it's included in your backups; notes are easy to lose and painful to reconstruct.
Mistakes that make notes look good and work badly
- Transcribing. Writing everything captures nothing.
- Highlighting as a substitute for notes. Colouring a page is not processing it.
- Rewriting neatly instead of condensing. A tidy copy of the same words adds nothing; a shorter version in your own words does.
- Never reviewing. Notes without review are a diary, not a learning tool.
- Over-engineering the system. Elaborate colour codes and templates become the task. The method should disappear.
FAQ
Which note-taking method is best for students?
The Cornell method is a strong default for lectures because it builds review into the page. Use outlining for structured reading and mind maps for pulling a topic together before an exam. Most students end up using two or three methods depending on the subject.
Should I take notes on slides the lecturer provides?
Yes, but don't copy them. Slides are usually an outline; your notes should capture the explanation, examples and emphasis the speaker adds. Annotating printed or digital slides with those additions is efficient.
How soon after a lecture should I review my notes?
Ideally within twenty-four hours, while you can still fill gaps from memory. A ten-minute tidy-up and summary the same day is worth more than an hour of re-reading weeks later.
Conclusion
Better notes come from doing less writing and more deciding. Choose a method that fits the situation, write in your own words, leave room for the review, and then actually do the review, testing yourself rather than re-reading. Handwrite when understanding matters, type when searchability matters, and keep the system simple enough that it never becomes the point. Notes taken this way are shorter, uglier and far more useful.
