Building a topic-overview map your students will actually use

Start with a question, not a noun

The single biggest mistake is putting a noun at the centre ('Photosynthesis', 'The French Revolution', 'Differentiation'). Nouns invite an encyclopaedic dump of every fact you know, which is the opposite of what students need.

Put a question at the centre instead: 'Why is photosynthesis the engine of life on Earth?' 'What made the French Revolution unstoppable by 1789?' 'When and why do we differentiate?' Questions force a thesis. Every branch then exists to support, qualify or complicate that thesis — exactly the cognitive moves you want students to make themselves.

Teachers often resist this because it feels like opinion-pushing. It isn't. A great central question has multiple defensible answers; the map shows the major ones as parallel branches. Students are then asked to weigh evidence, not memorise positions.

The three-level rule

Limit to three levels of hierarchy: central question → major branches → supporting elements. Deeper than three and the map stops being scannable. If you're tempted to add a fourth level, that's a signal to spawn a child mind-map from one of your supporting elements — Marvex Studio supports nested maps for exactly this.

Each major branch should be a single noun-phrase or short sentence (not a paragraph). Supporting elements follow the same rule. The rule of thumb: if a element can't fit on one comfortable line at 18px type, it's two ideas, not one — split it.

Colour groups themes — it doesn't decorate

Pick three to five colours and assign them by theme, not by depth. For a history map you might use one colour for political causes, another for economic, another for social, another for cultural. Colours then carry signal: when a student sees three economic-coloured branches clustered together, they perceive an economic argument without having to read each label.

Avoid rainbow gradients (every branch a different colour). That's decoration, not signal — students can't extract anything from it.

The 7-15-60 rule of thumb

A teaching map that students will actually use lives in a tight range: 7-15 first-level branches, 30-60 total elements. Fewer than seven major branches and the topic isn't substantial enough to need a map. More than fifteen and students can't scan it in one glance.

If your draft map has 80+ elements, the topic is too broad for a single map. Carve out the densest section as its own sub-map and link to it from a parent element. This is the same principle as splitting a long book into chapters — except chapters aren't browsable in one glance, and a properly-sized mind-map is.

Three structural mistakes to avoid

Mistake 1: Symmetric branches. A real topic isn't equally weighted in every direction. If you find yourself padding a branch to make it look balanced with its siblings, delete the padding. Asymmetric maps reflect the actual importance of each sub-theme.

Mistake 2: Verbs at the centre. 'Understanding photosynthesis' or 'Studying mitosis' is a goal, not a topic. Goals don't generate branches — they're a meta-statement about what you're trying to achieve. Pull the verb out and put a question in its place.

Mistake 3: A glossary by another name. If your map is just a list of terms with one-sentence definitions, it's a glossary, not a mind-map. The relationships between terms are the entire point. Make sure every supporting element has a connection to a sibling — if it doesn't, it doesn't belong in this map.

Your first map

Open Marvex Studio, pick the hardest topic you teach, and frame it as a question. Build it live, expecting to throw the first draft away — most useful maps are the third or fourth iteration, not the first. Aim for the 7-15-60 range. Stop when adding elements stops feeling clarifying and starts feeling completionist.

Save the map. We'll come back to it in Lesson 3 and attach every resource your students need to it.