Concept mapping to deepen project/product requirements Part 1

What does it mean when you say: "I understand"? Does it mean the same thing to you as it does to your customer or supplier? Wouldn't it be great if there was a way to demonstrate your understanding? Is there a way to get an inventory of the topics you need more information on?

(and obviously there is as this would otherwise be a very small blog entry)

A concept map presents the relationships among a set of connected concepts and ideas.

Constructing a concept map provides a way to expose, demonstrate, reflect on, enhance and share your understanding.  It is a tangible way to display how your mind "sees" a particular topic. By constructing a concept map, you reflect on what you know and what you don't know. In a Concept Map, the concepts, usually represented by single words enclosed in a rectangle (box), are connected to other concept boxes by arrows. A word or brief phrase, written by the arrow, defines the relationship between the connected concepts. Major concept boxes will have lines to and from several other concept boxes generating a network. This concept network could span multiple concept maps, linking them together.

Do not mistake Concept Mapping for Mind Mapping!

• Mind mapping is a graphical technique used to explore ONE central key word or idea. It uses a radial hierarchy and tree structures to denote relationships with the central governing concept.

• Concept mapping provides insight and understanding as it connects MULTIPLE ideas with their documented relationships.

Why use concept mapping?

The main reason I use concept maps is quick access, easy edits and smooth browsing of my information. The concept map works like an offline brain dump: the key elements of information with their specific relationships to each other are easily available and I can add new information or change existing information on the fly, ensuring that my concept map truly reflects my latest level of understanding.
This setup also works in teams where the digital concept map is available to add and detail information. No more fiddling with word processors and lengthy text as if you're writing an essay, just add the essential blocks of information and share with the team in an instant.  Concept mapping is - next to state diagrams [1] - my favorite knowledge visualization method. I have used it for

• documenting project and product details for internal and external partners
• gathering sufficient understanding of requirements and their influences on the whole
• capturing team knowledge
• online reference
• jotting down and analyzing new processes and production scenarios

Concept mapping earns itself back in an extreme short period of time:

• Time: Putting the information to file does not require extensive writing skills and does not force you to use a graphics application.  This will definitely save precious time.
• Quality: Most projects I ran did not have a technical writer on the team so the customer wanted the programmers to document as they worked. Big mistake! Programmers write code, not English. They comment instead of document and they will detail what THEY see fit at that particular point in time. The 'documentation' will become part of the code base or will be so cluttered with screenshots and code snippets that no one will be able to mold it into something usable.
• Budget: In one year's time, the project team will have moved on and the new hires will not be able to fully comprehend WHY stuff was coded in a certain way.  Ever tried to figure out how much time is invested by new team members to get a basic understanding of WHY stuff is done the way it is done? What time are they spending asking your senior members which are even more expensive and whose work is on the critical path?

If you feel at this point that you have no use for concept mapping, rejoice as you have reached the end of the blog.  Thanks for sticking with me!  On the oher hand, if you want to know more about concept mapping, feel free to read part 2 of this blog here.

[1] See my upcoming blog on BPM with state diagrams here