Project plan mind map template

What the template already gives you

The Project Plan template is one of the 13 starters Canvasola ships with, filed under business in the gallery. It arrives as a root node called Project Plan with five branches: Goals, Scope, Timeline, Team and Risks. Each branch comes with two children, from Success metrics and Alignment under Goals to Known risks and Mitigations under Risks.

That starter shape is the point. You are not staring at an empty root, you are arguing with a structure someone already thought through. A plan written against these five branches has to answer what success looks like, what is not being done, when things land and what could go wrong.

Open it from the Templates button in the mind map toolbar, or from the command palette with Ctrl/Cmd+K and "Start from a template". The gallery groups the 13 starters into business, education, personal and brainstorming. Choosing a template replaces the current map, so keep anything you already built in another workspace tab.

• Keep Goals, Scope and Timeline for almost every project
• The Out of scope child is the most valuable line on the template
• Team earns its place once two people share the work
• Put the project name in the root label, not in the tab title

Note: Workspace tab titles are generated, so they read Canvas 1 or Canvas 2 whatever the project is. The root label is where the project earns its name.

Delete the branches your project does not have

A template is a superset, and the first edit is subtraction. A weekend build does not need a Team branch, and a two-week spike does not need Risks unless the spike can burn something expensive. Select the branch and press Delete, and it goes with everything under it, so check the children before removing the parent.

Deleting the wrong thing is cheap to undo. Ctrl/Cmd+Z steps back through the shared history, which keeps 20 versions of the canvas, the mind map and the App Builder together. Duplicate a branch with Ctrl/Cmd+D first if you want the original shape for reference in a second tab.

1. Open the template. Choose Project Plan in the business section of the gallery so the map arrives with its five branches ready to fill.
2. Remove what does not apply. Select a branch and press Delete to remove it together with its children, starting with Team for work you do alone.
3. Straighten the map. Press A to auto-arrange once the deletions are done, which clears manual positions and re-runs the layout so the branches sit square.

Rewrite the root as an outcome

The root arrives labeled Project Plan, which tells a reader nothing about which project this is. Select the root and press Enter or F2 to rename it, then put the outcome in the label: "Ship the checkout redesign by 30 June". A label holds up to 8,000 characters, so the whole sentence fits.

An outcome at the root changes what the rest of the map is for. Goals then answers how you will know it worked, Scope answers what the outcome excludes, and Timeline answers when it lands. Write the root last if you prefer, because the outcome only becomes clear once the milestones and the risks are visible.

• One sentence: what will be true when the project is done
• A date in the root makes the map self-describing
• Name it for a reader who has never heard of the project
• Short enough to read without zooming in

Add owners and dates to the branch notes

A node label holds one line, which is why the template's branches carry children instead of details. Put the detail in the rich note on the branch: open Add / edit note from the node menu and write the owner, the date and the done condition as a bulleted list. A note can hold 80,000 characters, so nothing has to be trimmed.

Add a child with Tab when a branch needs its own label, and press Shift+Tab to step back out to the parent node. That round trip is the fastest way to work down a plan: Tab for the next line, Shift+Tab back to the branch, Tab for the next one. The shortcut cheat sheet lists Shift+Enter for a sibling as well.

1. Open the note. Select the branch and choose Add / edit note, then write the owner, the date and the done condition as a bulleted list.
2. Keep labels short. A branch labeled "Milestone 2, payments team, 14 May" cannot be read at a glance. Put the milestone in the label and the rest in the note.
3. Read it back. Presentation mode shows the root and then one slide per first-level branch, so a quick run-through shows which branch lacks a date.

Reuse the risk branch every time

The Risks branch is the one most people delete and the one that pays for itself. It arrives with Known risks and Mitigations as its two children, and that pairing is right: a risk without a mitigation is a worry, and a mitigation without a risk is a task in the wrong place.

Write each risk as a cause and an effect rather than a feeling. "The payments provider delays the sandbox key" is a risk, while "payments might be a bit slow" is not. Add a child under Mitigations saying what you will do about it and who owns it.

The Scope branch protects the Risks branch. Out of scope is where the work you decided not to do lives, and it is the cheapest mitigation available: if something is out of scope, it is not a risk you have to carry. The retrospective guide covers the other end of that loop.

• One child per risk, phrased as a cause and an effect
• Every risk gets a mitigation child or a reason it needs none
• Out of scope is the cheapest mitigation on the whole map
• Read the branch again at the start of every project

Export the plan to a shared outline

Not everyone has Canvasola open, so export the plan. The File menu and the command palette both offer Export mind map OPML, which writes an OPML 2.0 document other mind map tools can open, and the plain-text outline export for a document or a chat message. Markdown export gives the same tree as a bullet list. The project plan template page shows the starter shape on its own, and the project planning collection covers how the same structure scales up.

Press A to auto-arrange before you export. It clears manual positions and re-runs the layout, so the file carries a clean structure instead of a map that only makes sense in your head. Fit the map to the view with F, and open the outline panel with O to read the plan as text.

• OPML 2.0 for other mind map tools, Markdown for documents
• Auto-arrange before you export, never after
• Keep the .canv project file so the map can be reopened
• PNG and SVG are for slides, not for further editing

Note: Canvasola does not host maps online, so the exported file is how the plan travels. Two people editing two copies means merging by hand, because there is no live editing.

A checklist you can reuse

• The root label states an outcome rather than the project type
• Branches that do not apply to this project were deleted
• Every branch that needs an owner has a note saying who and by when
• Each risk names a cause and an effect and has a mitigation
• Something is written under Out of scope
• The map was auto-arranged before it was exported
• The plan was exported as OPML 2.0 or a plain-text outline
• A .canv project file is saved next to the export

Common mistakes to avoid

• Keeping every branch. A template nobody trimmed still carries branches you will never fill in. Delete the ones that do not apply so the map shows only the decisions you made.
• A project name at the root. The root should say what finishing looks like, not repeat the words Project Plan. Rename it with Enter or F2 and put the outcome in the label.
• Dates and owners in the label. A label is a single line, so anything long pushes the map out of shape. Put owners, dates and the done condition in the rich note.
• Risks written as feelings. "Payments might be slow" cannot be mitigated or tracked. Write the cause and the effect, then give each risk a child under Mitigations.
• Exporting before arranging. Auto-arrange with A first, otherwise the exported file carries your manual positions and the reader sees a map that looks broken.

Frequently asked questions

Which branches should I keep for a small project?

Keep Goals, Scope and Timeline for nearly everything, because they answer what success is, what you are not doing and when it lands. Add Team once two people share the work, and add Risks when something expensive could go wrong. A solo weekend build can run on three branches and still beat a flat list of tasks.

How do I attach an owner to a milestone?

Open the rich note on that branch with Add / edit note and write the owner, the date and the done condition as a bulleted list. Use a child node when the same owner appears on several milestones, so the name is changed in one place rather than in three separate notes.

Can I share the plan with my team as a link?

No. Canvasola has no published links and no live editing, so the plan travels as a file: export OPML 2.0 or a plain-text outline and send it yourself, or share the .canv project file with people who use Canvasola. If two people edit copies, the merge is manual.

How many nodes does a project plan need?

A small plan sits comfortably between 20 and 40 nodes. A single map holds up to 2,000 nodes and a label up to 8,000 characters, so the ceiling is never the constraint. If one branch has more than about six children, it is really two branches that never got separated.

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