Mind Map vs Concept Map

I came across a white paper written by a software vendor explaining the differences between a mind map and a concept map.  The white paper provides a good delineation between these two terms and provides examples of when to use each type of model.

Using a knowledge management perspective, the difference between a mind map and a concept map is very important.  A mind map is used to diagram concepts within a domain and typically involve identifying connections between the main topic and contributing ideas to the main topic.  For example, I could develop a mind map where I diagram the components of an automobile.  I would begin with the automobile topic then break it down into transmission, breaking, electrical, etc components.  Each of these components could then be further broken into sub-components and so on.  This more hierarchical modeling illustrates the connections between ideas.  This is a good tool to illustrate information and many students follow this approach when taking notes or preparing for a paper.

The concept map closely resembles the mind map but includes more cross-connectivity between sub-components to create a less hierarchical structure.  Additionally, and this is important, the concept map also describes the relationships between the elements in the model.  Rather than simply drawing the relationships in the mind map, the concept map describes the relationships.  This provides the contextual insight into the model and removes any reliance on individual interpretation of these relationships.  The more complex structure and the explicit definitions of the relationships illustrates knowledge of the domain.

While both models provide benefit, the concept map provides a much more complete description of the topic and unambiguous definitions of the relations between elements in the model.  The mind map is used to convey information while the concept map is used to convey knowledge.