Simplify your system, download my template - A personal knowledge system
When the graph isn’t enough
The graph shows connections, but doesn’t show hierarchy.
All the notes are on one level. A beautiful web, but no structure.
Example:
In the graph you see that the notes are connected. But it’s unclear:
- What is the main topic?
- What is a sub-topic?
- How are the notes organised logically?
- In what order should you study them?
Canvas solves this problem.
What is Canvas
Canvas is an infinite board for notes, built into Obsidian.
You can:
- Place notes in space
- Connect them with lines
- Group them into structures
- Build a hierarchy
It’s like a personal version of Miro or XMind, but right in Obsidian.
Canvas vs MOC
| MOC | Canvas |
|---|---|
| A text structure | A visual structure |
| Hierarchy through grouping | Hierarchy through space |
| Created quickly | Requires time to arrange |
| For text | For visualisation |
When to use a MOC:
- To describe a topic
- For links to notes
- For application in projects
When to use Canvas:
- To understand the structure
- To study a topic
- To plan a project
- To visualise relationships
Visualisation techniques
Technique 1: A vertical tree (top to bottom)
When to use: A hierarchy “from the general to the specific.”
Structure:
[MOC - Productivity]
|
+-----------+---+---+----------+
| | | |
[Time] [Attention] [Energy] [Motivation]
| | | |
+--+--+ +--+--+ +--+--+ +--+--+
| | | | | | | | | | | |
[A][B][C] [D][E][F][G][H][I] [J][K][L]
How to create it:
- You open Canvas
- You click on the board → add a “Note”
- You choose MOC “Productivity”
- Below it you add four notes (sub-topics)
- Even lower — specific ideas
- You connect them with lines
Pros:
- It’s easy to understand what’s important
- It’s easy to see the levels
- A structure natural for the brain
Cons:
- It requires vertical space (a tall screen)
- There’s a lot of empty space on the board
Technique 2: A horizontal tree (left to right)
When to use: Processes, sequences, “first → then.”
Structure:
[Goal] → [Stage 1] → [Stage 2] → [Stage 3] → [Result]
| | |
[a] [b] [c]
Examples:
- A project: from idea to launch
- A process: from gathering information to action
- A career: from apprentice to master
Pros:
- More compact (fits on the screen)
- The sequence is clear
- Good for processes
Cons:
- Harder to add side branches
Technique 3: Fishbone
When to use: Analysing causes, diagnosing problems.
Structure:
[Problem]
/ | \
/ | \
[Fact1] [Fact2] [Fact3]
/ \ / \ / \
[A] [B] [C] [D] [E] [F]
Example: why I procrastinate
[Procrastination]
/ | \
/ | \
[Fear] [Boredom] [Fatigue]
/ | \ | |
[A] [B] [C] [D] [E]
Pros:
- Visual for analysis
- All the causes and effects are visible
- Helps with deep understanding
Cons:
- Requires time to create
- Can be overloaded
Technique 4: Free form (for brainstorming)
When to use: Brainstorming, ideas, experimentation.
Structure: No structure. You just lay out ideas wherever.
How to use it:
- You add notes randomly
- You connect them if you see a connection
- As you make sense of it, you start moving them
- Gradually order appears
Pros:
- No need to plan in advance
- Natural for creativity
- Open to new ideas
Cons:
- It can become chaos
- Requires reworking into a structured Canvas later
Plugins for speeding up the work
The Advanced Canvas plugin
Adds:
- Hotkeys (Tab to expand)
- Formatting (colours, sizes)
- Conveniences (automatic alignment)
Installation:
- Settings → Community plugins → Browse
- Find “Advanced Canvas”
- Install → Enable
The main hotkeys:
- Tab → create the next card (a tree)
- Ctrl+Enter → create a card next to it
- Ctrl+Shift+Enter → create a card below
- Ctrl+D → delete a card
Formatting:
You can change the colour, size, icon of each card.
Use it for visually highlighting different types (MOC, resource, project, action).
The Canvas Mindmap plugin
Automatically creates a tree from a Canvas.
Installation:
- Settings → Community plugins → Browse
- Find “Canvas Mindmap”
- Install → Enable
How it works:
- You create a Canvas
- You add a root note (the main one)
- You click “Generate mindmap”
- The plugin automatically creates the structure
Result:
A vertical tree is created automatically. You just add notes.
Practical examples
Example 1: A Canvas for studying a new topic
Scenario: You want to understand Obsidian deeply.
Step 1: You create a Canvas
Title: “Canvas - Obsidian: from beginner to master”
Step 2: The central note
In the centre of the board you add MOC “Obsidian.”
Step 3: The first level (four sub-topics)
Around the MOC you add:
- Structure (PARA)
- Connections (MOC, double brackets)
- Tools (graph, Canvas, plugins)
- Rituals (daily work)
Step 4: The second level (specific notes)
Under each sub-topic you add notes:
Structure:
Connections:
And so on.
Step 5: You connect them with lines
You connect the MOC with the sub-topics, the sub-topics with the notes.
Result:
A full visual map of the “Obsidian” topic. You see:
- The hierarchy
- The connections
- What to study first
Now you can click on the notes on the Canvas and read them.
Example 2: A Canvas for planning a project
Scenario: Plan the launch of an Obsidian course.
Structure: a horizontal tree (a process)
[Idea] → [Preparation] → [Recording] → [Release] → [Sales] → [Outcome]
| | | | |
[Goal] [Plan] [Script] [Review] [Marketing]
[Resources] [Recording] [Test] [Feedback]
How to create it:
- You create a Canvas “Canvas - Course launch”
- You lay out the stages horizontally: Idea → Preparation → Recording → Release → Sales → Outcome
- Under each stage you add sub-tasks
- You connect them with lines
Saving:
Each task is a note. You can click and edit it.
Result:
A full road map of the project. You see:
- The sequence
- The dependencies
- The nesting
Example 3: A Canvas for analysing a problem
Scenario: You procrastinate when writing scripts.
Structure: fishbone (analysing causes)
[Why do I put off the script?]
/ | \
/ | \
[Fear] [Vagueness] [Distractions]
/ | \ / | \ / | \
[A] [B] [C] [D] [E] [F] [G] [H] [I]
Specifically:
[Script procrastination]
/ | \
/ | \
[Fear] [Vagueness] [Distractions]
/ | \ / | \ / | \
[Bad] [Judg] [Hard] [Boring] [Tools] [Social]
How to use it:
- You look at each branch
- For each cause you look for a solution
- You add the solution next to the cause
- You implement them one by one
Result:
You see the full picture of the problem and the ways to solve it.
Common mistakes when working with Canvas
Mistake 1: Canvas instead of a MOC
“I’ll create a Canvas and that’s it, nothing else is needed.”
Canvas is a supporting tool. It doesn’t replace a MOC.
The solution: Use a MOC for description, Canvas for visualisation.
Mistake 2: Too big a Canvas
200+ notes on one Canvas. This is a web, not a structure.
The solution: Break it into several Canvases. One Canvas = one topic.
Mistake 3: Forgetting to update the Canvas
You created a Canvas a month ago. Since then you’ve added 10 new notes. You haven’t updated the Canvas.
The solution: A ritual: once a month update the Canvas (add new notes, remove archived ones).
Mistake 4: Canvas for the sake of beauty
You spend hours on the styling, colours, alignment. But the Canvas isn’t used.
The solution: Canvas is a tool, not a work of art. Function is more important than beauty.
Mistake 5: Trying to automate everything
“I want the Canvas to be created automatically from the MOC.”
Automation deprives you of the thinking process. When you manually arrange notes on the Canvas — you think about their connections.
The solution: Create the Canvas by hand. It’s slower, but more effective.
Keep going? → Principles and rituals — how to keep the system alive