Concept Map¶

Artifact — instantiates Knowledge Map Navigation

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.

A Concept Map is a loose diagram of boxes-and-labelled-arrows that a person or group draws to externalize how the pieces of a subject hang together: each box is a concept, each arrow carries a linking phrase ("causes", "is a kind of", "requires") that names the relationship. Its defining trait is that it is informal and generative — it exists to think with, not to certify. Because the relationships are spelled out in plain language rather than a fixed type system, contradictions, redundant concepts, and above all missing links jump out the moment the sketch is laid flat. That is the whole point: a Concept Map is where a fuzzy sense of a domain becomes an explicit, criticizable picture that a more formal representation can later be built on — or that simply helps someone see the shape of what they are learning.

Example¶

A nursing student trying to understand heart failure keeps memorizing isolated facts that won't cohere. Following the concept-mapping technique from science education,^[1] she puts "reduced cardiac output" in the centre and starts drawing arrows outward — reduced output → triggers → renin-angiotensin activation → causes → fluid retention → worsens → congestion. Laying the pieces down this way, she sees a box she can't connect: she has "beta-blockers" floating with no labelled link to anything. The gap is the insight. It tells her she has memorized a drug without knowing where in the causal web it acts — so she goes back to the text with a precise question instead of re-reading the whole chapter. The finished map isn't a reference she'll query later; it's the byproduct of having actually understood how the concepts relate, and the blank arrows are her to-do list.

How it works¶

The map is built by iterative externalize-and-critique, not by filling a template:

Name concepts as nodes. Pull the domain's concepts out as discrete boxes, deliberately including half-formed ones.
Connect with labelled arrows. Every link must carry a linking phrase; the discipline of naming the relationship is what forces latent knowledge into the open and exposes where you can't name it.
Read the sketch for holes. Unconnected nodes, one-way relationships that should be reciprocal, and clusters that "should" touch but don't are read directly off the diagram as candidate gaps.
Redraw. The map is cheap to throw away and redraw; each pass tightens the vocabulary and merges duplicates.

What distinguishes it from its formal cousins is that nothing here is typed or validated — the informality is a feature that keeps the cost of being wrong near zero.

Tuning parameters¶

Formality of the link vocabulary — free-text linking phrases keep it fast and generative; a constrained set of verbs makes maps comparable across people but starts to harden into an ontology.
Authorship — a solo map captures one head's model quickly; a co-drawn map surfaces disagreement but slows to the speed of negotiation.
Scope per map — one tight sub-topic stays legible; a whole-domain sprawl shows more connections but becomes an unreadable hairball.
Lifespan — treat it as disposable scaffolding to be redrawn, or preserve it as an evolving reference (at which point stewardship and update discipline start to matter).

When it helps, and when it misleads¶

Its strength is revealing structure and absence cheaply: it is one of the fastest ways to make tacit understanding visible and to locate the exact places a mental model is thin. It is invaluable at the front of learning something new or scoping an unfamiliar domain, precisely because it does not demand rigor it can't yet supply.

Its failure mode is being mistaken for more than a sketch. Informal linking phrases are ambiguous — the same arrow can mean different things to different readers — so a Concept Map does not support querying, inference, or governance, and treating a pretty one as an authoritative model imports errors that were never checked. The classic misuse is reverse-drawing: producing a tidy map after the fact to look like understanding rather than to build it. The discipline that keeps it honest is to keep it disposable and force every link to carry an explicit phrase — the moment you want typed relations, precise boundaries, or a queryable store, you have outgrown this mechanism and should promote it to a formal sibling.

How it implements the components¶

A Concept Map fills only the informal, generative slots of the archetype's machinery:

concept_node — each box is a concept surfaced as a discrete, nameable entity.
relation_edge — the labelled arrows are its relationships, carried as plain-language linking phrases rather than typed edges.
gap_marker — unconnected nodes and missing arrows are read straight off the sketch as the domain's blank spots.

It does not draw formal type boundaries (cluster_boundary — that's Ontology Map), make its relations machine-queryable (cross_reference_bridge — that's Knowledge Graph), or maintain gaps as an owned worklist (map_steward, map_update_rule — that's Knowledge Gap Register).

Instantiates: Knowledge Map Navigation — the Concept Map is the informal, first-pass sketch of a domain's structure.
Sibling mechanisms: Ontology Map · Knowledge Graph · Domain Map · Research Landscape Map · Documentation Navigation Map · Learning Path Guide · Curriculum Map · Prerequisite Tree · Knowledge Gap Register · Map Navigation User Test

Notes¶

A Concept Map is often the seed of a formal representation, not a rival to it: the entities and relations it surfaces can be promoted into an Ontology Map's typed structure or a Knowledge Graph's queryable store once they stabilize. Keeping it explicitly informal is what lets it stay a cheap thinking tool rather than a half-built database nobody trusts.

References¶

[1] Concept mapping as a structured node-and-linking-phrase technique was developed by Joseph D. Novak and colleagues in science education research; the linking phrase — naming the relationship on every arrow — is the feature that distinguishes it from a free-form mind map. ↩