Learn · Obsidian for researchers

Obsidian Canvas as an evidence map: where every box is data

Most qualitative software gives you a mapping view: the boxes link back into a project database that only the software can open. On an Obsidian canvas, every box can be the note itself — drag a code onto the canvas and its actual quotes and counts come with it, in plain files you own. The map stops being a view of your analysis and becomes your analysis, arranged.

After this guide you will be able to:

Build a canvas where each node opens the real note behind it.
See a theme's grounding — its codes, quotes, and participants — at a glance.
Explain why this beats the manual whiteboards in NVivo and MAXQDA.
Keep the map honest: grounding, not a confidence score.

The difference: a view of a database vs the files themselves

In a traditional CAQDAS map, the box labelled "waiting" is linked back into the project database — click it and the software shows you the coded segments. The link is real. But it lives inside a proprietary project file: the map is a view of the database, it opens only in the software that made it, and it goes wherever the licence goes.

On an Obsidian canvas, you drop the actual note for that code onto the board. It shows the note's live contents; double-click and you are reading the coded quotes themselves. Rename the code, add excerpts, and the node reflects it, because the node is the note. Nothing is a representation of your data. It is the data, placed where you can see how it connects.

What an evidence map looks like

Lay out one column per theme. At the top of each, the theme's note, with a small card above it summarizing its grounding. Beneath, the code notes that feed it, each carrying its own live counts. Attach the negative cases in a different colour, with an edge that says "complicates".

Now the map earns its keep. You can see, without opening anything, that this theme rests on three codes and seven quotes across four participants, that two negative cases push against it, and that a human has signed it. Click any box to check the claim against the real excerpts underneath.

Grounding, not confidence

One discipline keeps an evidence map honest: the card shows grounding: how much evidence sits under a theme and whether counter-evidence has been sought — never a score for whether the theme is "true". No number can certify a theme, and a map that displayed one would be inviting you to trust the layout instead of the data. Read "negative cases: none linked" as a task you have not done yet, not a clean bill of health.

How to read the map for problems

An evidence map is most useful when it shows you what is wrong. Three patterns to look for:

A crowded theme: a dozen codes crammed under one theme usually means the theme is doing too much and should split into two. If you cannot state it in one sentence, the map is telling you so.
An orphan code: a code note sitting off to the side, attached to no theme. Often that is your most interesting finding, or the seed of a theme you have not named yet. Do not force it into a nearby cluster to tidy the picture.
A theme with no negative cases: a column with only supporting quotes and nothing marked "complicates". Nine times in ten that means nobody hunted for counter-evidence, not that none exists. The empty space is a task.

Because you rearrange the map by dragging real notes, thinking through these problems is the analysis — you are not annotating a picture of your work, you are moving the work itself.

Why this is Obsidian's real advantage over NVivo and MAXQDA

	Traditional CAQDAS map	Obsidian evidence map
The node is	a symbol linked into the project database	the note itself, a plain file
Click it	opens the coded segments inside the software	opens the note: the quotes are the file
Without the software	the map does not open; the licence is the key	Markdown and JSON canvas open in any editor
Portability	proprietary project file	plain files you own

The big tools treat visual mapping as a side feature — a whiteboard bolted onto a database. Because every object in Obsidian already exists as a linked Markdown note, the map and the data are the same thing. For auditability, that is a better kind of object than a map locked inside a project file.

Building it by hand: in Obsidian, create a new Canvas, then drag notes from the file list straight onto it — each becomes a live card. Add a plain text card above a theme for its grounding summary, and colour the negative-case cards to stand apart. It is manual, but it is real: every card you place is a note you can open.

You can assemble an evidence map yourself by dragging your code and theme notes onto a Canvas.

If you want it generated (a map drawn automatically from your reviewed coding, with grounding cards, negative cases attached, and codes not yet in any theme grouped honestly), QualiVahti Local builds exactly this evidence map, and ships a worked demo study so you can see a finished one first.

See the evidence map it generates — €49