| name | grinde-mapper |
| description | Creates GRINDE-style mind maps for higher-order learning and deep encoding. Use when organizing concepts, creating study notes, mapping relationships between ideas, visualizing knowledge structures, or when user mentions mind maps, concept maps, or note-taking. |
| allowed-tools | Read, Write, Edit |
GRINDE Mind Map Creator
Based on Dr. Justin Sung's methodology, GRINDE maps are optimized for learning and encoding, not just visualization.
Why GRINDE Over Traditional Mind Maps?
Traditional Buzan-style mind maps are hierarchical and radial. GRINDE maps are:
- Flexible - Non-hierarchical, chunks can go anywhere
- Learning-focused - Designed for deep encoding
- Scalable - Works for complex topics
- Higher-order - Supports analysis, evaluation, creation
The 6 GRINDE Principles
G - Grouped
What: Organize information into logical chunks using visual containers (boxes, circles, clusters)
Why: Chunking reduces cognitive load and creates meaningful units
How:
- Group related concepts together
- Use boxes, circles, or boundaries
- Each chunk should be a coherent unit
- Typical map has 4-8 major chunks
Example:
┌─────────────────┐ ┌─────────────────┐
│ CHUNK A │ │ CHUNK B │
│ - Related 1 │ │ - Related 1 │
│ - Related 2 │ │ - Related 2 │
│ - Related 3 │ │ - Related 3 │
└─────────────────┘ └─────────────────┘
R - Reflective
What: Pause to ask meaningful questions as you map
Why: Transforms passive note-taking into active thinking
Key Questions:
- "Why does this matter?"
- "How does this connect to what I already know?"
- "What's the significance of this relationship?"
- "What would happen if this were different?"
How:
- Don't just transcribe - think
- Add "why?" notes to your map
- Include your own insights
- Mark areas of confusion for later
I - Interconnected
What: Draw meaningful connections between concepts across chunks
Why: Learning is about relationships, not isolated facts
How:
- Look for connections BETWEEN groups, not just within
- Ask: "How does this relate to that?"
- Create a web, not isolated islands
- The more connections, the stronger the memory
Example:
┌─────────┐ ┌─────────┐
│ Chunk A │────────►│ Chunk B │
└────┬────┘ └────┬────┘
│ │
│ ┌─────────┐ │
└───►│ Chunk C │◄───┘
└─────────┘
N - Non-verbal
What: Use symbols, doodles, sketches, and visual elements instead of words
Why: Visuals are processed faster and remembered better than text
How:
- Replace words with icons where possible
- Use simple sketches (stick figures are fine)
- Develop personal symbol vocabulary
- Spatial arrangement conveys meaning
Symbol Ideas:
★ = Important/Key concept
? = Need to clarify
! = Insight/Aha moment
→ = Leads to/Causes
↔ = Bidirectional relationship
⚡ = Conflict/Tension
∴ = Therefore/Conclusion
≈ = Similar to
≠ = Different from
⟳ = Cycle/Loop
D - Directional
What: Show cause-effect relationships, flow, and process direction
Why: Understanding direction reveals mechanism and causality
How:
- Arrows should have MEANING
- Show cause → effect
- Indicate process flow
- Represent hierarchy where it exists
Direction Types:
A ──────► B (A causes/leads to B)
A ◄─────► B (Bidirectional relationship)
A ──┬──► B (A leads to both B and C)
└──► C
A ──► B ──► C (Sequential process)
E - Emphasized
What: Visually highlight the most important concepts and relationships
Why: Not all information is equally important; emphasis creates hierarchy
How:
- Make key concepts larger or bolder
- Use color or shading for importance
- The "backbone" should be immediately visible
- De-emphasize supporting details
Emphasis Techniques:
★★★ CRITICAL ★★★ (triple stars for most important)
★★ Important ★★ (double stars)
★ Notable ★ (single star)
(supporting detail) (parentheses for minor)
Output Format for Text-Based GRINDE Maps
When creating maps in text, use this structure:
═══════════════════════════════════════════════════════════
★★★ CENTRAL TOPIC ★★★
═══════════════════════════════════════════════════════════
┌─────────────────────────────────────┐
│ ★★ CHUNK 1: [Name] ★★ │
│ │
│ • Key point A │
│ • Key point B │
│ └─► Sub-detail │
│ • Key point C │
│ │
│ Why it matters: [insight] │
└──────────────────┬──────────────────┘
│
│ causes/enables
▼
┌─────────────────────────────────────┐
│ ★ CHUNK 2: [Name] ★ │
│ │
│ • Point with relationship ──────────────┐
│ • Another point │ │
└─────────────────────────────────────┘ │
│
┌─────────────────────────────────┘
│ connects to
▼
┌─────────────────────────────────────┐
│ CHUNK 3: [Name] │
│ │
│ (supporting details here) │
└─────────────────────────────────────┘
═══════════════════════════════════════════════════════════
BACKBONE: [1-sentence summary of the core insight]
═══════════════════════════════════════════════════════════
Map Creation Process
- Survey - Skim content first to identify major chunks
- Central Topic - Write the main topic prominently
- Chunk - Identify 4-8 major groupings
- Connect - Draw relationships between chunks
- Reflect - Ask "why?" and add insights
- Emphasize - Mark the most important elements
- Review - Check: Can you explain this from the map alone?
Common Mistakes to Avoid
- Linear notes in boxes - Just boxing text isn't grouping
- Too many words - Strive for symbols and brevity
- Islands without connections - Everything should link somehow
- No emphasis - If everything is important, nothing is
- Passive transcription - Must reflect and add insight
Additional Resources
