Deciding where a concept sits in a structure forces a judgment that reading never requires. The cognitive work happens during construction — the decisions about what connects, which relationship type to use, and why one chunk matters more than another. A mindmap built by copying structure from a source is reorganized notes. A mindmap built by actively evaluating importance, testing relationships, and revising the structure is a schema.
Building the Map
Start with 3–7 big chunks. These are hypothetical — do not commit to them. Arrange them so the relationships and flow between them are visually clear; this backbone is the most important thing on the map. Add sub-concepts and sub-chunks, always relating each new addition back to the big picture. Add details last. Highly specific facts with no relational connections belong in flashcards, not on the map.
Practical tips:
- Leave space early. Place the first chunks far apart so sub-chunks have room to grow.
- Make the backbone obvious. The main flow of relationships between the largest chunks should be visually dominant.
- Treat everything as provisional. Do not overly commit to a first structure. Revise when a better perspective emerges.
Chunking by Importance
Chunking by surface similarity is not enough. The similarities must be important enough to justify grouping — which requires evaluation, not just pattern recognition.
Finding the right chunk often means finding the root reason something matters, not the immediate reason. The “So what?” approach works: each time a reason for importance is found, ask “so what?” until the question no longer makes sense. The answer at that point is usually broader, more connective, and produces a better chunk name than the one that came first.
The first chunk structure is almost never the simplest it can be. Always assume there is a missing perspective or a simpler way. Finding it is difficult. Find it anyway.
Arrows vs. Lines
Arrows force explicit articulation of relationship type. Lines only acknowledge that a connection exists. The same set of nodes connected by lines can support dozens of different relational structures — arrows make those differences visible and force a choice about what the relationship actually is.
- Use arrows whenever the relationship has directionality, causation, sequence, or hierarchy. Different arrow types encode different relationship qualities: one-way, two-way, or grouping.
- Use lines only for lower-level detail where component facts genuinely co-exist without meaningful directionality.
Default to arrows. Defaulting to lines is the lower-processing option and should be a deliberate choice, not a habit.
Signs You’re Doing It Right
- New relationships and chunks become easier to see as the map grows — the existing structure generates the next move.
- Each piece connects visibly to the big picture.
- The map feels messy and confusing at first, then organizes as understanding improves.
- The structure gets refined and revised repeatedly.
- Higher-order thinking is active throughout: comparing, evaluating, prioritizing.
Common Failures
- No clear backbone. The biggest chunks are not visually dominant and the main flow is unclear.
- Too many branches from a single node. More than four usually means further chunking is possible.
- Chunking by surface similarity. Groups that share a feature but not an important reason to be grouped together.
- Lines instead of arrows. Relationships are acknowledged but not defined.
- Treating the first structure as final. Early chunk structures are hypotheses. Revision is the process, not a sign of failure.
- Spiderwebbing. Chaotic, crossing arrows produced when relationships are identified after chunks are fixed. See below.
Spiderwebbing
Spiderwebbing occurs when chunks are formed first — usually by following the textbook or lecture hierarchy — and relationships are added retroactively. The structure inherits the source order (called waterfalling: all connections flow downward in a fixed hierarchy with no lateral relationships), and when lateral relationships are then forced in, arrows cross everywhere and the map becomes unworkable.
The fix is to reverse the sequence: identify relationships before committing to chunks. Start with a flat list of keywords extracted from all available sources. Find relationships and similarities between them. Evaluate which groupings are most important. Let the chunks emerge from that evaluation rather than from the source structure.
Checklist for avoiding spiderwebbing:
- Regularly check that the overall chunk structure is the simplest and most intuitive — not just locally coherent.
- When arrows become chaotic, ask whether nearby concepts could be brought into the same chunk.
- Avoid committing to a chunk structure early; stay open to restructuring as more of the topic becomes clear.
- Evaluate each arrow: is this relationship important enough to show? What is its direction and type?
GRINDE: The Refinement Standard
GRINDE is the checklist applied during the Skin step to bring a mindmap to its final form. Each letter names a quality the finished map should have.
- Grouped. Information is chunked by importance, as outlined above. The backbone is clear and the layers are organized.
- Reflective. The order of relationships, logic, concepts, and details reflects how your brain actually understands the topic — not the order the source presented it. Layers should be explicit: backbone/logic → concepts → important details.
- Interconnected. Arrows connect within layers as well as between them. Watch for the wheel and spokes failure: good chunking radiating from a central hub with no lateral connectivity between chunks. A well-interconnected map has a clear web, not just branches.
- Non-verbal. Doodles, visuals, and minimal words. Images encode more than text. Develop a personal shorthand and abbreviation system for recurring terms.
- Directional. A clear flow showing how concepts influence other concepts. Direction comes from treating the first logic layer as importance-based and maintaining the big picture throughout.
- Emphasised. Visual hierarchy is made explicit through size, color, or font weight. The main logic layer, concepts, and sub-concepts should be distinguishable at a glance. This is not decoration — it forces explicit judgment about what is most important and speeds up retrieval during revision.