Color-Coding Your Mind Maps: A Quiet System

Most people add colour to their mind maps because it looks better. That's fine - a beautiful map is more likely to be revisited than an ugly one. But colour can do much more than decorate. With a small, consistent set of rules, colour becomes a second layer of meaning the brain reads faster than text.

The mistake almost everyone makes

People colour their branches by mood. Important things get red. New things get green. Boring things get grey. After the third map, the system collapses - what counts as important changes from chapter to chapter, and the colours stop meaning anything specific. The map starts to look like a brand-new map every time, which is a problem because your brain remembers patterns, not paintings.

Rule one: colour by role, not by importance

Pick a small set of roles that recur across your maps and assign each one a colour. Our standard palette:

• Forest green - central claim or core concept
• Slate blue - supporting evidence (data, studies, examples)
• Warm amber - actionable items, practical steps, things you'd do
• Soft grey - counter-arguments, criticisms, caveats
• Rose pink - your own reactions, questions, disagreements

Five colours. They map to roles, not to importance. After a dozen maps, your eye finds the green node and you know it's the centre of gravity. You scan the rose branches first when you re-read a map, because that's where your future questions are. The system becomes ambient.

Rule two: the palette should not exceed six colours

You can hold five colours in your head. Six is the upper limit before you start mis-identifying what's what. Seven is too many. If you find yourself wanting a seventh colour, you have a category that's actually two categories - split them and use one of your existing colours twice with different shapes (a square vs a circle, for example).

Rule three: pick a palette that survives photocopying

If you ever scan or photocopy your maps in black-and-white, your palette should still be readable. That means avoiding similar-luminance colours next to each other. Forest green and slate blue have very different luminance, which is good. Bright red and orange next to each other become indistinguishable in greyscale. This sounds pedantic until you've lost a map to a low-quality photocopy at a conference.

Rule four: colour the branches, not the text

The most legible maps colour the line between two nodes - the branch - rather than the text of the node itself. Text in black on a white background is easier to read; the coloured branch tells you the role at a glance without making the words harder to scan. This is a small detail that matters more than it sounds. Coloured text gets tiring fast.

Rule five: leave room for an unclassified branch

You will always have a branch that doesn't fit your five roles. Don't force it. Leave it black. Over time you'll notice which 'black' branches keep appearing - that's the signal for a sixth colour, if you really need one.

An aside on highlighter culture

Most knowledge workers came up through a culture of highlighters and sticky tabs. Both are usually fake-learning props - the act of choosing what to highlight feels like comprehension but rarely is. A mind map colour system is the opposite: the colour applies to a role, which forces a comprehension decision (is this evidence or claim?) every time you reach for the pen.

That decision is the work. The colour is just where it lives.

One palette, one notebook

The single best move you can make for your map literacy is to use one palette across one notebook for a season. Don't change colours mid-project. Don't try a new palette per book. Repetition is the entire point. After six weeks of consistent use, you'll be reading your old maps the way you read sentence diagrams - at a glance, in the right grammar.

You can change palettes between projects. You should not change palettes within one.