A fitness goal mind map you can review weekly

Define the measurable target

"Get fitter" cannot be checked, and a target you cannot check cannot drive a week. Put the target in the root node as three things: a number, a date and where you are now. "Run 10 km without stopping by 30 March, currently 6 km" is a target, and it is one that survives a bad fortnight because you can still tell whether you are closer.

The Personal Goals starter is one of thirteen templates in the gallery, and it gives you a shape you can rename, fill in or delete, which is useful when the blank page is the real problem. Write your own target in your own words afterwards, because a template's phrasing will not match the way you talk about your own training. The template gallery guide lists what the other starters are for.

• A number, a date and a current baseline in the root node
• Someone else could tell you in a month whether you hit it
• Rewrite any template wording in your own words
• One sentence, written the way you would say it out loud

Break the goal into weekly sessions

A goal becomes real when it is divided into sessions you could actually do on a Tuesday. Divide by the week rather than by the whole programme: three sessions a week for eight weeks is a plan, and twenty-four sessions is only a total. Put the weekly number in a child node and the reason you chose it in the note, because the reason is what you will need when a week goes wrong.

Give every session branch a capacity, the way the day branches in the travel itinerary map each carry a budget of hours and travel time. "Three sessions, forty-five minutes each, evenings only" is a constraint you can plan around. A session with no length and no time of day becomes the session that gets skipped.

Plan the first week around a week you have already lived. Eight sessions in the first week looks heroic on a map and never happens, and a missed first week is where most goals quietly end. Start with a week you could repeat, then let the log tell you when the plan can stretch.

• Divide by the week, not by the whole programme
• Every session has a length, a time of day and a place
• Plan a first week you could actually repeat
• Sessions are branches, so the map shows the shape of the training

Name the habits that carry it

Sessions are events and habits are the repeatable things that produce the events. Name them plainly: train at six on Tuesday and Thursday, kit ready the night before, protein breakfast before every session. A habit node should be small enough that you can answer it with yes or no, because a habit you cannot check is an intention.

Cross-link each habit to the sessions it supports, so a missed habit shows you exactly which sessions it costs. The link appears as a tube between the two nodes and there is no label editor for it, so write the relationship in the note of the habit, for example "missing this costs the Thursday session". The cross-links guide shows how the tubes behave.

• Three to five habits, each answerable with yes or no
• A cross-link from every habit to the sessions it supports
• Write what a missed habit costs in the note
• A habit with no session attached is a wish, not a habit

Log what actually happened

Add a log branch and give it one child per session, with the date in the label and the details in the rich note: what you actually did, how long it took and how it felt. Keep the log on the same map as the plan, because the comparison between the two is the entire point, and separating them means you stop comparing at all.

As the log grows the map sprawls, and sprawling is when a map stops being read. Press A to auto-arrange, which clears your manual positions and re-runs the layout so the branches settle back into a readable shape after a few weeks of adding. Version history keeps 20 versions, so you can look back at how the plan looked a month ago, and the undo and history guide explains that panel.

• One child per session, with the date in the label
• Skipped sessions get a node and a reason
• A re-runs the layout when the log sprawls
• Version history keeps 20 snapshots to compare

Adjust the plan, not the goal

The weekly review has two questions: what happened, and what changes. Leave the goal in the root untouched for now and change what sits under it. Volume, time of day and session length all move; the target on the root moves only for a reason you can name, such as an injury or a schedule that has changed for good.

The reason to protect the goal is that it is the thing you judge yourself against, and a goal that moves whenever the week is bad is a goal that is never met and never failed, which is the same as having no goal at all. If the plan is wrong, the plan changes, and that is correcting the route rather than lowering the bar.

Look for the pattern rather than the week. Four missed Tuesday sessions in a row is a scheduling problem, and the fix is a different time of day, not a new goal. Write what you changed and why in the note of the session you changed.

• Two questions only: what happened and what changes
• The root target stays put while the plan under it moves
• Change the time, the length or the count rather than the aim
• Write the change and its reason in the session note

Celebrate the streak

Add a streak branch with one node per completed week, your best run so far, and a note on what each good week was like. A streak is the cheapest motivation there is and it costs nothing to record: a node per week, colored once the week is done, so the run is visible without reading a single label.

Link the streak to the thing that produced it with a cross-link to the habit that carried it. When a good week came from a habit you enjoy rather than a session you dreaded, that is exactly the information you want before planning the next eight weeks, and it is much easier to find on a map than in a notebook.

Celebrate in a way that does not create a new goal. A reward that needs its own plan and its own budget is another project, and it competes with the one you are trying to finish. A written note in the streak branch is enough.

• One node per completed week, colored when it is done
• A note on what made the good week easier
• Cross-link the streak to the habit that carried it
• Keep the record when a run breaks

A checklist you can reuse

• The root node holds a number, a date and a current baseline
• The target is stated so that someone else could check it
• The first week on the map is one you could genuinely repeat
• Every session has a length, a time of day and a place
• Three to five habits, each linked to the sessions it supports
• Skipped sessions are logged with a reason
• The weekly review changes the plan and leaves the target alone

Common mistakes to avoid

• A target nobody can check. Goals like "get fit" or "improve" cannot be marked as met or missed. A number, a date and a baseline turn an intention into something you can review.
• Planning a new programme every Monday. Starting a fresh plan each week means no plan ever gets tested. Change one thing at a time and let a few weeks of evidence decide.
• Logging only the good weeks. A log of good weeks tells you nothing, because the plan only exists in the weeks you did not want it. Record the misses and the reason for each.
• Moving the goal when a week goes badly. A target that shifts whenever the week is bad is never met and never failed. Adjust the sessions, the timing and the count underneath the goal.
• A list of ten habits. Ten habits is a second project, and it competes with the training. Keep three to five, and cut any habit that is not attached to a session.

Frequently asked questions

How often should I update the map?

Log each session on the day it happens, since the memory of a session fades within a couple of days, and review the map once a week. The weekly pass is where the plan changes: look at the misses, decide one adjustment, and write it into the note of the session you are changing.

What should I do after missing a week?

Change the plan rather than the target, and write down what you changed and why. Missing a week usually means the sessions were scheduled badly, not that the goal was wrong. A map is useful here because the log shows you the pattern across several weeks, while a bad week alone tells you very little.

Does Canvasola track my workouts for me?

No. Canvasola is a place to plan and record, and the log is a record you write by hand after each session, with no connection to a watch, a heart rate monitor or a gym system. What it does give you is the history: 20 versions of the plan, so you can compare this month with the last one.

Can I use a template instead of building the map myself?

The Personal Goals starter is a reasonable first afternoon, since it gives you branches to rename with Enter and F2, fill in or delete. Write your target and your own sessions into it rather than leaving the template wording in place, and keep the habits and the log as your own branches.

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.