Three basic types of map

Earlier postings have mentioned the importance of having a clear purpose for a software mind map. In this posting we will look at three basic "types" of map. Although this might seem at odds with the divergent thinking and creativity that characterises mind maps, it is important when sharing maps with others that they understand what you are trying to achieve. There are more than three basic types, but these are the scenarios that occur frequently in business life.

"Library" maps

A Library map is a collection of reference information for the purposes of

• transferring information and knowledge
• storing and recovering useful materials
• understanding or learning something

The focus of a library map is the subject. Topics can be sub-headings or statements that are expanded, and the position of a piece of information represents its relationship to the bigger subject. A common issue with Library maps is that the same piece of information "belongs" in more than one place - chairs can be classified as both furniture and as things made from wood. Not all Furniture is chairs, neither are all Wooden Things chairs. Do we put chairs under Wooden Things or furniture, or both? How do we decide? Or do we use a database instead? One solution is to decide on a major classification scheme where everything appears once, then identify other groupings with colours or icons. Other users will typically navigate the map themselves by following signposts to the resources they seek.

"Presentation" maps

A Presentation map is a story or an argument, designed to

• Inform an audience in a directed fashion
• Argue a proposition or case
• Make a call to action

The focus of a presentation map is the audience themselves, although you would not necessarily write that in the central topic. The positioning of information is relative to the audience's viewpoint, and the deeper it is in the map, the more involved they are. The development of arguments away from the centre builds on inductive thinking that justifies or amplifies higher level statements, and if your audience is still with you, then you are well placed to add more detail to the foundations you have laid. Topics near to the centre are major statements that easily connect to your audience's world view. You can see this kind of architecture in most marketing materials - the opening gambit is usually to get you to identify with a problem or issue. Presentation maps should use statements rather than headings, and should retain their integrity when viewed at different levels of detail. You can then use the same map for the two-minute briefing to the board of directors, or the two-hour version for the technical nit-pickers. Presentation maps will also need to follow a sequence, for example clockwise.

"Tunnel Timeline" maps

A Tunnel Timeline map is a map that is designed around delivering an outcome. The primary purpose of this kind of map is to visualise success. You are drawing a picture of what success looks like, and showing the actions on the path or paths to reach it. Use Tunnel Timelines for

• Project outlines and plans
• Strategies
• Problem solving

Topics at or near the centre of the map represent the successful outcome, and  topics near the edges are the next actions to take towards those outcomes. The relationship with a "tunnel" is that the map shows your project as the light at the end of the tunnel, with your next actions around the walls nearest to you. As you make progress towards the centre, you complete the actions and decisions along the way. Major milestone topics in the map should be written as outcomes to keep you focused on achievement, e.g. "reject rate is 3%" or "client has renewed contract". This is the key benefit of visualising projects in software mind maps - you stay focused on your objective and keep your eye on where you want to go, not on your short-term direction. Responding to changes and obstacles is easier if you are focused on the big target, and a continual visual reminder of objectives is a positive force. Participants in your project or strategy can see where it is headed, and can understand how their contribution takes it forward.

"Brainstorm" maps are intermediate maps ("rough working") on the way to the above structures. We will talk about brainstorming and development techniques in the next posting.

Comments

[Marc Orchant]

Great post Nick. I'd suggest a fourth map type that I use all the time - the Writer's Map. Before I begin any substantial writing project, I organize the structure of my writing project in a mind map. Often, one branch in the map will be a library map-in-miniature as you describe, containing all of my reference material for the piece.

Using a mind map to sketch out a writing project is so much more flexible than outlining it. A good mind mapping program will allow you to export to an outline when you're ready to transition to the actual draft writing.

[Iain]

Do you have any examples of these three different types of mindmaps? I have not used them enough to be able to see your classifications.

[Ben Royal]

You comments on the types of maps has clarified my thinking about expanding their use. I recently created maps during initial planning sessions with several project teams and they were well received. Maps seem to capture team brainstorming much better than linear notes.

[Marcel Geijsberts]

This is a very clear exposition how business mapping can be classified. I have been using mind maps for quite some time now (since 1996) and have seen the mind mapping software evolve in the past years (especially mind manager).

The ideas put forward here really make sense to me:
how information can be seen from visual structure and that consistency in presenting the structure is vital for getting your point across the audience (in the future).

To have different templates for different purposes seems logical; the Mind Map book by Tony Buzan shows good examples of different uses of mindmaps but hitherto i did not come across to a "language" for business mapping using computer mind maps.

At this time I am trying to implement the classification put forward by Nick Duffill in my dayly practise. I had an example of a tunnel map ready but it seems that I cannot post it; by the way I hope Nick will show his version to clarify his classification and enlighten us all

Much appreciated your blog!

[Tom Collins]

Great start on a very useful blog. I'd only like to echo Iain's request for some examples. Uploading graphics to Typepad is really easy now, so please share the visuals, as well as your wonderful verbal explanations!

[Denham]

Welcome to the blogosphere. Another type of map is often used is the site map - portrays the relationships between 'pages' within a website or portal.

I've always found mindmaps to be limited when compared to concept maps as there are no nodes and cross-linking is not often seen, i.e. mindmaps are most often associated with outlines or hierarchies.

It is far easier to show relationships and meaning, if you have both nodes and arcs to work with. Mind manager also makes it difficult to use spatial position to portray additional understanding - unless I'm missing something.

[carla]

very good

[Bea]

I know I'm a little late on this one... I use the library most often to map out my entire Masters. I also use the writing map as described above to map out any papers I need to write. I find my first draft doesn't need to be throw away this way as the knowledge is already in logical order and thought out thoroughly.

I also have a paper map template for reading others papers and mapping them. It includes critical reflection, structuring and application in practice questions to make me think about each paper as I read it (not as I try to write my own paper).

By mapping literally everything I do in my study, I only need to do a single pass on wordy readings. Any further thinking, reviewing and re-reading is done with my mind maps (and is super fast!).

Thanks for these other types. I'd not thought about the best way for presenting (or project work) before. Much more flexible than the old project chart!

Cheers,
- B

[Joshua Long]

Great definition of the foundational use of maps! I had never thought of using them for presentation tools. They have always been libraries and now 'Tunnel Timelines' thanks to ResultsManager and GyroQ.