Short answer: Use one mind map as a daily dashboard: give each day of focus a single first-level branch, collapse the rest with the chevron, and keep the next concrete action in the root note. Fold finished branches away so only today's work is visible, and walk the plan in presentation mode when you want to review it.

Keep one map open as your dashboard

A focus map is a document you keep open, not a set of notes you file. Open the mind map at the start of the session, give the work one first-level branch, and leave it on screen for the rest of the hour. When the next step is not obvious, you look at the map instead of hunting through a folder.

Canvasola keeps a local autosave of the current document, so the map survives a closed tab and a browser restart without an account. That makes one open map a reasonable home for a day's work even if you switch to the canvas mid-session. The complete Canvasola guide explains how the tabs fit together.

A second map is a second thing to maintain. The moment you want one to hold a sub-task, put that sub-task under today's branch instead. One map with one visible branch is the whole setup, and everything else about it can be added later.

  • One map, one visible branch, one working session
  • The map is the only place you look for the next step
  • Local autosave means the map is still there tomorrow
  • Sub-tasks go under a branch, not into a new document

Note: Local work needs no account, but cloud sync is opt-in: if you want the map on a second device you have to switch sync on yourself.

One branch equals one day of focus

A day of focus deserves one branch, not one branch per task and not one per hour. The branch is a container for everything belonging to that day: the tasks, the questions, the reading, the small decisions. You want to see today as a single thing you can open.

Inside the branch, use children for the pieces. Add a child with Tab and a sibling with Shift+Enter. Keep labels short enough to read at a glance, because the branch is scanned rather than read. If a child needs a paragraph, that paragraph belongs in the node's note.

Rename a node with Enter or F2 and the map updates in place. If the day needs a different shape, Shift+Tab returns a node to its parent so you can re-file it. Structure stays editable, so there is no reason to plan the branch shape in advance.

  1. Create the day branch. Select the root node, press Tab, and name the branch for the day or for the single outcome you are working toward.
  2. Add the first task as a child. With the branch selected, press Tab and type the first concrete action. Keep it to a verb and an object.
  3. Add the rest as siblings. Use Shift+Enter for each further task at the same level, then read the branch from top to bottom to check the order.

Keep the rest of the map out of sight

A map with twelve open branches is a map you have to read before you can work in it. Fold the branches you are not using: click the chevron on a node and everything below it disappears, while the label stays visible. Collapse All reduces the whole map to its first level.

Collapsing is cheap and reversible. Each node stores its own expanded state, so a branch you folded on Monday is still folded when you return. Press Ctrl/Cmd+F when you cannot remember which branch held a thought; search looks at labels and notes, ranks the results and jumps you to the node.

The guide to collapsing mind map branches covers the full folding routine. Toggle the minimap with M once the map grows past a single screen, and click it to jump the camera elsewhere.

  • The chevron on a node folds everything under it
  • Collapse All reduces the map to its first level
  • Every node remembers whether it was open or folded
  • Ctrl/Cmd+F finds a branch you only half remember

Note: Folding hides content but deletes nothing, and hidden nodes still count toward the 2,000-node ceiling for a single map.

Put the next action in the root note

The root node is the one label you can see from anywhere in the map, which makes it the right home for a single next action. Open the root note and write the next step as a sentence: "send the draft to Priya", not "draft email". A root note survives every collapse.

Notes are rich text, so you can use bold for the action, a bulleted list for the steps behind it, and a link to your source. A note holds up to 80,000 characters, far more than a focus map needs, and that is worth using for detail that would otherwise sprawl into child nodes.

Keep the root note to one action and two lines of context. If it grows into a list, the plan belongs in the branch you are working on, and the root label has stopped being the thing you glance at. The notes guide covers the panel and Dictate.

  • One action in the root note, written as a sentence
  • Bold the action so it reads at a glance
  • Link the source you are working from inside the note
  • Anything longer moves down into a branch

Move finished branches out of the way

Finished work should not keep competing for attention. When a branch is done, fold it and move it down the map, or rename it with a date and a tick so the top shows only what is still live. A folded branch takes one line of space no matter how much it holds.

If a branch is finished but you want the detail later, export it rather than keeping it in the way. A mind map exports to Markdown or OPML 2.0 as text and to SVG or PNG as images, so a completed day can leave the working map and live in a file.

A weekly sweep is enough. Once a week, collapse every branch, look at the first level and ask which items are still alive. Most focus maps hold three or four live branches and a history of the rest, which is a map you can still read at a glance.

  • Fold the branch, then rename it with a date or a tick
  • Export finished work to Markdown or OPML 2.0
  • Sweep the first level once a week
  • Keep three or four branches live at any time

Walk the map in presentation mode

Reading a map is not the same as using it. Presentation mode turns the map into a sequence: the first slide shows the root label, and each following slide shows one first-level branch with its immediate children. Press P to enter, ArrowRight to advance, Esc to exit.

Use that sequence as a two-minute review of the day. Each slide is a branch and its immediate children, enough to tell whether a branch is a task, a question or something you keep meaning to start. A map with a clean first level presents well; a map with a messy first level does not.

For a single-task session, pair presentation mode with zen mode: Ctrl/Cmd+. hides the interface around the canvas so only the map and the work are left. The keyboard cheat sheet lists the full set, including the arrow keys and Esc.

  • P opens presentation mode on the active map
  • Slide one shows the root label
  • Each later slide is one first-level branch with its immediate children
  • Ctrl/Cmd+. clears the interface for a single-task session

A checklist you can reuse

  • Exactly one mind map is open for focus work
  • Today's work sits on a single first-level branch
  • Every other branch is collapsed with the chevron
  • The root note holds one next action written as a sentence
  • Finished branches are folded and renamed with a date
  • Presentation mode has confirmed the first level is clean
  • Zen mode is available with Ctrl/Cmd+.

Common mistakes to avoid

  • One branch per task. A day with eight branches is a list, not a focus device. Put the day on one branch and let the children carry the tasks.
  • Leaving every branch open. An open map has to be read before it can be used. Fold the branches you are not working on and leave only today's visible.
  • Storing the next action in a child node. Child nodes vanish the moment their branch is collapsed. The root note stays visible, so the action belongs there.
  • Keeping finished work at the top. Old branches push live work out of view. Fold them, rename them with a date and keep the map short.
  • Never using presentation mode. A quick pass through the slides exposes a messy first level faster than scrolling the map does.

Frequently asked questions

How many branches should be open on a focus map at once?

One. The point of the map is that the next thing to work on is visible without scrolling. Everything else can be collapsed, and because each node stores its own expanded state, nothing is lost when you fold it back down again.

Does a focus map keep working offline?

Yes. Canvasola is offline-first: the current document is kept in a local autosave in your browser, and the app carries on without a connection. Cloud sync is a separate opt-in step, so an unsynced focus map stays on the machine where you made it.

Can I use a focus map alongside the canvas and the App Builder?

Yes, and undo and redo is shared across the canvas, the mind map and the App Builder, so a mistake in one is reversible in the others. Keep the focus map in its own workspace tab and switch to it when the session changes.

What if a focus map grows too big?

A map holds up to 2,000 nodes and each label up to 8,000 characters, so size is rarely the limit. Folding branches and moving finished days into an exported file keeps it readable, but the real limit is your attention rather than the node count.

Open a focus map for today's work.

Start a new map, add one branch for the day, and put your next action in the root note. Everything else can wait until tomorrow.

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.