Mind map for a thesis: from question to plan

Begin with the research question

A thesis map that starts with a chapter list is a filing cabinet. Start with the question instead, written as one sentence in the root node, and let every branch earn its place by serving that sentence. The test is simple: if a branch would look the same in a different thesis, it is background and belongs in your notes.

The wording matters more than it looks. "How does remote work affect retention" is a topic and can absorb any evidence you find. "Under what conditions does distributed work reduce voluntary turnover" is a question with an answer, and it tells you which literature to read and which findings would count as support.

Add a child node called "what would count as an answer" and list the evidence that would settle the question. That child becomes your filter later, when a source is interesting but irrelevant. If the topic is still fuzzy, the research topic map covers the search plan you need first.

• The root holds one sentence you could defend out loud
• Every branch can be described as serving that sentence
• The 'what would count as an answer' child is your filter
• One map for one thesis, never one per chapter

Map the literature by argument, not by author

Give each position in the debate a branch, and let the authors live underneath as children. A branch called "training reduces onboarding time" collects every study that argues it, whoever wrote it, while a branch called "training is cost, not investment" collects the counter-evidence. The same author's work often sits in both branches, and an author-first map hides that.

Give each position branch three children: the claim in one sentence, the kind of evidence it rests on, and the sources with author, year and page. The sources belong in the rich note as a bulleted list, because the note holds up to 80,000 characters and the label can only carry so much. You want the reference list to be the first thing you can generate, not the last thing you reconstruct.

Use cross-links to join the positions that argue against each other, which is allowed between any two nodes. The link shows as a tube, and there is no label editor, so name the relationship in the note of one of the two nodes, for example "direct contradiction of the training result".

• One branch per position, not per author or paper
• Authors become children, because one author can hold two positions
• Sources live in the note with author, year and page
• Cross-links mark which positions contradict each other

Note: Keep a position and a finding apart. A finding is what a study observed; a position is what somebody concludes from it, and your thesis will sit on the second level.

Expose the gaps your thesis can claim

A gap is where two positions on the map fail to resolve each other, and it is the only place a thesis can be original. Look for branches that argue past each other, and for positions whose evidence is thin in a way you can name. Then ask the harder question: is the gap real, or is it only that you have not read the paper that settles it?

Add a branch called "the gap" with three children: what is already known, what is missing, and what my thesis will argue. Write the missing piece as a claim you would defend out loud, because a gap written as a topic cannot become a chapter. Write the known part as a bulleted list of the sources that already cover it.

• The gap is a disagreement between two branches
• Write what is missing as a claim you can defend
• List the sources that already cover the known part
• Name one paper that would close the gap

Turn the gap into a chapter plan

Chapters follow from the argument, they do not contain it. A four-chapter thesis usually looks like this: the question and the definitions, the literature and where the gap sits, the method or the evidence, and the argument itself with what it implies. If you cannot say why a chapter exists, it is a container for material you have not organized yet.

Add one branch per chapter, and under it one child per section, with each section named after the claim it makes rather than the topic it covers. A section called "results" says nothing, while "remote teams stay longer in roles with new hires" tells you exactly what has to be argued. Then cross-link each section to the position branch it argues against, and check whether every section has a link.

1. Name the chapters by job. Give each chapter branch a label saying what the chapter does, such as 'defines the terms' or 'presents the evidence'.
2. Break chapters into claims. Add one child per section and write each label as the claim that section will make, not as a topic name.
3. Link sections to positions. Draw a cross-link from each section to the position branch it argues against, and note what it claims.
4. Cut the orphans. Remove any section with no link to the gap, because a chapter with no argument in it is where the page count comes from.

Track evidence against each claim

Every claim node needs its source, and the source belongs in the rich note where you can format it. Use a bulleted list, one line per source with the author, the year and the page, followed by a short sentence on what it supports. Write the quote in the note as well, because a paraphrase is already halfway to a misquote in a draft.

Then audit with search. Press Ctrl/Cmd+F while the map is active and search a keyword from your central claim, and the results are ranked across both labels and notes, so you see every place that depends on it. Run that for three or four key terms and you learn which claims are load-bearing and which are decoration.

• One note per claim, listing source, year, page and support
• Copy the quote into the note rather than paraphrasing
• Every claim node carries the page of its source
• Search key terms and read the ranked results as an audit

Note: Search only works while a mind map is the active tab, and it reads labels and notes rather than images, so anything captured as a picture still needs its text in a note.

Check the argument with an adviser

Export the map before the meeting. Markdown gives you a text outline you can paste into a document, and OPML 2.0 keeps the full structure in tools that read it, with multi-layer maps round-tripping through a layer tag. Export both: the outline is what you send, and the OPML file is your own backup. The complete Canvasola guide shows where the export options sit.

Send a paragraph, not a tree. Write one paragraph that states the question, the gap and the claim, and attach the exported outline underneath it. Advisers read paragraphs, and a paragraph that says "the map has eleven branches" tells them nothing about whether the argument holds.

Bring the map to the meeting too, and use presentation mode. Press P and slide one shows the root label, then each slide shows one first-level branch with its immediate children, which is close to the structure of a ten-minute discussion. Use it to walk the argument, and use the adviser's question to decide which branch deserves the time.

• Export Markdown for the outline and OPML for the backup
• Send a paragraph stating the question, the gap and the claim
• Rehearse the argument in presentation mode beforehand
• Decide in advance which branch the adviser should focus on

Note: Canvasola has no comments, no share links and no live editing, so your adviser reads a file you send rather than the live map. Agree the version by naming the export date.

A checklist you can reuse

• The root node holds a research question in one sentence
• Every branch can be described as serving that question
• Each position branch has claim, evidence type and sources
• The gap branch states what is missing as a claim you can defend
• Every section in the chapter plan links to a position branch
• Every claim node has a note with source, year and page
• Markdown and OPML exports exist as your own backups

Common mistakes to avoid

• Organizing by author. Author-first maps hide the argument, because the same researcher often supports opposite positions. Branch by position and let the authors live underneath.
• Choosing chapters before the gap. A chapter list you chose in week one will not survive contact with the literature. Find the gap first, then let the chapters follow from it.
• Using the map as a bibliography. A long list of sources is a reading list, and you already keep one. The map earns its place by showing which source supports which claim.
• Claiming a gap nobody looked for. Write "no one has studied this" and you will be corrected by the first search. Name the disagreement between two positions instead.
• Paraphrasing sources from memory. A paraphrase written in a note becomes a misquote in the draft. Copy the sentence into the note while you are looking at it.

Frequently asked questions

How many nodes does a thesis mind map need?

A single map holds up to 2,000 nodes, far more than a thesis should need. If you are approaching that, the map has usually stopped being an argument and become a library. Aim for the shape of your argument rather than the volume of your reading.

Should the literature be mapped by author or by topic?

By argument. A branch per position tells you what the field thinks and where the disagreements are, which is the material a thesis is made of. Authors are then children of the positions they defend, so a researcher who changed their mind is visible rather than duplicated.

Can I import notes I already wrote?

Canvasola imports and exports Markdown and OPML 2.0, so a plain outline or an existing OPML file can be brought in and reworked. The structure still needs thinking: imported material gives you the words, and you decide which become branches, which become notes and which are cut.

Can my adviser open the map in Canvasola?

Not directly: there are no share links and nothing is published from the app, so an adviser cannot open a live map. Send the Markdown outline or a PNG, and if they use Canvasola, send the .canv project file, which carries the notes, the colors and the cross-links.

This guide is part of the mind map use cases collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.