Mindmaps

The first marks on a mindmap are three to seven guessed chunks, placed far apart so the relations show and the next layer has room, then redrawn once a better grouping appears. Headings copied off a table of contents and given branches stay notes in a new shape. The work is those decisions.

Building the map

The first marks are three to seven big chunks, treated as guesses rather than commitments. That range is this system’s starting heuristic, not a finding about how much a head can hold. The chunks get placed so the relations and the flow between them are visible at a glance. That backbone is the most important thing on the page.

Sub-concepts come next, each one tied back to the big picture as it lands, in the same sequence Layers of Learning uses on any other page: backbone, then concepts, then important details last. A highly specific fact with no relational hook does not belong on the map. It belongs in Flashcards, and it is tested later through Spaced Interleaved Retrieval.

Space is planned, not discovered. The first chunks sit far apart so the next layer has room to grow. A map that cannot be cleaned usually started with those first chunks packed close, so everything after had to be threaded between them. A long link that weaves between other nodes is hard to remember as a relation. The repair is to move the point, not to route the line: related nodes sit physically near each other so the link is short. Proximity is a form of the relation, not a layout preference.

The backbone stays visually dominant. Everything on the page stays provisional. A first map is expected to come out tangled. The second pass is where the spatial work happens, and that pass is planned for rather than tolerated. Rearranging is not a loss of the first map’s work. It regularly surfaces a chunk that did not exist in the first version — a pattern invisible while the content was still being placed.

A copied map is readable on sight. Arrows added after the content was written run through words, take long detours around nodes that were placed first, and cross each other. A map whose relationships were decided first has short, direct links, because the nodes were positioned to make them short. The failure is near-universal for a simple reason: content is easy to place, so it gets placed first, and the relationships are then fitted into whatever space is left.

Importance, then arrows

Grouping by surface similarity is not enough. The similarity has to matter enough to justify the group. Novices group by surface features; experts group by principle. Finding the right chunk often means finding the root reason something matters, not the immediate one. Ask “so what?” until the question no longer makes sense; that answer is usually a better chunk name. Genetic diversity matters because it produces variation — that is the immediate reason. What variation buys is survival. Survival is the better name: broader, able to hold more under it, easier to form relations to and from. The full craft of that move lives on Importance-Based Chunking.

The first chunk structure is almost never the simplest it can be. A missing perspective, or a simpler way, is assumed to be there. Finding it is difficult. Find it anyway. Groups do not have to be the source’s groups, or anyone’s official ones. A grouping earns its place by making the topic easier to hold.

One common miss is justifying a node by what it produces rather than by what gave rise to it. That miss is owned by Reverse Causality; this page only names it.

Arrows force a decision about what kind of relationship is there. Lines only acknowledge that a connection exists.

Five nodes joined only by plain lines.

Every directed arrangement over those same five — one way, the other way,
both ways, a bracket that groups rather than points — is consistent with
that picture. The lines are true, and they hide every distinction that mattered.

The vocabulary in use is one-way, the reverse, double-headed, a bracket for grouping, and the deliberate plain line. Choosing among them is the processing. The choice cannot be made without deciding what kind of relationship is there. A plain line is the right call at the lower levels of detail, where a chunk splits into component facts that genuinely co-exist without direction. Default to arrows. Defaulting to lines is the lower-processing option, and it should be a deliberate choice rather than a habit.

The failure family

The three named failures are one condition with three faces: no lateral relationships, seen from different angles.

Doing it right is checkable on the page: new relations get easier to see as the map grows, each piece still connects to the big picture, and the first version is messy and then organizes. The common failures are a missing backbone; more than about four branches from a single node, which this system treats as a sign that further chunking is available rather than as a working-memory finding; chunking by surface similarity; lines where arrows were needed; treating the first structure as final; and the three faces below.

Spiderwebbing is chunks formed first — usually taken straight off a source’s headings — with relationships added afterwards. The layout was never built to hold those relationships, so the arrows scatter, run long detours, and cross. The name comes from how the links look strung between branches. The cost lands four ways: the map takes longer to make, holds less, loads working memory while the layout is being fought, and is frustrating enough that mapping gets abandoned as a technique that “does not suit” the person doing it.

Waterfalling is the same condition seen from the other side. All connections flow downward in a fixed hierarchy, with no lateral relationships. When laterals are then forced in, the arrows cross and the map becomes unworkable. The second face of the same condition is everything funneling through one central node. The consequences are specific. Maps of unrelated topics come out looking identical to each other. Every terminal fact has to be memorised, because nothing in the structure holds it.

Wheel-and-spokes is that funnel with one hub. Chunking can be good and the map still fails, because every arm hangs off the centre and none of the arms touch.

The repair, in order: flatten the source’s headings into a plain list of keywords. The flattening is what breaks the source’s framing. Find the relationships and similarities across the list. Judge which of those similarities matter enough to group by. Let the chunks fall out of that judgement. Chunks appear at this stage that were in no heading of the source.

A map already built does not have to be thrown away. Find the chunk carrying the highest density of connections and re-chunk it. Grouping the concepts that all connect to that node removes the need for most of the lines, and it preserves every relationship already found. The four standing checks against the family: whether the current structure is the simplest and most intuitive one available; whether chaotic links can be brought closer or into the same chunk; whether a structure has been committed to too early; whether each link is necessary, and what kind of relationship it is expressing.

Chunking in the source’s own shape is the most common origin of the whole family, because the shape arrives already looking logical. Non-Linear Note-Making owns the delay that keeps that shape from being written down as if it were the chunks.

The finishing check

GRINDE is this system’s six-point check, applied during the Skin step of Bear Hunter System, that a finished map is grouped, in the learner’s order, laterally linked, spare with words, flowing, and visually ranked. It is a house checklist defined by those six qualities, not a published construct.

Letter	What it checks
Grouped	Chunked by importance. Backbone clear. Layers in order. A node carrying more than about four branches is a node with more chunking still available in it — a sign, not a law.
Reflective	The order of relations, logic, concepts, and details is how the topic is understood, not the order it was presented. Layers run backbone, then concepts, then important details. A map that reproduces the source’s numbering comes out looking like a family tree: chunked, tidy, and still the lecture.
Interconnected	Arrows connect within layers as well as between them, and only where a real relationship exists. Arrows added because two words sit near each other are not connections. A map can fail this check by having too many links as easily as too few.
Non-verbal	Fewer words leave the structure visible instead of buried under text. A mark that stands for the idea is the target. Drawing everything is not.
Directional	A clear flow of how concepts influence other concepts. Direction can only be drawn once a decision has been made about which of two things outranks the other.
Emphasised	Visual hierarchy by size, colour, or weight. The emphasis forces an explicit ruling on which relationships matter most, and it lets the backbone be picked out at a glance on every later pass.

The mark under Non-verbal has to distinguish, not decorate. A set of drawings that all look alike is worth no more than the words were. A symbol earns its place when it carries the attribute — a shape drawn to say strong, a small sun inside a letter to say this phase is the relaxed one.

A map built in the right order comes out visibly lopsided: the region drawn first is neater and denser, later additions trail off in one direction. That skew is a side effect of building from the backbone outward, and it is a good sign rather than a defect. The finishing audit runs letter by letter and comes out with named improvements — this cluster needs another level of grouping, this region needs a mark instead of a word, this main line needs to be heavier. A finished map is a map whose remaining faults have been named.

Links do not cross. Where two must, one of the points is in the wrong place: pull it out rather than routing the line around the obstruction. Take out what has become obvious. Facts written down early are, by the end of the topic, things that will not be lost, and they can leave the map. Other facts leave because they never connected to anything. Those are two different exits. Finishing does not remove information; it changes what can be seen. Overlapping chunks, when spotted — the same material admitting two valid groupings at once — add a dimension rather than a contradiction. No copy-pasted diagrams. No lined or cramped paper, if the surface can be chosen.

Research Foundations

What the reachable record supports is learner-constructed concept mapping against conventional study, with the effect larger for construction than for studying a map somebody else built. That finding is this page’s operating claim measured from the outside. The radial-diagram brand of mind mapping is the weaker literature — small, mixed studies. The evidence sits with maps built by the learner with labelled, directed relationships, not with the radial format as a format. Dual coding supports a mark alongside words. It does not support a blanket claim that images encode more than text.

Finding a better chunk structure is slow and heavy. Re-chunking a topic is a real second pass. It loads working memory while the old structure and the candidate one are held together, and the first several attempts at a topic feel wrong before the move transfers. What it buys, in the same breath: a structure that expresses the same relationships with far fewer links, and one unique enough to a topic to be memorable.

A finished map is not evidence that anything was learned. A map made without the deciding is worth no more than any other notes, and it costs more to make — which is exactly the experience behind “mind maps don’t work for me.” A second honest failure: a map can prioritise relationships so hard that the detail never arrives, leaving a clean shape with too little in it.

Two quit signals, each with a next move. If the nodes on a finished map cannot be justified, the drawing is not the problem — stop mapping and go back to deciding importance. If a large share of a topic is lost when it is tested from memory, suspect the structure rather than memory: check the map for the funnel and the scatter, and re-chunk the densest node.

Three things should be checkable on the page itself: new relationships get easier to see as the map grows, the map comes out skewed, and what is left to memorise outright is a small set of specific facts rather than the topic. How wide to build that structure is the job of Best-attempt Encoding.

The deciding is the encoding. A finished page says which order the work ran in. Short, direct links, a visible backbone, a lopsided first region, leftovers off in flashcards: the map was built by judging. Arrows that run through words, detour, and cross: the headings were placed first. The simpler perspective, once found, is visible the same way.

Open Questions

How far a typed map can carry the same deciding, now that paper is no longer the default surface.

Related

• Bear Hunter System — the encoding loop whose finishing pass this checklist serves.
• Deep Processing — the parent dimension: encoding that changes the structure, not the volume.
• Importance-Based Chunking — what “grouped by importance” actually is; this page keeps one instance and sends the craft.
• Spaced Interleaved Retrieval — where leftover unconnected facts go, and how the finished map is tested.
• Best-attempt Encoding — how wide to build the schema.

Sources

• Nesbit, J. C., & Adesope, O. O. (2006). Learning with concept and knowledge maps: A meta-analysis. Review of Educational Research, 76(3), 413–448. Learner-constructed concept mapping against conventional study, d ≈ 0.46; the effect is larger when learners construct rather than study a provided map. Supports the page’s operating claim from the outside.
• Chi, M. T. H., Feltovich, P. J., & Glaser, R. (1981). Categorization and representation of physics problems by experts and novices. Cognitive Science, 5(2), 121–152. Novices group by surface features, experts by principle — the supported basis for chunking by importance rather than by resemblance.
• Farrand, P., Hussain, F., & Hennessy, E. (2002). The efficacy of the ‘mind map’ study technique. Medical Education, 36(5), 426–431. Small and mixed. The weaker literature around the radial-diagram brand, cited as the bound rather than as support.
• Paivio, A. (1991). Dual coding theory: Retrospect and current status. Canadian Journal of Psychology, 45(3), 255–287. A mark alongside words has a trace of its own. The theory does not license “images encode more than text.”