Overview
A concept map lays out the concepts in a domain as nodes and connects them with labelled arrows that name the relationship — ‘causes’, ‘is part of’, ‘depends on’. Unlike a mind map, which radiates from one centre, a concept map is a network, and the labels on the links carry as much meaning as the nodes.
It is a tool for understanding structure. Building the map forces you to articulate exactly how things relate, which surfaces gaps and misconceptions in your own understanding — the act of mapping is itself the learning.
When to use it
Learning or explaining a complex topic, or aligning a team on how parts of a domain fit together.
How to use it
List the key concepts
Identify the important ideas in the domain.
Rank rough hierarchy
Place broader concepts higher, more specific ones below.
Connect with labelled links
Draw arrows and name each relationship explicitly.
Add cross-links
Connect concepts in different branches to show how the domain interrelates.
Revise as understanding grows
Treat the map as living — update it as you learn, and let gaps guide study.
Worked example
A new hire maps the company’s product domain: ‘users’ — create → ‘content’ — feeds → ‘recommendations’ — drive → ‘engagement’ — funds → ‘the business’. Building it, they realise they don’t understand how ‘moderation’ links in — an explicit gap that tells them exactly what to ask about next.
Common pitfalls
- Leaving links unlabelled, which loses the meaning the map exists to capture.
- Cramming in every concept until the map is noise.
- Treating it as a one-off diagram rather than a living model.
Frequently asked questions
How is a concept map different from a mind map?
A mind map radiates from a single central idea; a concept map is a network with labelled relationships between many concepts.
Why label the links?
Because the relationship (‘causes’, ‘depends on’) is where much of the meaning lives — unlabelled arrows lose it.
Is it mainly for learning?
It is excellent for learning and for aligning a team on how a domain fits together.