Mind Maps versus Concept Maps
🔥 Mind Maps and Concept Maps are fundamentally different information mapping methods. The most significant differences are that:
1. Mind maps are hierarchical, with subjects and sub-subjects all connecting from a main (or central) subject. Links are not named and not directional, just connecting subjects hierarchically (and never laterally). Links between subjects are not directional or named.
Many individual or collaborative uses.
2. Concept maps are not hierarchical, subjects can be connected to one or multiple other subjects not necessarily hierarchically. Links are directional (one-way or two-ways), and their function is named (unlike in a mind map).
Uses: modelling, organising and representing knowledge.
X
Welcome to the Mind Mapping forum. The topic being discussed here is: "Mind Maps versus Concept Maps".
Log in
|
|
|
|
|
|
2 |
|
Nick Duffill, United Kingdom
|
|
White Paper on Mind Maps and Concept Maps
I have a paper about the differences and different uses at harportconsulting.com. In essence, concept maps are designed for visualizing and communicating knowledge, while mind maps are better at capturing information in a personal way.
Hierarchy has much less influence in concept maps. By convention, top-level ideas are drawn at the top of the map, but in practice there is not a strict ranking of concepts further down. Cross-tree links are considered a good sign of the ability to relate concepts in different domains.
Moreover, in a Concept Map, concepts are always connected together through linking texts. There are no unexplained connections in a Concept Map. This is more rigorous than Mind Maps, because propositions are clearly visualised. A proposition is a pair of concepts, connected in a given direction by "linking text" which explains how they are related. A concept may be connected to many others in the same map, helping to define its scope and clarify its meaning.
Mind maps in fact can include cross-tree links and this is supported by most Mind Mapping software. Cross-links are commonly used to denote dependencies in maps containing tasks.
|
|
|
|

|