Short answer: Mind map a lecture by catching its structure as it happens: one branch per question the lecture answers, one-line labels you can type in seconds, and a node icon on anything you did not follow. Within the hour, fill the notes with detail you skipped, and turn every flagged node into a question you can answer before the next class.
Catch the lecturer's branch structure
A lecture already has a structure, and mapping it means noticing that structure while it happens. Listen for the moment the subject changes: "so that is the mechanism", "now the case against it". That shift is a branch, so write the new subject as a first-level branch and keep going.
Capture the branch the moment it starts, not the moment you understand it. Understanding takes longer than typing, and the detail belongs in a note you write afterwards. Add a branch with Tab and a sibling with Shift+Enter, and relabel anything later with Enter.
If the lecturer uses slides or a handout, use them as the skeleton and add branches for the things they say that are not on screen. Those are often the points that appear in the exam. The introduction to mind maps is a good short primer.
- One branch per shift in the argument
- Type the branch label the moment it starts
- Add your own branch for anything off the slides
- Keep the detail for the note pass afterwards
One branch per question the lecture answers
Turn the lecture into questions and each answer becomes a branch. "Why does the policy fail at scale?", "What evidence was used?", "How does this connect to last week?" A lecture answering four questions gives four branches, a shape you can review in minutes.
Questions keep the labels parallel, which is what makes a live map readable. Write each branch in the same shape: "What is X?", "How does X work?", "What if X fails?". Any branch becomes an exam question by swapping the order of the words, which is free revision material.
Leave a few branches half-labeled if you are unsure of the wording, then fix them in the write-up pass. Renaming with Enter or F2 is faster than a paragraph, and a better word written later is a branch you will remember. The branching rules cover parallel labels.
- Catch the first shift. When the lecturer changes subject, add a first-level branch with Tab and type the question the new part answers.
- Add the answers as children. Under each question branch, add the three or four things the lecturer said, one child per point.
- Close with a placeholder. If a point lands while you are typing, type a short placeholder rather than nothing, and resolve it later.
Type less and label more
Live mapping breaks when you try to write sentences. The rule is one line per node, no full stops, and no typing while the lecturer is mid-argument. If a label needs more than about six words it is a note, not a label: leave a short placeholder and move on.
A placeholder reading "example from lecture" is enough, because the live pass preserves the shape of the argument. You cannot reconstruct detail from memory either, so the live map captures structure and the careful pass afterwards captures content. The notes guide covers the notes you fill in later.
The same rule applies if you are taking notes on a phone, with even less room to stretch. One line per node keeps the map scannable on a small screen, and the labels you write in the room are the ones you will recognize a day later.
- One line per node, no full stops
- Six words is the limit for a live label
- Placeholders are fine, empty nodes are not
- Content waits for the note pass, structure does not
Note: A live map is a rough draft on purpose. A map you can finish typing is worth more than a map you abandon halfway through the lecture.
Mark what you did not understand
In a live map you will hit three moments you do not understand, and if you do nothing they disappear. Every node can carry an icon, drawn from a fixed set of 7 plus a remove option, so you can mark a node in one click. Use the icon to mark a gap, then turn the node into a question.
A flagged node is also a fast search handle. Press Ctrl/Cmd+F with the map active, type a word you half remember, and search returns ranked matches across labels and notes, with keyboard navigation and jump-to-node. That is how you find a gap you left in the back row.
Flags are temporary. By the end of the week every flagged node should be a note with an answer or a branch you asked someone about. A map still full of flags a week later is a map of your gaps, which is useful only if you meant it.
- One click adds an icon from a fixed set of 7, plus remove
- Flag the gap, move on, resolve it later
- Ctrl/Cmd+F finds a flagged node by a half-remembered word
- Resolve or delete every flag within the week
Fill the notes within the hour
The live map is the skeleton; the notes are the content. Give yourself one sitting, the same day, to open each branch and write what the lecturer said. Node notes hold rich text with bold, italic, lists and links, and up to 80,000 characters each.
Work from your own placeholders. Where the map says "example from lecture", write what the example was, and use a link in the note for the reading or slide deck. Dictate is faster than typing when you are walking and talking through a point, which is when lecture notes get written.
Do this the same day. The gap between a live map and a written note is where the understanding forms, and it is the part a photograph of the board cannot do for you. The guide for students covers how the note pass fits into a revision week.
- Open the map straight after. Give yourself one sitting the same day, before the lecture blurs into the next one.
- Work branch by branch. Open each question branch, write the answer, and replace every placeholder with the real point.
- Add links where you have them. Paste the link to the reading or slide deck into the note so you can return to the source.
Turn the live map into revision material
The review method for a lecture map is a gap sweep. Open the map, find every node carrying the flag icon, and work through them one at a time. For each one, write the question it raises and answer it from your notes. If the notes cannot answer it, write the question down to ask.
Then use presentation mode to walk the argument. Press P: the first slide shows the root label, and each following slide shows one first-level branch with its immediate children. A slide that takes more than a sentence to explain is where the lecture weight sits, and where your revision should go.
Export the finished map so it becomes revision material rather than a leftover file. Markdown or OPML 2.0 keeps the structure as text you can paste into revision notes, and SVG or PNG keeps the shape for a document or a slide.
- Sweep every flagged node and write the question it raises
- Presentation mode walks one branch per slide
- Export to Markdown or OPML 2.0 for your revision notes
- A slide that needs more than a sentence is where to revise
A checklist you can reuse
- One first-level branch per question the lecture answered
- Sibling branch labels follow the same question pattern
- No label is longer than about six words
- Every node has a label, even if it is a placeholder
- Gaps are marked with an icon from the set of 7
- Every branch has a note written the same day
- Every flag was answered or turned into a question to ask
Common mistakes to avoid
- Writing full sentences live. You will fall behind and stop listening. One line per node, and the detail goes into a note afterwards.
- Copying the slide deck. A map that repeats the slides misses what the lecturer added. Add branches for the spoken points that are not on screen.
- Leaving gaps unmarked. An unmarked gap is invisible a week later. Flag the node with an icon while it still embarrasses you.
- Leaving the note pass for later. The live map holds structure, not content. Write the notes the same day, while the lecture is still sharp.
- Reading the map instead of testing it. Your own map feels fluent because you wrote it. Sweep the flagged nodes and answer them without looking.
Frequently asked questions
How fast do I need to type during a lecture?
Fast enough to catch a branch label and a handful of children, and no faster. The live pass is a sketch of the argument, not a transcript. A map you finish typing is worth more than a perfect one you abandoned halfway through, because an unfinished map is a map you will not review.
What if I miss a whole section of the lecture?
Add a branch with a placeholder label such as "missed - 20 minutes" and flag it with an icon. You can fill it from a recording, a classmate or the reading later, and the gap stays visible in the map instead of quietly disappearing.
Can I search a lecture map I made weeks earlier?
Yes. Hold Ctrl/Cmd+F while the map is the active surface and the search box ranks matches across your labels and notes, with keyboard navigation and jump-to-node. If the canvas has the focus instead, switch to the map tab first, because search only runs against an active map.
Is a mind map the right tool for a fast lecture?
It is the right tool for the argument, not for the transcript. A map tells you how the lecture was built, which is what you need when the exam asks you to explain or criticise it. If you need every word, take linear notes as well and use the map for the shape.
Map the next lecture live.
Open a map before the lecture starts, add one branch per question, and flag what you miss. Write the notes the same afternoon.
This guide is part of the mind mapping guides collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.