The long branch title problem
We've all cringed at PowerPoint presentations which are full of large blocks of text instead of bullet points. Especially when the presenter just reads the slide verbatim, adding no apparent value to what has being visually presented.
Yet many people fall into the same trap when they create their MindGenius maps. They put in swathes of text into their branch titles and do not recognise that they have significantly reduced the effectiveness of the maps they have produced.
When people look at a map which has large amounts of text in the branch title they find it difficult to identify the key messages that are contained within the information presented. All the glue words that we use in verbal communication seem to hinder, rather than help, in the visual communication medium. The highlighter pen businesses profit greatly from this.
The inherent structure of the information is not readily apparent which hinders understanding. You have to mentally discard the glue words to identify and understand the structure, instead of your eyes communicating the structure directly to your brain. This significantly slows down the rate of understanding the content of your map.
In extreme cases, your map can appear unappealing to the eye. It is not memorable, just a series of large text blobs.
|Long Branch Titles|
|Short Branch Titles|
Short branch titlesThere are significant drawbacks in using branches with large amounts of text. Keep your branch titles short and to the point.
Easy to say, but it is not necessarily easy to do. There is always the temptation to add another word to make the branch title less ambiguous. However, before you know it you are creeping back towards the swathes of text scenario. The secret is in knowing when to stop.
Keeping your MindGenius branch titles short and to the point requires self-discipline but it does become easier with practice.
Here’s how I do it. I reduce the information I wish to communicate to its essentials by identifying the key words (e.g. nouns, verbs) or phrases by mentally highlighting them. I then create the structure of the information using parent/child branches structures. I don’t worry about losing the 'detail' or the 'finer nuances' of the information that are contained in the richness of our language. If needs be, I can put the grammatically correct representation of the information in the notes associated with the branch. The Note icon indicates to the reader that more information is available if they require it.
The previous map, with long branch titles would be changed to the following:
Try thisIf you want to practice developing your short branch title skills then try the following:
• Create a dummy parent branch,[e.g., type ‘A’ and hit return] and paste your wordy text into the branch note.
• In the Notes Editor Highlight the key words in the block of text.
• Then put a meaningful summary title in the dummy branch title and create a child branch structure to reflect the key words.
What branch title length?Now comes the big question. How short is short? What is the optimum number of words for a branch title? The mindmapping purists would say one word per branch title. I take a more pragmatic approach. I believe that the answer depends on the purpose of the map, its intended audience and the ramifications of the map’s information being misinterpreted.
The shorter a branch title is, then the more ambiguous its meaning to a reader can become. You could say that ambiguity is the ally of creativity and the enemy of deployment.
When you are seeking to be creative you do not wish to restrict the avenues of thought that people could pursue.
If I was facilitating a brainstorming session then I would tend to use single word branches where possible in the idea generation phase.
If I made the branch title ‘red door’ then the brainstorming participants may limit their thoughts to scenarios with red doors.
If instead I made the parent branch ‘door’ and it’s child branch ‘red’ then the brainstorming participants have a much wider range of avenues of thoughts to consider such as other colours, other traits of a door, etc.
However if I was seeking to instruct someone on how I wish some procedure to be performed then I would want to ensure that they clearly understood what they had to do and that there was no room for misunderstanding. In such a case I would use a few words (up to five) words in the branch title to zero in on the specific aspect I wished to address and provide the detailed instructions in the note associated with the branch. I would also add some child branches to provide them with the key points associated with the detail.
So my rule of thumb for branch length is one word for maps used to facilitate creativity and the development of ideas and up to five words for instructional maps, augmented by details in the branch notes if required. But remember, it is a rule of thumb. Don’t let it get in the way of your map being fit for the purpose you intend it for.
So there you have it. Keep your branch titles short and reap the immense benefits that MindGenius maps can give to you and your organisation.
As ever, if you have any questions or queries, Ask Gordon
Visit the MindGenius site at www.mindgenius.com.