With MindManager8, new functionality includes an interactive PDF image which I am trying to share via a wiki. Anyone have thoughts on attaching a PDF and also getting the links to work on the mind map? The wiki is the only common companywide place to store the attachments…no fair putting them on a SharePoint or server because there is no companywide of either of them.

Another thing that I do is to make the map closer to the org chart format where there are main columns of information going downward instead of the branches extending radially.

Nothing converts a client or prospect as much as beginning a conversation with Main Topic-level map with questions or points to be addressed, and letting them watch as their responses or priorities are added during the call. Then, sending the map to them and encouraging them to download the trial software, or the MindManager Reader, or–failing that–sending them a PDF of the map.

People like to hear themselves speak: they’re even fonder of seeing their goals and ideas turn into a prioritized action plan in front of their eyes!

I’ve recently started testing Comapping (see comapping.com). This is a neat flash based online mindmapping program, not as feature rich as Mindmanager, but allows you to share your maps with others, who do not need to hold a Comapping account. You can try it out for 30 days, and if you should like it, it will set you back the princely sum of $25US for a year’s subscription.

I’m sure there are others, but these are the one’s I’ve used and found worthwhile.

For non-mindmappers, I still try to confront “Map Shock Syndrome” by educating about the benefits of mapping, and in fact, turn it into something that is a value-add provided by my company – others deliver a 100 page report, I give them a mindmap with the same information on one page, clearly showing the relationships etc. Generally, I’ll export to a jpg or pdf and share those files, as well as the printed versions.

Jürgen Strauss
http://www.innovabiz.com.au

First, if you can get your audience engaged in building the map, they won’t be shocked, they’ll be ‘bought-in’ and aligned. That’s the beauty of team-mapping. But if that’s not possible, here are a few ideas for your consideration:

Map Organization: This is essential. Too many main topics off the central topic may start the overwhelm process as soon as the map is presented.

Topic Positioning: Where’s the starting point (if there is one)? Would it help to number topics? Are you presenting this info or emailing it out? If your not presenting, using a numbering system will help others understand the desired order to review the map.

Topic Text: Too much text will tend to make maps difficult to read and cause eyes to glaze over the map. Use meaningful concise words or phrases. Add details into topic notes or sub-topics.

Text Size: Is your map readable? I use map font sizes to indicate levels in the map, starting with the largest font as the central topic and reducing it (or at times keeping the same but not larger) on each subsequent level.

Projecting: Are you projecting your map on a wall? Test it out beforehand. Often topics are hard to read, fonts too small, etc…

Colors / Shapes / Images: Use these judiciously. Do they add value to the map? Or distract? There is no right or wrong here. Take into consideration the purpose of the map, the content, the audience, your goals.

Collapse Your Map: Make sure the map is fully collapsed. If you open a branch, only 1 level should show at a time unless there is a practical or strategic reason to expand beyond 1 level.

Balance Your Map: Does your map cause visual dissonance? Use the balance map feature or manually drag main topics into places that make the map more appealing to the eye.

Growth Direction: Does the growth direction make sense for the content inside? For instance a SWOT map makes sense to have a topic in each corner. However, I find project maps (plans) are easier to read / follow / present when they are ‘right facing’, like linear lists. Don’t try to force fit everything into a radial structure.

Extraneous Elements: In the ‘view’ menu, you can opt to hide elements in your map before making the presentation. These could include task info, markers, text tags, links, labels, comments, etc…Removing elements from view will make the map easier to digest.

Master the Keyboard: Demonstrating maps with your mouse can also lead to problems. I’ve learned to use the extensive short cut keys to facilitate real-time mapping and map presentations. Here are a few that I find most useful:

Use F4 to hide the entire map, except the branch that you want to discuss. Clicking F4 again on the same topic will make the map reappear.
Use F3 to center and open the current branch while closing all other branches.
Use ‘CTRL + D’ to opens the topic levels, 1 level at a time for each CTRL – D that you click.
Use the Arrow keys to navigate around the topics.
Use ‘CTRL + Arrow keys’ to scroll the map in small increments.
Use ‘CTRL+=’ or ‘CTRL+-’ to zoom in or out.
Lost in your own map? Use ‘CTRL+Home’ to return the focus to the central topic.

Last, with your hands on the keyboard, you can quickly insert criticisms and comments directly into the map. When your audience sees this, they’ll feel heard and the process of ‘Map Delight Syndrome’ has just begun.

Again, great discussion. What are some of the other approaches used? Would love to hear more feedback.

One of the most effective ways I’ve seen to share Mind Maps is… don’t share them at all. Mind Maps are a tool. Instead of selling the idea of the tool (the maps) use the tool in context and then let people ask “Wow! How did you do that?”.

I have introduced hundreds of people to Mind Mapping while teaching workshops on SharePoint, which has nothing to do with Mind Mapping. In order to display the hierarchy of a site, or how to build a specific section in the platform, I expose the presentation incrementally through the expansion and contraction of the various sections, never mentioning ‘Mind Map’.

At the end of the presentation, I will ALWAYS get the ‘Wow!’ statement. I then briefly introduce the tool. From my unscientific estimates, 50% to 75% of the people in the workshop immediately download a trial version of the software.

If you are interested, there’s a five minute screencast on my site talking about how to create a Master Calendar in SharePoint. Literally a third of the screencast is a walk-through of the Mind Map that defines the process of creating the calendar.

http://www.endusersharepoint.com/?p=892

Hope that helps.

Regards,
Mark

The Herrmann Brain Dominance Instrument (HBDI), similar to the MBTI but based on brain physiology, has been administered to more than a million people and shows thinking preferences in a quantitative way. Thinking preferences have little to do with competence, – but they are both wired and the result of working experience. About half the world prefers the linear style.

I have had good experience using a map in a presentation to a City Council – we got what we wanted – but I was there to explain exactly how the map works. But for ordinary communication, you can follow an old marketing rule. Communicate in the language that the receiver understands.

I use two products; MindManager and TopicScape and both have merits and deficiencies.

It frustrates me more, when they say that the graphics are too confusing. That means they’re communicating the fact that they are turned off to it, when I’m all pumped up and excited to show what it can do! The biggest complaint is the moving around and navigating to and fro, here and there, panning, zooming in / out, filtering views to branches, etc.

I find that people react differently to the number of objects on a screen. What I might view as eye candy, others might say is eye clutter. To those that say it’s clutter, I convert to HTML. That way, they have a list and a map. I also convert to a Word document if they don’t want any map parts.

To me, I construe the world as visual and consume things through my senses. I notice that as much as I am that way, others are polar opposites! They’d never purchase a product like MindManager or TopicScape, because they would say (and have) that it’s a waste of time and money.

As a project manager, I apply all documentation to TopicScape structures and project plans are first developed in MS Project, then imported to MindManager. Once there, my consulting team, along with client members, discuss and refine the project plan. This is all visual, up on a screen for the room to see from my laptop. I then re-apply the new MindManager project plan to a new MS Project plan with a new version number. Issue logs and risk logs are living documents and live in MindManager.

Personally, I dislike lists and some people love lists and outlines. I like to move objects around and look for relationships between objects, whether it’s an HTML, document, powerpoint, excel spreadsheet, whatever… and that’s where TopicScape comes in quite handy. I can put these things inside of pyrimids (or cones), assign different types of relationships, find occurences between them and so forth. This has a slightly different effect on some people. I think it’s because TopicScape is more 3D than MindManager.

I have been experimenting with a couple of types of 3D glasses, but they tend to bother me between my eyes and results in giving me a headache.

So, that’s my take!