Knowledge Map Navigation¶
Create and use a map of a knowledge domain so people can locate concepts, gaps, dependencies, and learning paths.
The Diagnostic Story¶
Symptom: The knowledge exists somewhere, but people cannot find it, sequence it, or know where they are in it. Search returns items but not orientation. People skip prerequisites because the dependencies are invisible, then hit walls they do not understand. Different audiences enter the domain with different goals and all of them wander, reinvent things already documented elsewhere, or browse into dead ends.
Pivot: Convert the scattered or opaque collection into a navigable structure: define useful concept nodes, type the relations between them, create multiple entry points for different goals, mark gaps explicitly, and validate whether real users can actually move through the domain toward their objectives.
Resolution: Orientation improves because the structure of the domain is visible rather than implied. Sequencing becomes reliable because dependencies are typed and followable. Gaps stay visible rather than silently misleading, and the map remains maintainable without replacing the judgment of people who use it.
Reach for this when you hear…¶
[medical education] “Students keep asking why they are learning this before they understand where it fits — we need a concept map so they can see the dependencies before they hit them.”
[software onboarding] “Every new engineer spends two weeks rediscovering things that are already written down somewhere in Confluence — the information exists but the structure does not.”
[scientific literature] “I can find papers but I cannot find out what is settled, what is contested, and what nobody has actually looked at yet.”
Mechanisms / Implementations¶
- Concept Map: An informal node-and-link sketch that surfaces the concepts in a domain, the labelled relationships between them, and the connections still missing — before any formal structure is fixed.
- Curriculum Map: A program-level chart that lays out the units of a course of study, the outcomes each serves, and the prerequisite order that binds them into a coherent whole.
- Documentation Navigation Map: A wayfinding layer over a body of documentation — entry points, guided routes, and cross-links that let a reader get around instead of searching blindly.
- Domain Map: A one-glance overview that draws the outer edge of a whole field, divides it into major regions, and marks where a newcomer can sensibly enter.
- Knowledge Gap Register: A maintained list of the known holes in a body of knowledge — each gap named, evidenced, owned, and scheduled for revisiting so the blank spaces don't stay invisible.
- Knowledge Graph: A machine-queryable web of typed entities and relations you can traverse — following links from one concept to another to discover connecting paths a flat list would hide.
- Learning Path Guide: A goal-directed route through a body of knowledge that starts from where the learner already is and climbs at a manageable difficulty toward a chosen destination.
- Map Navigation User Test: A usability test that hands real users a goal and watches whether the map actually gets them there — turning wayfinding failures into evidence for revision.
- Ontology Map: A structured picture of a domain's entities, their types, and the boundaries between them — drawn so that definitional disagreements become visible and negotiable.
- Prerequisite Tree: A dependency diagram showing what must be understood before what — its roots the safe places to start, its depth the climb in difficulty.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Mental Model: Internal system representation.
- Schema: Structured knowledge framework.
- Search and Retrieval: Locate and extract information.
Also references 7 related abstractions
- Cognitive Load: Mental effort.
- Ontology: What exists and how entities relate.
- Problem Space: Range of possibilities.
- Representation: Model complex ideas.
- Scaffolding: Temporary learning support.
- Task Interdependence: Tasks rely on each other.
- Transfer of Learning: Apply knowledge across contexts.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Learning Path Navigation · domain variant · recognized
Uses a domain map to sequence learning through prerequisites, examples, milestones, and transfer checks.
Research Landscape Navigation · domain variant · recognized
Maps a research field so people can locate debates, methods, evidence clusters, contradictions, and open questions.
Documentation Wayfinding · implementation variant · recognized
Organizes documentation so users can navigate by task, question, role, error state, or prerequisite rather than browsing a flat corpus.
Dependency-First Knowledge Navigation · subtype · recognized
Builds navigation around prerequisites, dependency order, and blocked paths rather than around topical similarity.
Gap-Oriented Knowledge Navigation · risk or failure variant · recognized
Uses a map to reveal missing, weak, contested, or outdated regions so inquiry or maintenance can be directed.