Logos52
wiki / Dimensions / Deep Processing / Non Linear Note Making

Non-Linear Note-Making

technique updated 2026-05-29

Non-Linear Note-Making

Notes earn their keep by prioritising relationships, which is exactly what linear, verbatim transcription throws away. Research links linear notes — especially typed, close-to-verbatim ones — to weaker learning, lower retention, and lower test scores. Done correctly, non-linear note-making is a surprisingly technical skill, which is why many learners try mindmaps, do them wrong, and wrongly conclude they don’t work.

Process before you write

The strongest single habit is delaying notes: spend time making sense of what you consumed before writing anything. Continuous note-taking feels safe and produces little learning — it removes the brain’s incentive to process. The confusion of “trying to figure it out” is uncomfortable, and that discomfort is the work; learners who use it as fuel reach a far faster, more efficient state than those who write to feel secure.

Mapping mechanics

  • Arrows, not lines. A line says “these are connected”; an arrow says how. One-way, two-way, bracketed, or deliberately-not-an-arrow each encode a different relationship — choosing forces the higher-order thinking that a bare line lets you skip.
  • Chunk first, then map. Form chunks by finding relationships and judging their importance before drawing — chunks should reflect how you processed the material, not a source’s hierarchy.

Two failure modes

  • Spiderwebbing. Chunking the way a textbook is structured, then trying to add lateral relationships afterward, produces a chaotic web of arrows — slow, frustrating, and bad for retention. The fix is to convert the source hierarchy to a flat list first, then build chunks from real relationships.
  • Reverse causality. Justifying one fact’s importance solely by another fact you must also memorise creates a closed loop (“A matters because it makes B”) that adds a memory burden instead of reducing one. Anchor importance in a wider network (A relates to C, D, and E) so each piece is logically inferable rather than rote. Intuitive chunking prevents it; importance-checklisting and simple Q&A can worsen it.

Keeping references while encoding

Non-linear encoding makes citation awkward, so run two parallel sets of notes: the non-linear map for understanding, and — every two or three sources — a short linear, cited synthesis for consolidation and reference. For reuse across projects, store the cited layer in a second-brain app.

The mechanics behind Note-Taking and Bear Hunter System Shoot; chunking quality is governed by Importance Based Chunking and Survive and Thrive.