Meeting notes are chronological because that's the order things were said in. That order is almost never the order they matter in, which is why a page of notes answers "what happened" and completely fails to answer the two questions anyone actually returns to it with: what did we decide, and who owes what?
A mind map answers those, because it's structured by topic rather than by time. The conversion is mechanical once you know what you're converting to.
Don't mirror the meeting
The mistake that produces useless maps is one branch per agenda item, in the order they were discussed. That's the notes again, bent into a circle.
Use these five branches instead, every time:
- Decisions — settled, with who settled it.
- Actions — owner and date on every one, or it isn't an action.
- Open questions — unsettled, with who needs to answer.
- Context — the reasoning worth keeping. Why the decision went that way.
- Parked — raised, deliberately not now. Prevents the same topic being re-litigated in three weeks.
The fixed shape is the point. Every map looks the same, so six weeks later you know exactly where to look, and building the map becomes sorting rather than designing.
The method
1. Extract before you organise
Read the notes once and mark every line that is a decision, an action, a question or a piece of reasoning. Everything unmarked is transcript, narration of who said what, and it does not go in the map. This step usually removes sixty to eighty per cent of the text, and doing it before thinking about structure is what stops the map inheriting the meeting's shape.
2. Sort into the five branches
Ambiguous items resolve with one question: could someone act on this without asking anything further? If yes it's an action. If it needs an answer first, it's an open question. If it closed off other paths, it's a decision.
3. Give every action an owner and a date
An action with no name attached is a wish. If the meeting didn't assign one, the
map should record the gap. Owner: unassigned is useful information
and much better than a blank.
4. Add the second level, and stop
Under Decisions, one level down: what the decision rules out. Under Open questions: who is expected to answer. Two levels below the five branches is enough for almost every meeting. Three means you're transcribing again.
5. Cross-link
This is the step that pays for the whole exercise. Link each action back to the decision that produced it, and each open question to the decision it blocks. Six weeks later, when someone asks why a thing is being built that way, the answer is a line on the map rather than an archaeology exercise.
The fast version, with AI
If the meeting produced a transcript rather than notes, don't paste the transcript into a mind map generator. You'll get a map of the conversation, which is the failure mode above. Ask for the extraction first:
From this transcript, produce a Markdown outline with exactly five
top-level headings: Decisions, Actions, Open questions, Context, Parked.
Under Actions, one bullet per action in the form "Owner — task — date",
using "unassigned" where no owner was named. Quote nothing; do not
include anything that is only narration.
Then import that Markdown into whichever tool you use. Most mind map apps read Markdown or OPML directly, so the outline becomes a map in one step, and you review the structure rather than build it.
Two things to check in the output, every time. The Actions branch is where AI invents things. It will confidently assign an owner who was never named. And an empty Parked branch usually means it wasn't looking; things get raised and deferred in nearly every meeting.
Imports Markdown and OPML, cross-links any two topics, and gives every task a checkbox whose progress rolls up the branch, so the Actions branch reads as a completion percentage. Everything stays on the device, which matters for notes you shouldn't be uploading.
What it doesThat last point is worth stating plainly: meeting notes are frequently the most sensitive text a person handles all week: headcount, pricing, client names, a decision not yet announced. A browser tool that uploads them is a considered choice, not a default. The comparison of free AI mind map tools sorts the options by where the text ends up.
Making the map worth keeping
Check the Actions branch, not the map. If checkboxes are available, put them on the actions only. A branch that reports "4 of 7" is a status update you didn't have to write.
Colour by owner, not by topic. Then "what do I owe from this meeting" is a glance instead of a read.
Carry Open questions and Parked into the next meeting's map. Those two branches are the agenda, already written. This is the habit that turns a series of maps into a thread rather than a pile.
One map per meeting series, not per meeting, for anything recurring. A weekly standup wants one map that grows a dated branch each week; twelve separate maps of a standup are twelve things nobody opens.
When not to bother
Some meetings don't need this. If the meeting produced one decision and no actions, write the decision down in a sentence and move on. Mapping a fifteen-minute meeting costs more than the meeting did.
The threshold is roughly: more than three actions, or more than one open question. Below that, the notes are already short enough to read.