A concept map is a way of drawing what you understand about a topic so that the relationships between ideas become visible. It was developed by Joseph Novak and his team at Cornell in the 1970s, growing out of David Ausubel's theory of meaningful learning, which holds that we learn best when we connect new ideas to knowledge we already hold. A concept map is built to make those connections explicit rather than leaving them in your head.
What a concept map actually is
Four parts do the work.
Nodes are the concepts, usually a word or short phrase in a box or circle: "gravity", "interest rate", "photosynthesis".
Linking phrases are the labels written on the lines between nodes. This is the feature that sets the method apart. A line does not just say two ideas are related, it says how. "requires", "causes", "is a type of", "leads to".
Propositions are what you get when two nodes and a linking phrase combine into a statement that reads like a sentence: "plants require sunlight", "higher rates reduce borrowing". A concept map is really a network of these small, checkable claims.
Hierarchy organises the map from general to specific. The broadest concepts sit near the top and more detailed ones branch below, though the ranking further down is loose rather than strict.
Two more ideas hold it together. A focus question anchors the map: you decide up front what question the map should answer, such as "what drives inflation?", and every concept earns its place by helping answer it. Cross-links are lines that connect concepts in different branches. Novak treats these as the most valuable part of a map, because spotting that an idea in one branch relates to an idea in another is often where genuine understanding, or a new insight, shows up.
How to build one
- Pick a focus question. Without it, maps sprawl.
- Brainstorm the key concepts and list them loosely, most general first.
- Place the broadest concepts near the top and arrange the rest below them.
- Draw lines and, crucially, label every line with a linking phrase so each connection becomes a proposition.
- Look for cross-links between separate branches and add them.
- Revise. First drafts are always messy, and rearranging nodes is where the thinking happens.
When it helps, and when it does not
Concept mapping earns its cost when you are synthesising a whole topic, comparing this method against the broader family of note-taking methods, or studying how parts of a system relate. Because every link is labelled, the map exposes gaps: a concept floating with no honest connection is a sign you do not yet understand where it fits. That makes it a strong tool for studying from your notes and for remembering what you read by rebuilding structure from memory.
It is the wrong tool for fast linear capture. In a lecture or meeting you need speed, and stopping to label every relationship is too slow, so a running outline serves better. It is overkill for simple material, plain lists, or a set of steps. It can also get cluttered fast: add enough nodes and cross-links and the map turns into a tangle you can no longer read. And it is genuinely awkward on a phone, where a small screen fights against a spatial, sprawling diagram.
Concept map vs mind map
These two get conflated, but they are not the same. A mind map starts from a single central topic and radiates branches outward. Its lines are unlabelled, its structure is loosely associative, and each topic typically has one parent. It is built for fast, free brainstorming.
A concept map starts from a question, holds many concepts, and labels every connection. A concept can have several parents and children, and cross-links weave the branches together into a network rather than a starburst. Mind maps are quicker and looser. Concept maps are slower but make relationships precise. If you want to generate ideas, reach for a mind map. If you want to show how ideas relate and test whether you actually understand them, reach for a concept map. Related spatial and tabular approaches include the mapping method and the charting method.
Concept mapping is a synthesis tool, not a capture tool. Use it after you have gathered material, when the goal is to see the whole and find the gaps. If you are still deciding which approach fits your material, the guide on choosing a note-taking method can help you match method to task.